Alan Cox (firstname.lastname@example.org)
Sat, 19 Jun 1999 11:45:31 +0100 (BST)
> > It wont. It will however eventually do aborts, resets and then give up
> > on failed bus resets.
> I stand humbly corrected (the abort/reset sequence is an area I want
> to stay away from), although once a device has had a failed bus reset
> it is as good as dead. The mid-level SCSI code ignores the driver and
> if the driver is a module there is no way to unload it (from memory -
> pending requests prevents dismounts).
> Time to figure out how to increase the timeouts, preferably the
> "correct" way rather than jumping on the SCSI request which appears
> fraught with danger. That and no other SCSI driver I know of attempts
> such black magic.
I think this will work in the abort handler
/* Fake that this isnt the second timeout */
Scpnt->flags &= ~WAS_TIMEOUT;
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Sat 19 Jun 1999 - 06:50:29 EDT