cpu frequency governer does not change cpu frequency after hibernation and comeback
http://bugzilla.kernel.org/show_bug.cgi?id=9181
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|power- |[email protected] |management_other@kernel- | |bugs.osdl.org | Component|Hibernation/Suspend |cpufreq
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9181
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
------- Comment #1 from [email protected] 2007-10-20 11:47 ------- Can you try a bit more.., e.g.:
does it work with ondemand governor
after conservative governor broke, does switching to other governors, e.g. powersave, performance still work?
These are the easy to test..., if you know how to compile and a kernel it would be great if you could test the latest 2.6.23.1 or -git kernel. Then also enable CONFIG_CPU_FREQ_DEBUG=y (or similar), boot with cpufreq.debug=7 (or enable it at runtime: "echo 7 >/sys/module/cpufreq/parameters/debug") and attach syslog/klog output.
Not sure, but I think I saw a report with ondemand governor breaking away after suspend..., I try to find it.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9181
------- Comment #2 from [email protected] 2007-10-21 06:41 ------- This bug is a duplicate of #8581. If you're alright with compiling your own kernel, please try the patch I've uploaded to fix #8581.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.