Occasional CPU frequency scaling problems on AMD Turion
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Occasional CPU frequency scaling problems on AMD Turion
Hello,
I have an MSI M635 Megabook laptop, with Ubuntu Gutsy (kernel 2.6.22-14). After installation, powernowd and module powernow_k8 was installed automatically, and CPU frequency monitor in Gnome shows frequency changing from 800MHz to 2GHz depending on load. But after some (up)time (2-3 days), it starts to show 800MHz only, and I notice that PC becomes slow. I checked and found that /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq and /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq both contain 800000. When scaling works correctly, scaling_max_freq contains 2000000, as expected. I tried to unload and reload modules (powernow_k8, freq_table, cpufreq_powersave) - but after I load them back, again I see 800000 in both files, and scaling does not work. Is it a buggy bios, or what?
Thank you for detailed info! I will follow your recommendations if it fail again I suspected that the problems began since I installed and run GKrellM (not immediately after running it, but after some time of GKrellM being run). After last reboot I did not start it, and CPU works correctly since then (4 days).
When CPU was locked at 800MHz, the files contents were:
Perhaps you have a CPU freq modifier plugin in gkrellm which interferes. (I really doubt that) In case you have one remove that plugin and leave the kernel to decide.
Or more likely there is a problem with ondemand governor (for your kernel and hardware config). I would say switch to conservative and leave it like that forever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.