Fajun Chen wrote:
Hi Tejun, Could you please elaborate all the conditions triggering the error handling? I know that command failure or HBA error can trigger EH, but does EH schedule any routine error checking autonomously? The particular scenario I am looking at is if a drive is moved away from interface mode (through back door noninterface command) for some time then move back, will EH detect and declare it as an interface error?
What do you mean by moving away from interface mode? Do you refer to transfer mode? libata doesn't do any autonomous EH. Unless command fails or host reports exception (phy status change, etc...), EH won't kick in except for one case - it snoops cache on/off and schedule EH to revalidate device and configure SCSI dev accordingly.
-- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
