Re: [PATCH 1/2] cpufreq: try to resume policies which failed on last resume
From: BjÃrn Mork
Date: Fri Jan 03 2014 - 05:15:33 EST
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
echo 1401000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1401000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
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
Hope this helps.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/