Bug 508562 - CPU speed stuck at lowest after resume from hibernation
Summary: CPU speed stuck at lowest after resume from hibernation
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-28 15:58 UTC by Cosimo Cecchi
Modified: 2013-04-30 22:54 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-01 13:27:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Cosimo Cecchi 2009-06-28 15:58:16 UTC 
[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
DeviceKit-power 008-1.fc11
gnome-power-manager-2.26.2-1.fc11
kernel 2.6.29.5-191.fc11.i686.PAE
cpufreq_ondemand and acpi_cpufreq modules loaded
Comment 1 Cosimo Cecchi 2009-09-10 17:08:44 UTC 
Hrm, I'm not seeing this bug anymore with recent F11 kernel builds, but I also changed laptop in the meanwhile (Thinkpad X60).
Comment 2 Cosimo Cecchi 2010-03-01 13:27:48 UTC 
I did not see this in a long while now.
Note You need to log in before you can comment on or make changes to this bug.