Robert Hancock wrote: > Darrick Burch wrote: >> Robert Hancock wrote: >> >>> Could be some kind of SATA PHY quirk or incompatibility that only shows >>> up in AHCI mode or something. It seems from the output that the SATA >>> link may be going up and down. You could try forcing 1.5Gbps >>> (libata.force=1.5Gbps if libata is built in, or force=1.5Gbps when the >>> libata module gets loaded) and see if that helps. >> >> That appears to have done it--thanks! I feel kinda bad now because I was >> suspecting a speed issue, but couldn't figure out how to force it. If I >> had read the kernel documentation a little more, I would have found the >> kernel option you mentioned. Duh. At any rate, thanks again. > > Could be we need a quirk in libata for that drive to do that > automatically, or something.. Can you post the dmesg output from bootup > with the force 1.5Gbps option in place? I don't think we can do a quirk here as it happens before the driver has any way to identify the device. libata EH usually can react to PHY problems like this correctly and lowers speed automatically but in this case it doesn't work because the PHY stays online too briefly for libata EH to consider it to be the one device failing. It just resets error history and restarts probing sequence on each PHY event. :-( Maybe libata EH needs to keep PHY errors over failing probings and act on it. Hmm... -- 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
