Red Hat Bugzilla – Bug 508562
CPU speed stuck at lowest after resume from hibernation
Last modified: 2013-04-30 18:54:33 EDT
[might not be a gnome-power-manager bug, but a kernel one]
- sometimes, after a hibernate/resume cycle, the cpu speed gets stuck at the lowest value, no matter what I set in the cpufreq applet
- setting something in the cpufreq applet just does nothing (no errors)
- hibernating and resuming again does not help
- this does not happen every time, but once in a while (say once every five cycles)
Fedora 11 on a Dell Inspiron 630M laptop
cpufreq_ondemand and acpi_cpufreq modules loaded
Hrm, I'm not seeing this bug anymore with recent F11 kernel builds, but I also changed laptop in the meanwhile (Thinkpad X60).
I did not see this in a long while now.