ondemand governor sets cpu frequency to 100% after resume

[Russell Sears]

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-2.6.22-11-generic (2.6.22-11.33)
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.d/powernowd restart
<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.d/sleep.sh

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.

[Leann Ogasawara (leannogasawara)]

Hi Russell,

This looks like a duplicate of bug 124797 so I am marking it as such. Thanks.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!