You are not logged in.
Hi.
As said I have an i5 480m in my laptop:
available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHzSo I have this in my cpufreq config:
chris@chrisl ~ % cat /etc/conf.d/cpufreq
#configuration for cpufreq control
# valid governors:
# ondemand, performance, powersave,
# conservative, userspace
governor="ondemand"
# limit frequency range (optional)
# valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="1.20GHz"
max_freq="2.67GHz"
# use freq to set up the exact cpu frequency using it with userspace governor
#freq=
chris@chrisl ~ %Yet the CPU cores never reach 1.20 GHz.
chris@chrisl ~ % LC_ALL=C cpufreq-info
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 1 2 3
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.67 GHz
available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 1.20 GHz and 2.67 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.33 GHz.
cpufreq stats: 2.67 GHz:4.40%, 2.67 GHz:0.06%, 2.53 GHz:0.13%, 2.40 GHz:0.04%, 2.27 GHz:0.06%, 2.13 GHz:0.07%, 2.00 GHz:0.02%, 1.87 GHz:0.05%, 1.73 GHz:0.03%, 1.60 GHz:0.09%, 1.47 GHz:0.16%, 1.33 GHz:94.89%, 1.20 GHz:0.00% (1073)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.67 GHz
available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 1.20 GHz and 2.67 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 2.40 GHz.
cpufreq stats: 2.67 GHz:3.30%, 2.67 GHz:0.03%, 2.53 GHz:0.00%, 2.40 GHz:0.03%, 2.27 GHz:0.00%, 2.13 GHz:0.04%, 2.00 GHz:0.04%, 1.87 GHz:0.01%, 1.73 GHz:0.02%, 1.60 GHz:0.30%, 1.47 GHz:0.09%, 1.33 GHz:96.13%, 1.20 GHz:0.00% (635)
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.67 GHz
available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 1.20 GHz and 2.67 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.33 GHz.
cpufreq stats: 2.67 GHz:2.98%, 2.67 GHz:0.03%, 2.53 GHz:0.00%, 2.40 GHz:0.04%, 2.27 GHz:0.02%, 2.13 GHz:0.01%, 2.00 GHz:0.02%, 1.87 GHz:0.01%, 1.73 GHz:0.03%, 1.60 GHz:0.08%, 1.47 GHz:0.11%, 1.33 GHz:96.67%, 1.20 GHz:0.00% (857)
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.67 GHz
available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 1.20 GHz and 2.67 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.33 GHz.
cpufreq stats: 2.67 GHz:2.26%, 2.67 GHz:0.04%, 2.53 GHz:0.00%, 2.40 GHz:0.00%, 2.27 GHz:0.01%, 2.13 GHz:0.02%, 2.00 GHz:0.04%, 1.87 GHz:0.00%, 1.73 GHz:0.02%, 1.60 GHz:0.04%, 1.47 GHz:0.10%, 1.33 GHz:97.47%, 1.20 GHz:0.00% (508)
chris@chrisl ~ %I don't think the power saving between 1.20GHz and 1.33 GHz would be that big but still it bugs me that it doesn't reach 1.20 GHz ever.
powertop looks like that:
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 0.0%) 2.67 Ghz 0.2%
polling 2.2ms ( 0.0%) 2.40 Ghz 0.2%
C1 mwait 0.1ms ( 0.0%) 2.00 Ghz 0.2%
C2 mwait 0.8ms ( 0.5%) 1466 Mhz 0.3%
C3 mwait 10.9ms (102.9%) 1333 Mhz 98.7%
Wakeups-from-idle per second : 101.4 interval: 5.0s
Power usage (ACPI estimate): 11.9W (3.4 hours)
Top causes for wakeups:
30.3% ( 36.0) kworker/0:1
21.0% ( 25.0) kworker/0:0
16.5% ( 19.6) [ath9k] <interrupt>
10.6% ( 12.6) [kernel scheduler] Load balancing tick
4.2% ( 5.0) [ahci] <interrupt>
3.4% ( 4.0) xfce4-systemloa
2.2% ( 2.6) thunderbird-bin
1.9% ( 2.2) tilda
1.7% ( 2.0) xfce4-netload-p
1.3% ( 1.6) soffice.bin
1.3% ( 1.6) [kernel core] hrtimer_start (tick_sched_timer)
0.8% ( 1.0) kworker/0:2
0.8% ( 1.0) xfce4-orageclocSo I see no reason why it shouldn't go to 1.20 GHz.
Is this a bug in the cpufreq display? Or does the CPU report false possible frequencies?
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline