[Bug 849768] New: cpufrequtils application version 008-22.1.1.1 w/openSUSE 13.1 and appears Defective
https://bugzilla.novell.com/show_bug.cgi?id=849768 https://bugzilla.novell.com/show_bug.cgi?id=849768#c0 Summary: cpufrequtils application version 008-22.1.1.1 w/openSUSE 13.1 and appears Defective Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jmcdaniel3@austin.rr.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 In openSUSE 12.3 (cpufrequtils, version 008-19.1.1 ) if I run the terminal command on my laptop, it works properly: cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to http://bugs.opensuse.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. In openSUSE 13.1 (cpufrequtils, version 008-22.1.1 ) if I run the terminal command on my laptop, it works properly: cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to http://bugs.opensuse.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHhz. The governor "powersave" may decide which speed to use within this range. The info is incorrect and appears to be a problem in the package cpufrequtils, version 008-22.1.1 Reproducible: Always Steps to Reproduce: 1. open up terminal in openSUSE 12.3 2. type in cpufreq-info 3. open up terminal in openSUSE 13.1 4. type in cpufreq-info 5. Compare results Actual Results: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to http://bugs.opensuse.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHz. The governor "powersave" may decide which speed to use within this range. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 2.60 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 2.60 GHhz. The governor "powersave" may decide which speed to use within this range. Expected Results: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to http://bugs.opensuse.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 782 MHz - 1.70 GHz available frequency steps: 1.70 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz, 782 MHz available cpufreq governors: ondemand, performance current policy: frequency should be within 782 MHz and 1.70 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.70 GHz. I have a bash script to set CPU speed using cpufrequtils that works in openSUSE 12.3 and does not work in openSUSE 13.1 due to this defective YaST package. http://forums.opensuse.org/blogs/jdmcdaniel3/c-f-u-cpu-frequency-utilitiy-ve... -- 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=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c1
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c2
James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c3
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c4
James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c5
Thomas Renninger
So the max cpu speed is 1701 MHz as indicated on openSUSE 12.3 and not the random speeds shown in openSUSE 13.1. This probably is the speed the kernel thinks it's running at, please double check with cpupower monitor what the real max speed is (should already be avail with all you need in 12.3 as well).
-- 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=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c6
James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c7
--- Comment #7 from James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c8
--- Comment #8 from James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c9
Thomas Renninger
Available monitor Mperf needs root access Have you been root when executing this?
-- 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=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c10
James McDaniel
https://bugzilla.novell.com/show_bug.cgi?id=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c11
Thomas Renninger
From what I can see intel_pstate driver does things wrong. You CPUs can at least run at 2.4 GHz. You can utilize one core by doing: cat /dev/zero >/dev/null & and run cpupower monitor -m Mperf again. I expect you see one core running at 2.6 GHz all the whole time. As said these are average frequency values, therefore you see on a somewhat utilized core something between lowest and highest freq. ACPI P-state information looks totally wrong. You could also try to find the specs for your processor from Intel using CPU family and model from /proc/cpuinfo. On wikipedia you should find the exact processor name and possibly the spec. I expect the 0.8-2.6 GHz are correct.
-> It's the other way around. Things were (shown) wrong and are now fixed -> closing bug. -- 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=849768
https://bugzilla.novell.com/show_bug.cgi?id=849768#c12
--- Comment #12 from James McDaniel
http://bugzilla.novell.com/show_bug.cgi?id=849768
Al Sokol
participants (1)
-
bugzilla_noreply@novell.com