Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 171229 - CPU Frequency Scaling Monitor not working correctly after suspend
Summary: CPU Frequency Scaling Monitor not working correctly after suspend
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-17 10:03 UTC by jipmanvuong
Modified: 2008-05-27 18:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jipmanvuong 2007-03-17 10:03:56 UTC
When resuming from a suspend-to-ram (S3) the CPU Frequency Scaling Monitor does not work properly anymore for cpu1, while it still works for cpu0. Changes in the frequency are not shown anymore, while you can still use the applet to set speeds.

Reproducible: Always

Steps to Reproduce:
1. Add a cpufreq applet to the panel for CPU 1
2. Suspend to ram and resume
3. Do a watch -n 1 cat /proc/cpuinfo and try playing with the frequencies.


Actual Results:  
In the watch you'll see the frequencies changing, but not in the applet

Expected Results:  
Show correct frequencies

CPU INFO

vendor_id       : GenuineIntel
cpu family      : 6
model           : 14
model name      : Genuine Intel(R) CPU           T2300  @ 1.66GHz
stepping        : 8

NOTES

I have read bug 168685 , but I don't have symlinks in my sysfs. Also, it looks like I can set the frequency for both cores individually

Also, since I have cpu hotplug support (needed for the sleep states). It might be that the applet gets confused by that or something. Since (as far as I can tell from the suspend messages) CPU 1 is shut down when doing a suspend.
Comment 1 jipmanvuong 2007-03-17 10:06:00 UTC
Note. Without suspending, the applet works fine for both cores. 
Comment 2 Rémi Cardona (RETIRED) gentoo-dev 2008-05-27 18:27:49 UTC
Is this bug still an issue with recent kernels and gnome? If so, don't hesitate to reopen this bug with the versions of your kernel, gnome-panel, gnome-applets and hal.

Thanks