ondemand governor sets cpu frequency to 100% after resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.22
This bug occurs on a Lenovo Thinkpad X61 Tablet (Low voltage core 2 duo, 1.6ghz)
I'm running:
linux-image-
powernowd (0.97-1ubuntu7)
pm-utils (0.99.2-1)
acpi-support (0.95)
gnome-power-manager (2.18.2-0ubuntu3)
I'm using the ondemand governor (the default settings, as this just worked out of the box...) When the laptop resumes from suspend, the CPU frequency is pinned at 100%. I can work around this by running:
# /etc/init.
<now the governor is working correctly>
# ps uax | grep powernowd
<powernowd is not running>
#
I haven't touched the powernowd config files.
This command reproduces the problem:
# pm-suspend --quirk-s3-bios --quirk-s3-mode
as does:
$ killall gnome-power-manager
$ sudo /etc/init.
Clicking the red gnome logout button, then clicking suspend leads to erratic behavior, but does not reproduce the cpu governor problem. echo mem > /sys/power/state doesn't seem to cause the problem, but it crashes X. However, CPU load causes the governor to revert to its correct behavior and X / gdm / gnome use CPU on startup, so this isn't a great test.
Hi Russell,
This looks like a duplicate of bug 124797 so I am marking it as such. Thanks.