On 12/27/2010 02:08 PM, JB wrote:
First, make sure your system is up-to-date.
It is.
Here the Infos you requested:
[icehawk@icehawk-laptop linuxhome]$ lsmod |grep -i freq
cpufreq_ondemand 7262 0
acpi_cpufreq 6285 0
mperf 1141 1 acpi_cpufreq
[icehawk@icehawk-laptop linuxhome]$ sudo cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq(a)vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: *frequency should be within 1000 MHz and 1000 MHz.*
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: *frequency should be within 1000 MHz and 1000 MHz*.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
[icehawk@icehawk-laptop linuxhome]$ sudo cpufreq-set -c 1 --g userspace
-u 2000000
[icehawk@icehawk-laptop linuxhome]$ sudo cpufreq-set -c 0 --g userspace
-u 2000000
[icehawk@icehawk-laptop linuxhome]$ sudo cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq(a)vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: *frequency should be within 1000 MHz and 1000 MHz*.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, performance
current policy: *frequency should be within 1000 MHz and 1000 MHz.*
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
[icehawk@icehawk-laptop linuxhome]$ stress -t 30 -c 2 &
[1] 22884
[icehawk@icehawk-laptop linuxhome]$ stress: info: [22884] dispatching
hogs: 2 cpu, 0 io, 0 vm, 0 hdd
[icehawk@icehawk-laptop linuxhome]$ grep -i mhz /proc/cpuinfo
cpu MHz : 1000.000
cpu MHz : 1000.000
[icehawk@icehawk-laptop linuxhome]$ grep -i mhz /proc/cpuinfo
cpu MHz : 1000.000
cpu MHz : 1000.000
[icehawk@icehawk-laptop linuxhome]$ stress: info: [22884] successful run
completed in 30s
mfg
icehawk