Bug#733545: Processed (with 1 errors): Re: Bug#733545: Fails to set profiles
On Mon, Dec 30, 2013 at 04:30:33AM +0100, Ben Hutchings wrote:
> Which scaling driver is being used?
acpi-cpufreq
> Which scaling governor are you using?
ondemand
> What was the last kernel version where this worked?
I don't know, I usually just leave ondemand do it's work without
interfering. I looked at this because of the bugreport sent to cpufreqd.
below the output of cpufreq-info that includes stats. The oddity is
these two frequencies:
1801000 1800000
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.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: 800 MHz - 1.80 GHz
available frequency steps: 1.80 GHz, 1.80 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
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.80 GHz:0.00%, 1.80 GHz:6.45%, 1.70 GHz:0.36%, 1.60 GHz:0.15%, 1.50 GHz:0.14%, 1.40 GHz:0.12%, 1.30 GHz:0.17%, 1.20 GHz:0.20%, 1.10 GHz:0.19%, 1000 MHz:0.26%, 900 MHz:0.29%, 800 MHz:91.68% (18673)
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: 800 MHz - 1.80 GHz
available frequency steps: 1.80 GHz, 1.80 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
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.80 GHz:0.00%, 1.80 GHz:12.74%, 1.70 GHz:1.08%, 1.60 GHz:0.35%, 1.50 GHz:0.11%, 1.40 GHz:0.16%, 1.30 GHz:0.19%, 1.20 GHz:0.20%, 1.10 GHz:0.21%, 1000 MHz:0.35%, 900 MHz:0.46%, 800 MHz:84.15% (18075)
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: 800 MHz - 1.80 GHz
available frequency steps: 1.80 GHz, 1.80 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
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.80 GHz:0.00%, 1.80 GHz:3.03%, 1.70 GHz:0.38%, 1.60 GHz:0.30%, 1.50 GHz:0.29%, 1.40 GHz:0.26%, 1.30 GHz:0.25%, 1.20 GHz:0.22%, 1.10 GHz:0.37%, 1000 MHz:0.47%, 900 MHz:0.45%, 800 MHz:93.99% (12177)
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: 800 MHz - 1.80 GHz
available frequency steps: 1.80 GHz, 1.80 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
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.80 GHz:0.00%, 1.80 GHz:4.84%, 1.70 GHz:0.59%, 1.60 GHz:0.34%, 1.50 GHz:0.31%, 1.40 GHz:0.24%, 1.30 GHz:0.20%, 1.20 GHz:0.25%, 1.10 GHz:0.28%, 1000 MHz:0.28%, 900 MHz:0.28%, 800 MHz:92.40% (14871)
--
mattia
:wq!
Reply to: