From: Mike Anderson <andmike@us.ibm.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Andries.Brouwer@cwi.nl, torvalds@transmeta.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.5.63/64 do not boot: loop in scsi_error
Date: Thu, 6 Mar 2003 00:30:54 -0800 [thread overview]
Message-ID: <20030306083054.GB1503@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303060256200.25282-100000@montezuma.mastecende.com>
Zwane Mwaikambo [zwane@linuxpower.ca] wrote:
> scsi1 : QLogic ISP1020 SCSI on PCI bus 04 device 70 irq 89 MEM base 0xf8a18000
> scsi: Device offlined - not ready or command retry failed after error recovery: host 1 channel 0 id 0 lun 0
> scsi: Device offlined - not ready or command retry failed after error recovery: host 1 channel 0 id 1 lun 0
>
Did this work in 2.5.62? The qlogicisp driver does have any error
handlers. Any error will cause a device offline state. You
should see a message at boot like:
ERROR: This is not a safe way to run your SCSI host
ERROR: The error handling must be added to this driver
This does not explain what is causing the error handler to start up or
do anything to help your problem.
We have been switching to the feral driver to handle the qlogic isp
card. This driver contains error handling routines. I believe the 2.5
versions of the driver is in the -mm tree. I also believe Andrew has it
as a separate patch.
I did try running the qlogicisp driver and it appears to be loading for
me, but I do not have any non-disk devices on the system at the moment.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-03-06 8:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 6:39 2.5.63/64 do not boot: loop in scsi_error Andries.Brouwer
2003-03-06 6:49 ` Mike Anderson
2003-03-06 7:59 ` Zwane Mwaikambo
2003-03-06 8:30 ` Mike Anderson [this message]
2003-03-06 8:35 ` Zwane Mwaikambo
2003-03-06 8:55 ` Mike Anderson
2003-03-06 9:00 ` Zwane Mwaikambo
2003-03-06 9:18 ` Mike Anderson
2003-03-06 9:58 ` Zwane Mwaikambo
2003-03-06 16:31 ` James Bottomley
2003-03-06 17:15 ` Zwane Mwaikambo
2003-03-06 17:21 ` James Bottomley
2003-03-06 17:39 ` Zwane Mwaikambo
2003-03-06 18:14 ` Mike Anderson
2003-03-06 17:24 ` Mike Anderson
2003-03-06 8:37 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 9:22 Andries.Brouwer
2003-03-06 1:01 Andries.Brouwer
2003-03-06 1:13 ` Patrick Mansfield
2003-03-06 1:22 ` Linus Torvalds
2003-03-06 4:15 ` Rob Radez
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=20030306083054.GB1503@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zwane@linuxpower.ca \
/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