[3545] in linux-scsi channel archive
Re: SMP 2.1.90-pre3 SCSI kernel panic
daemon@ATHENA.MIT.EDU (Juergen Gaertner)
Tue Mar 17 05:31:36 1998
Date: Tue, 17 Mar 1998 11:28:41 +0100 (MET)
From: Juergen Gaertner <Juergen.Gaertner@mbox.si.uni-hannover.de>
To: Doug Ledford <dledford@dialnet.net>
cc: sistema@readysoft.es, linux-scsi@vger.rutgers.edu
In-Reply-To: <350E47B9.3B2F001A@dialnet.net>
On Tue, 17 Mar 1998, Doug Ledford wrote:
> sistema@readysoft.es wrote:
>
>
> Secondly, there are a lot of drives out there with firmware that starts to
> flake out if the error is bad enough. Some of the drives I've seen in the
> recent past would completely wedge the entire SCSI bus so hard that the only
> solution was to power down the system before it would work again when it hit
> particularly bad portions of the disk.
>
My driver is capable to see, if all things are right with the host. But If
it detects, that there is some corrumption, what can I do, to inform scsi
code about such a condition. I implemented it in a way, that the card
doesn't accept new commands, returning "DID_ERROR". I'm not shure, if this
is the right way. Is there some other method to inform scsi-code about the
state of the host? How I can tell scsi-code to reset my host? (In the
moment, my driver makes that itself, but I don't know how to tell scsi-code,
that the host has been resetted, or needs to be resetted, when there are no
outstanding scsi-commands)
Rgs. Gärti
public PGP key can be obtained via
"http://www.unics.uni-hannover.de/gaertner.juergen/pgp.asc"
\ *** Schering-Institute for high-voltage technologies and applications ***
\/\ My Name: J"urgen G"artner | Phone: +49+511+762-2705 Fax: -2726
\ gaertner@mbox.si.uni-hannover.de | Ordinary Mail: Callinstrasse 25A
_\| http://www.unics.uni-hannover.de/~nhmasche | D-30167 Hannover
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
