Bug#603487: linux-image-2.6.32-5-amd64: CPU runs on lowest frequency only, does not increase anymore on demand (as it used to do before)

[fbugs <fbugs@gmx.net>]

On 11/14/2010 06:21 PM, Ben Hutchings wrote:
> On Sun, 2010-11-14 at 17:45 +0100, Florian wrote:
>> Package: linux-2.6
>> Version: 2.6.32-27
>> Severity: important
>> Tags: squeeze
>>
>>
>> Since some kernel versions the CPU frequency always stays at its lowest value (in my case, on a Intel i5 M540,
>> this is 1.2 GHz). I have a Lenovo Thinkpad X201 with newest BIOS installed.
>>
>>  cpufreq-info tells me:
>>
>> -----------------
>> 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.53 GHz
>>   available frequency steps: 2.53 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: conservative, powersave, userspace, ondemand, performance
>>   current policy: frequency should be within 1.20 GHz and 1.20 GHz.
>>                   The governor "ondemand" may decide which speed to use
>>                   within this range.
> [...]
> 
> Does frequency scaling work again if you run:
> 
> 	echo 2530000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
> 
> Ben.
> 

No.


#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1199000
#echo 2530000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1199000

#cpufreq-info | grep "hardware limits\|current policy"
  hardware limits: 1.20 GHz - 2.53 GHz
  current policy: frequency should be within 1.20 GHz and 1.20 GHz.



thanks, Florian