https://bugzilla.kernel.org/show_bug.cgi?id=62351 --- Comment #4 from Tejun Heo <tj@xxxxxxxxxx> --- So, when the machine boots up libata doesn't touch the LPM setting and just considers it "max_performance", which may or may not be true. I think it'd work the same if you just set the lpm knob to max_performance explicitly. The problem is that your BIOS is most likely configuring DIPM on both the device and host sides during boot; however, after coming back from suspend, the device side seems to be configured but the host side isn't, so the device's LPM operations register as link events to the controller leading to the spurious failures. Maybe we should set max_performance mode explicitly during boot requiring the user to explicitly set min_power mode if [s]he wants to but then we might cause power regression on some setups. Anyways, can you please verify echoing max_performance also makes the issue go away? -- You are receiving this mail because: You are on the CC list for the bug. -- 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
