[3949] in linux-scsi channel archive
2.1.10x scsi code: no timeout
daemon@ATHENA.MIT.EDU (Kurt Garloff)
Mon May 18 19:59:28 1998
Date: Sat, 16 May 1998 02:20:23 +0200
From: Kurt Garloff <garloff@kg1.ping.de>
To: linux-scsi@kg1.ping.de
Cc: "Leonard N. Zubkoff" <lnz@dandelion.com>,
Doug Ledford <dledford@dialnet.net>,
Eric Youngdale <eric@andante.jic.com>,
Gerard Roudier <groudier@club-internet.fr>
Mail-Followup-To: linux-scsi@kg1.ping.de,
"Leonard N. Zubkoff" <lnz@dandelion.com>,
Doug Ledford <dledford@dialnet.net>,
Eric Youngdale <eric@andante.jic.com>,
Gerard Roudier <groudier@club-internet.fr>
Hi Linux SCSI experts,
As I'm working on the tmscsim (AM53C974) driver and did a lot of testing, I
happen to have situations, where the driver doesn't actually sends a command
to the SCSI bus, but leaves it in the driver queue and never calls scsi_done.
With 2.0.3x, the midlevel code then times out and abort the command.
With 2.1.10x, nothing happens. Nothing, but the program being responsible for
the request (insmod, fdisk or whatever) hangs (D). No timeout.
Has the driver to be adapted to 2.1 or is this a bug? (I know, that there
is a new error handling policy in 2.1 midlevel SCSI, but it's some work to
implement it, hardly any driver uses it yet (?) and the old should work in
any case.)
Does this only show up on my adapter or on others too?
Im looking forward to doing further tests to track this down ...
Regards.
--
Kurt Garloff, Dortmund
<K.Garloff@ping.de>
PGP key on http://student.physik.uni-dortmund.de/homepages/garloff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
