[Bug 436717] New: CPU locked to lowest available frequency (SMP kernel only )
https://bugzilla.novell.com/show_bug.cgi?id=436717 Summary: CPU locked to lowest available frequency (SMP kernel only) Product: openSUSE 11.1 Version: Beta 2 Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mdrolc@gmail.com QAContact: qa@suse.de Found By: Beta-Customer CPU frequency scaling is limited in range from 800MHz to 800MHz (according to output from cpufreq-info) and system is very slow (installation of Beta2 version took about 4 hours). This bug happens only when SMP is enabled. With SMP disabled with 'nosmp' option at boot, frequency scaling works OK, but I'm limited to one core. Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-65 System detects available frequencies: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 1800000 1600000 800000 But the following command shoud output 1800000: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 800000 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436717
Michal Seben
https://bugzilla.novell.com/show_bug.cgi?id=436717
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c1
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436717
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c2
Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c3
--- Comment #3 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c4
--- Comment #4 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c5
--- Comment #5 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c6
--- Comment #6 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c7
Thomas Renninger
This bug has made it into 11.1 GM Hey guys, I set the prio to 1, this is the maximum I can set it to. There was no answer for a month. I really like to find the root cause, if you also do and you are willing to invest a bit of time, let's track this one down in the next year. An update kernel for 11.1 should pop up pretty soon. Thanks.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436717
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c8
--- Comment #8 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c9
--- Comment #9 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c10
Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c11
Robert Davies
despite my Dell Inspiron 531 being certified for SLED/SLES This one is certified? Then we should have one somewhere around, I try to find
From your initial bug description: But the following command shoud output 1800000: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 800000 It looks like we have more than a sampling or say cpufreq algorithm problem. If scaling_max_freq is lowered to the lowest the dynamic freq algorithm can't do anything and cur_freq will always stay at lowest. It looks like you only run into this sometimes (maybe this got fixed with the latest BIOS?)? If not set through a BIOS option (you might want to check your BIOS configs),
https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c12
Thomas Renninger
while (true); do cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq | grep -v 1000000; done you might want to use: watch -n1 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq} to monitor current and maximum frequency. watch -n1 refreshes the output every second.
For the algorithm: I want to look closer at this, but did not have the time yet. The load threshold when to switch up the frequency and a patch series for improved sampling on no_hz kernels I'd still like to test for SLE11 (which would get integrated/backported into 11.1 then also). Benchmarking power vs performance is time consuming, but we have some nice tools now and I hope to be able to work on that soon. For this bug report I'd only like to examine the situation when max_freq gets lowered. Do you use libsensors? This might falsify ACPI temperature readings and could cause the kernel to lower max_freq, due to wrong, high temperature values. If you could reproduce when/why max_freq gets lowered (or if at all with the new BIOS), this would be great. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c13
--- Comment #13 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=436717#c18 Thomas Renningerchanged: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #18 from Thomas Renninger 2009-01-13 16:18:35 MST --- We have a system, but cannot reproduce the problem. This is all about the initial description: > But the following command shoud output 1800000: > cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq > 800000 I expect that this is due to: - A bad BIOS config (unlikely, would be fixed high freq, if e.g. PowerNow is switched off, maybe you even have a fixed low BIOS option accidently enabled) - An old broken BIOS If you should still run into this with latest BIOS, try to find a way to reproduce it and reopen the bug. Robert: About general cpufreq performance is currently looked at, but the bug is about frequency being stuck totally at lowest freq -> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c19
--- Comment #19 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c23
--- Comment #23 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c24
--- Comment #24 from Robert Davies
https://bugzilla.novell.com/show_bug.cgi?id=436717
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c25
--- Comment #25 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c26
--- Comment #26 from Robert Davies
participants (1)
-
bugzilla_noreply@novell.com