From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Rugen <jprugen@earthlink.net>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: RTC and SCSI for PowerStack/2.4.6 Kernel
Date: Mon, 9 Jul 2001 16:47:58 +0200 [thread overview]
Message-ID: <20010709144758.31505@smtp.adsl.oleane.com> (raw)
In-Reply-To: <000e01c10884$e4201e60$0401a8c0@trex>
>Did anything change in regards to oops output on crashes since 2.2.x? I'm
>not suprised that the kernel would crash/hang without producing any, but I
>thought I'd ask to make sure.
2.4 can Oops instead of always panic'ing, but it's frequent that you
are too much locked up already to be able to read the oops report.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-09 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 7:49 RTC and SCSI for PowerStack/2.4.6 Kernel Jeff Rugen
2001-07-08 19:00 ` Tom Rini
2001-07-09 14:38 ` Jeff Rugen
2001-07-09 14:47 ` Benjamin Herrenschmidt [this message]
2001-07-09 14:57 ` Tom Rini
2001-07-09 15:08 ` Geert Uytterhoeven
2001-07-09 15:17 ` Tom Rini
2001-07-09 15:25 ` Jeff Garzik
2001-07-09 16:20 ` Jeff Rugen
2001-07-09 18:48 ` Olaf Hering
2001-07-09 20:37 ` Jeff Rugen
2001-07-09 20:54 ` Olaf Hering
2001-12-13 16:13 ` Tom Rini
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=20010709144758.31505@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=jprugen@earthlink.net \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).