From: Jun Sun <jsun@mvista.com>
To: Jack Miller <jack.miller@pioneer-pdt.com>
Cc: Linux-Mips <linux-mips@linux-mips.org>, jsun@mvista.com
Subject: Re: kernel BUG at sched.c:784!
Date: Fri, 18 Jul 2003 15:59:27 -0700 [thread overview]
Message-ID: <20030718155927.I31523@mvista.com> (raw)
In-Reply-To: <JCELLCFDJLFKPOBFKGFNAEKOCFAA.jack.miller@pioneer-pdt.com>; from jack.miller@pioneer-pdt.com on Fri, Jul 18, 2003 at 03:51:25PM -0700
On Fri, Jul 18, 2003 at 03:51:25PM -0700, Jack Miller wrote:
> Jun,
> ' Got the BUG() again after about 5 hours of operation. The BUG()
> report is below. Any additional insight you can provide is greatly
> appreciated. Thanks again for your help.
>
> Jack
>
> Linux version 2.4.17 (jack@saturn) (gcc version 3.2.2 20030612 (Pioneer
> Voyager)) #5 Fri Jul 18 12:51:00 PDT 2003
>
> active_mm = 83f02b20
>
This make CPU bug being the cause unlikely.
Are you using preemptible-kernel? I can't think of anything specific.
I think you have to do some honest kgdb debugging.
BTW, I have a simple trace tool (which I think is easier to use
than LTT) you may find helpful. Good luck.
http://linux.junsun.net/patches/generic/experimental/030716.a-jstrace.patch
Jun
prev parent reply other threads:[~2003-07-18 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 16:57 kernel BUG at sched.c:784! Jack Miller
2003-07-18 17:08 ` Steven J. Hill
2003-07-18 17:22 ` Jun Sun
2003-07-18 17:26 ` Jack Miller
2003-07-18 17:44 ` Jun Sun
2003-07-18 17:48 ` Jack Miller
2003-07-18 18:29 ` Jun Sun
2003-07-18 18:48 ` Jack Miller
2003-07-18 22:51 ` Jack Miller
2003-07-18 22:59 ` Jun Sun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030718155927.I31523@mvista.com \
--to=jsun@mvista.com \
--cc=jack.miller@pioneer-pdt.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.