From: William Lee Irwin III <wli@holomorphy.com>
To: Misha Nasledov <misha@nasledov.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11 Oops
Date: Mon, 8 Dec 2003 01:56:54 -0800 [thread overview]
Message-ID: <20031208095654.GS19856@holomorphy.com> (raw)
In-Reply-To: <20031208095349.GA1232@nasledov.com>
On Mon, Dec 08, 2003 at 01:41:38AM -0800, William Lee Irwin III wrote:
>> What did it say the cause for it was? BUG()? Fault?
On Mon, Dec 08, 2003 at 01:53:49AM -0800, Misha Nasledov wrote:
> I don't know; I copied everything off the screen once it stopped scrolling by
> so fast. A few other stack traces popped up but were scrolled up too quickly.
> I couldn't scroll up or anything..
Scheduling while atomic warnings look different and there aren't many
obvious places to oops or BUG in the scheduler (or at least AFAICT there
haven't been stability issues there for some time).
-- wli
prev parent reply other threads:[~2003-12-08 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 3:21 2.6.0-test11 Oops Misha Nasledov
2003-12-08 9:30 ` Misha Nasledov
2003-12-08 9:41 ` William Lee Irwin III
2003-12-08 9:53 ` Misha Nasledov
2003-12-08 9:56 ` William Lee Irwin III [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=20031208095654.GS19856@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=misha@nasledov.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox