Same problem here. Just upgraded from kernel 3.8 to kernel 3.10.1 and this bug has come up :(
cpufreq-info says:
vistausss@bodhimbp:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, 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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz. The governor "performance" 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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz. The governor "performance" 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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz. The governor "performance" 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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz. The governor "performance" may decide which speed to use within this range.
vistausss@bodhimbp:~$
Same problem here. Just upgraded from kernel 3.8 to kernel 3.10.1 and this bug has come up :(
cpufreq-info says:
vistausss@ bodhimbp: ~$ cpufreq-info
The governor "performance" may decide which speed to use
within this range.
The governor "performance" may decide which speed to use
within this range.
The governor "performance" may decide which speed to use
within this range.
The governor "performance" may decide which speed to use
within this range. bodhimbp: ~$
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, 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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz.
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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz.
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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz.
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: 1.20 GHz - 3.10 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 1.20 GHz and 3.10 GHz.
vistausss@