[6124] in linux-scsi channel archive
Re: Guru required: BUSY status
daemon@ATHENA.MIT.EDU (grant@torque.net)
Thu Mar 18 19:35:07 1999
From: grant@torque.net
To: schaefer@alphanet.ch (Marc SCHAEFER)
Date: Thu, 18 Mar 1999 17:42:25 -0500 (EST)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <7crsv7$hdd$1@vulcan.alphanet.ch> from "Marc SCHAEFER" at Mar 18, 99 10:59:03 pm
> > option - the initiator must respond to reselection within 200us, so
>
> 250 ms (250 millisecond).
The standard says: "The reselected initiator shall then assert the BSY signal
within a _selection_abort_time_ of its most recent detection ..."
And _selection_abort_time_ is defined to be 200us in my copy of the standard.
_selection_timeout_delay_ is 250ms, but that's not the same thing.
> > What I propose is to detect the BUSY status in the low-level driver,
> > sleep for a short time, and then retry the command, without ever alerting
> > the mid-level code. This seems a fairly obvious solution, but I
> > might be missing something. (In particular, I'm worried about the
> > possibility of the mid-level code timing out and aborting the command.)
>
> If you set DID_BUS_BUSY, the higher level code will retry indefinitely.
> Look in aic7xxx.c for BUSY for more details.
I'll look at that - but are you sure that the eh logic won't reset the
bus ?
--------------------------------------------------------------------------
Grant R. Guenther grant@torque.net
--------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
