Can you elaborate a bit?  I don't really think completing a command
after 30sec timeout contributes a lot to driver stability.

Timeout, timeout, timeout, reset, timeout.. (repeat), failed I/O

This gives the end user no information about the fault, nor does it let
the upper layers of SCSI and above distinguish between a random passing
sulk and media errors which need the disk replacing.

quoted

Should that not then be a per host flag ?

Yeah, that would be the best.  The problem is that there are several
different kinds of timeouts and we don't know which controller locks up
after which timeout and investigating them is really difficult.

PATA controllers don't lock up in that case so its quite easy. The one
exception is if the device jams IORDY but in that case you are dead
anyway the next I/O (except on a SIL680 which has a timer we could use).

Old IDE says it works for PATA. For SATA I can see it might need more
care and you might simply not be able to get the info.

Alan