Bjørn Mork <bjorn@xxxxxxx> writes: > "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx> writes: > >> OK, thanks! Well, this is somewhat worrisome. >> >> Could you also check the linux-pm.git/fixes branch that contains all patches >> I'm planning to push for 3.13-rc7 shortly? > > It's definitely still there. But I'm less sure about the exact trigger. I did a couple of more tests after clean reboots, and 100% sure ways to trigger the circular locking on my laptop are echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor s2disk or echo 1401000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq s2disk or echo 1401000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq s2disk Note that "ondemand" and "1401000" are the default vaules, so I don't actually change anything here. The write is causing the problem, not the value. As expected, I guess. Also note that boot vs non-boot cpu doesn't seem to matter. Nor does cancelling the hibernation. The warning appears on hibernate - not on resume. Hope this helps. Bjørn -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
