James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: > I just noticed this with a rather finickey SAS system I have. It's got > a SATA DVD attached over an expander. Periodically the DVD just hangs > up, so we wait for the timeout and then send a phy reset which clears > it. > > What I'm seeing with the new block timer code is that the timer never > expires. I can dig some more into this, but if you wanted to test it as > well, the timer code is easy to excite. Just throw away one command in > every 128 or so in the queuecommand routine of your favourite HBA > driver. I have not seen the case of the timer never expiring, but will look into other test cases. Mike C and I where seeing timeout issues (host staying in recovery state or list debug bugon's) when running tests with timeouts set to 1 or 2 seconds. We are working with Jens to address this. The issue we where hitting appears related to the scsi_eh / scsi_done completion synchronization. -andmike -- Michael Anderson andmike@xxxxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
