Part of the problem I've had in debugging this 'hang' condition has turned
out to be a failing drive- I finally caught in a situation of:
First Error:
(da1:isp0:0:1:0): READ(10). CDB: 28 0 0 47 57 aa 0 0 6 0
(da1:isp0:0:1:0): ABORTED COMMAND asc:48,0
(da1:isp0:0:1:0): Initiator detected error message received field replaceable unit: 2
Then the next command fails to do Auto Request Sense:
isp0: Auto Request Sense failed for target 1 lun 0
Then there's an infinite (and quiet until I put a debug line in) sequence of:
isp0: fdevq 1.0 20c 8, i.e., freeze of Device Queue because the device is
always sending back a busy status. This goes on until you reset the machine.
It strikes me that an upper bound of busy time would be a good thing to
have- it took me several days of hangs in the middle of the night until I
finally caught this. You can say that this is "flaky" h/w (and you'd be
right), but seems like a good case for defensive programming. Whew. I'm
sore fatigued...
-matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message