https://bugzilla.kernel.org/show_bug.cgi?id=62351 --- Comment #5 from Patrik Jakobsson <patrik.r.jakobsson@xxxxxxxxx> --- Here are all the test cases: After boot: LPM policy reports max_performance and min_power and max_performance can be switched back and forth without any errors. Before suspend: If I don't touch LPM policy after boot (still reporting max_performance) I can successfully suspend and LPM policy still reports max_performance (though probably incorrect) after resume. Before suspend: If I explicity set max_performance after boot and go into suspend it fails. If I set min_power back in this state, the errors stop. Before suspend: If I explicity set min_power after boot and go into suspend it succeeds. So I must either never touch the LPM policy or set it to min_power to not get the errors on resume. min_power seems to be what the hardware is set to but doesn't get reported correctly (as you say) until I've actually set it to something. -- 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
