I see this happening too, since I started tracking hardy which has made
the switch to the pm-utils infrastructure. I have to resort to
restarting powernowd every time after I resume. Looking at /var/log/pm-
suspend.log, it appears that all the resume hooks are running, which
includes /usr/lib/pm-utils/sleep.d/94cpufreq. That script should set the
governor back to ondemand, but apparently that's not happening, and the
governor remains performance instead of switching back to ondemand.

-- 
pm-utils changes default cpu policy after resuming from suspend-to-ram
https://bugs.launchpad.net/bugs/162652
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to