Hi Mathieu,
Thank your for reporting bugs and trying to make PowerNap and Ubuntu
Server better.
I have looked into this and in fact this is not an issue with PowerNap
directly, but rather with acpi-support/ondemand init scripts.
1. When the machine boots up, then it executes the acpi-support init script
2. This init scripts, also executes the /etc/acpi/power.sh script.
3. Then, the power.sh script, executes pm-powersave (which cases all the
scripts installed by powernap to be executing during boot time)
4. Way after this is done, the /etc/init.d/ondemand init script sets the
CPUFREQ to ondemand.
This mean that the ondemand frequency is set to ondemand way after pm-
powersave has been executed, causing the cpu_frequency script to save
the "incorrect" governor.
Thank you for pointing this out. Your patch looks good. I'm merging it.
Cheers,
** Also affects: powernap
Importance: Undecided
Status: New
** Changed in: powernap
Status: New => In Progress
** Changed in: powernap
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: powernap (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: powernap (Ubuntu)
Status: New => In Progress
--
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