[Bug 350805] New: CPU frequency throttling NOT supported with Processor ( CPU): AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ Speed: 2,511. 39 MHz Cores: 2
https://bugzilla.novell.com/show_bug.cgi?id=350805 Summary: CPU frequency throttling NOT supported with Processor (CPU): AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ Speed: 2,511.39 MHz Cores: 2 Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: alpha096@virginbroadband.com.au QAContact: qa@suse.de Found By: Customer CPU throttling is not supported with Processor (CPU): AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ Speed: 2,511.39 MHz Cores: 2 Boot log reports Loading CPUFreq modules (CPUFreq not supported) BIOS on Motherboard can revile hardware CPU and RAM current temperatures making adjustments to CPU and Case Cooling fan, however O/S boot indicated no control over throttling of CPU to prevent/enable throttling/overclocking of CPU. Motherboard States it features AMD Cool 'n' Quiet Technology - The Motherboard supports the AMD Cool 'n' quiet Technology, which monitors system operation.......automatically adjusts CPU voltage and frequency..... This could indicate that O/S is functioning as designed an allowing BIOS and CPU to control throttling/overclocking - In this case please adjust Bug report as follows.Consider boot message should reflect if CPU and BIOS can be identified as controlling frequency the boot message change from Loading CPUFreq modules (CPUFreq not supported) to Loading CPUFreq modules (CPUFreq supported by Hardware) in such cases to remove alarm from other users. In this case please downgrade bug to normal/minor. -- 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=350805
User dmuhamedagic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c1
Dejan Muhamedagic
https://bugzilla.novell.com/show_bug.cgi?id=350805
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c2
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c3
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User dmuhamedagic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c4
--- Comment #4 from Dejan Muhamedagic
https://bugzilla.novell.com/show_bug.cgi?id=350805
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c5
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c6
--- Comment #6 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User dmuhamedagic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c7
--- Comment #7 from Dejan Muhamedagic
https://bugzilla.novell.com/show_bug.cgi?id=350805
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c8
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=350805
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c9
--- Comment #9 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c10
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
User dmuhamedagic@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c11
--- Comment #11 from Dejan Muhamedagic
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c12
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c13
--- Comment #13 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c14
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c15
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c16
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=350805
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c17
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=350805
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350805#c18
Thomas Renninger
let the user know in a clearer way that we aren't able to control the CPU frequency even though the CPU supports them and that they should take a look at the BIOS. I do not think this is a good idea or say, not that easy to do. We rely on the BIOS to export specific ACPI functions (on latest ia64/i386/x86_64 archs). If they are not exported by the BIOS (as done in this case -> wait for a BIOS update supporting your brandnew CPUs) we can only guess by CPU family/model or read some other CPU registers, but I don't think it is a good idea (you will get wrong messages on some machines pretty sure if you try to double check whether CPU freq should be supported...).
I doubt that M$ will support cpufreq on that machine also. The user must be clever enough to look for a feature. If it doesn't work, look at the vendor's site, browse the BIOS updates, often there are "new CPUs supported" (or similar) stated, etc. -- 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.
participants (1)
-
bugzilla_noreply@novell.com