[2921] in linux-scsi channel archive
How to test SCSI drivers? Interrupt driven reset/abort ???
daemon@ATHENA.MIT.EDU (Juergen Gaertner)
Fri Dec 12 14:50:34 1997
Date: Fri, 12 Dec 1997 20:38:10 +0100 (MET)
From: Juergen Gaertner <Juergen.Gaertner@mbox.si.uni-hannover.de>
To: linux-scsi@vger.rutgers.edu
Hi,
I'm currently writing on a driver for the Western Dig cards 7193, ... 7296.
In my current attempt I'm using an interrupt driven abort/reset sheme. But I
have the preoblem, that I then can't tell the result to the mid-level code.
If I give back "SCSI_RESET_PENDING" scsi.c sits still and makes nothing.
If I try to do a done() to the command passed to the reset function of my
driver, horrible things are going on. This makes sence, because done() has
been called once before.
But what can I do, If there are no more outstanding commands? how to tell
scsi.c, if the reset was succesfull or not?
Another question concerning testing:
To test if all things are working, I use an old Miniscribe 20MB drive, make
a "badblocks -s /dev/sda" on it and then interrupt the power line for some
ms.
What happens is, that I get some commands timed out, then scsi.c makes an
device reset, but nothing else, leaving badblocks suspended.
Is this test too hard, or is it related to my first question?
Rgs. Gaerti
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
