From: "Jeffrey W. Baker" <jwb@gghcwest.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: SuSE 2.4.19-SMP x86_64 crashing on SCSI errors
Date: 07 Jun 2003 10:45:46 -0700 [thread overview]
Message-ID: <1055007945.28393.13.camel@heat> (raw)
I have a machine where I can induce SCSI transmission errors by
configuring the bus for U320 operation. Unfortunately this panics SuSE
2.4.19-SMP kernel on x86_64 with adaptec 39320D. Stack:
timer_bh + 792
bh_action + 79
tasklet_hi_action + 139
do_softirq + 174
do_IRQ + 341
default_idle + 0
default_idle + 0
common_interrupt + 95
thread_return + 0
default_idle + 31
default_idle + 0
cpu_idle + 50
Code: unintelligible. bummer.
-jwb
reply other threads:[~2003-06-07 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1055007945.28393.13.camel@heat \
--to=jwb@gghcwest.com \
--cc=linux-kernel@vger.kernel.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