From: "Tony Battersby" <tonyb@cybernetics.com>
To: tom@qwws.net, linux-scsi@vger.kernel.org
Subject: RE: SCSI regression: sym53c8xxx_2 (2.6test11 vs. 2.6final)
Date: Fri, 19 Dec 2003 09:07:44 -0500 [thread overview]
Message-ID: <03Dec19.090744est.332228@cyborg.cybernetics.com> (raw)
In-Reply-To: <200312190923.57405.tom@qwws.net>
> Booting 2.6.0 final results in the following messages:
>
> [...]
> sym0: <895> rev 0x1 at pci 0000:02:0a.0 irq 22
> sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking
> sym0: SCSI BUS has been reset.
> scsi0: sym-2.1.18b
> sym0:0:0: ABORT operation started.
> sym0:0:0: ABORT oberation timed-out.
> sym0:0:0: DEVICE RESET operation started.
> sym0:0:0: DEVICE RESET operation timed-out.
> sym0:0:0: BUS RESET operation started.
> sym0:0:0: BUS RESET operation timed-out.
> sym0:0:0: HOST RESET operation started.
> sym0: SCSI BUS has been reset.
I've seen this under 2.4.x when the machine is not processing interrupts
correctly. I know nothing of 2.6, but it's a good bet that there is
something that is preventing the SCSI interrupt from being processed.
Under 2.4 you can verify this by checking the interrupt count from
/proc/interrupts. Under 2.4, I would say to try booting with "noapic".
I think 2.6 has different boot options (I remember seeing something
about ACPI and interrupts). Maybe someone else can help out here.
Anthony J. Battersby
Cybernetics
next prev parent reply other threads:[~2003-12-19 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 8:23 SCSI regression: sym53c8xxx_2 (2.6test11 vs. 2.6final) Tom Winkler
2003-12-19 14:07 ` Tony Battersby [this message]
2003-12-22 1:27 ` Matthias Andree
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=03Dec19.090744est.332228@cyborg.cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tom@qwws.net \
/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