After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 414897 - cpufreq applet doesn`t work correctly when processor is turned offline and than turned online
cpufreq applet doesn`t work correctly when processor is turned offline and th...
Status: RESOLVED DUPLICATE of bug 356694
Product: gnome-applets
Classification: Other
Component: cpufreq
2.16.x
Other All
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-05 13:27 UTC by matezz
Modified: 2007-03-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description matezz 2007-03-05 13:27:39 UTC
Please describe the problem:
On core2duo (T5500) processor when system suspends the second core (CPU1) of the processor is turned offline and than after "waking up" online again. Cpufreq applet monitoring this cpu is not able to cope with this and it continues showing the status of this core before suspending. 
One can change governors via applet on this core, but the applet does not show the correct frequency nor the correct governor.
The first core (CPU0) applet works correctly

Steps to reproduce:
1. suspend computer with core2duo and wake it up
2. try to change governors of the second core using cpufreq applet 
3. check the real governor and frequency of this core


Actual results:
applet continues to show the frequency an governor which was actual before suspend, you can change governors via applet, but nor the frequency nor the governor are not shown correctly

Expected results:
i would expect changing governors and frequencies folowed by changing governors and frequencis in the UI of the applet

Does this happen every time?
yes

Other information:
Comment 1 Carlos Garcia Campos 2007-03-05 13:45:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 356694 ***