Public bug reported:
Binary package hint: powernap
Hello,
when first invoked, the /etc/pm/power.d/cpu_frequency script save the active
governor to /var/run/powernap/cpu_governor.default for latter restoration.
However that might happen when the active governor is not (yet) set to the
desired one.
For example during the boot sequence.
In my case the desired active governor (ondemand) is set at boot time by the
cpufrequtils init.d script.
However during the boot sequence powernap is started before cpufrequtils (at
least here), and the governor written in /var/run/powernap is the wrong one
(performance, which was active before cpufrequtils run)
Latter when powernap runs the powersave actions, it correctly set the
governor to 'powersave', but when the recover actions are taken,
cpu_frequency set the governor to performance (which is what
/var/run/powernap/cpu_governor.default contains) not ondemand (which was
the active governor just before powernap became idled).
I have modified /etc/pm/power.d/cpu_frequency to acheive a behavior that seems
more correct to me.
Now /var/run/powernap/cpu_governor.default is written for latter restoration
each time the governor is about to be set to powersave, not just when the
script is first invoked.
That way powernap doesn't silently override the governor set by
cpufrequtils init.d script, or any governor change made when the machine
is not idled.
** Affects: powernap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743682
Title:
cpu_frequency restore wrong governor
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
