Re: Incorrect response to SK/ASC/ASCQ = x 02/04/01 (becoming ready)

[Luben Tuikov <luben_tuikov@adaptec.com>]

> Maybe the solution, then, instead of blocking, is to do something
> similar to quiesce, wherein we block normal user-initiated medium access
> but allow special requests. (?)

Yes, something like that.

> Not sure what an HOQ task attribute command is. Where in the t10.org
> specs should I look for a definition of that?

"Head Of Queue", cf., E.g. SAM-3r13, section 8.
 
> How would this interact with tagged command queueing? We don't want to
> attempt to queue other commands while START STOP UNIT is pending at the
> device. We don't want to disable disconnects, either, otherwise the bus
> would be blocked while waiting for START STOP UNIT, correct?

What would happen when you have SSU with IMMED=0 pending at the device
server and you send another task with say SIMPLE task attribute? ;-)
 
> Maybe this is a SCSI-novice question, but, does disconnection require
> tagged commands? Is the Linux midlayer smart enough to know that some
> kinds of commands need to block others until they complete?

Not sure I completely understand the questions, but I don't think
SCSI Core keeps an image of the deivice server's queues.  It may
keep a state (send/don't send) given recently sent commands, but
not as delicatly as a device server.

		Luben