From: Keith Owens <kaos@ocs.com.au>
To: ryan <ryan@netidea.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.0test10 crash (RAID+SMP)
Date: Mon, 06 Nov 2000 11:04:06 +1100 [thread overview]
Message-ID: <1459.973469046@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 05 Nov 2000 13:08:41 -0800." <3A05CC59.7B0566C7@netidea.com>
On Sun, 05 Nov 2000 13:08:41 -0800,
ryan <ryan@netidea.com> wrote:
>Kernel oops. A message like:
>
>"Detected LOCKUP on CPU0"
>or sometimes its CPU1...
Which tells us precisely nothing. Saying "a message like" is no good.
You need to follow the procedure in linux/REPORTING-BUGS, including the
_exact_ message, run through ksymoops if necessary.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-05 21:08 Kernel 2.4.0test10 crash (RAID+SMP) ryan
2000-11-06 0:04 ` Keith Owens [this message]
2000-11-06 1:39 ` ryan
2000-11-06 3:12 ` Neil Brown
2000-11-06 0:09 ` ryan
2000-11-06 9:00 ` Jeff Garzik
2000-11-06 9:40 ` Andre Hedrick
2000-11-06 22:19 ` Neil Brown
2000-11-06 11:51 ` Jason Straight
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 0:02 Ion Badulescu
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=1459.973469046@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@netidea.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