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)
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.
current CPU frequency is 1.20 GHz.
cpufreq stats: 2.53 GHz:0.00%, 2.53 GHz:0.00%, 2.40 GHz:0.00%, 2.27 GHz:0.00%, 2.13 GHz:0.00%, 2.00 GHz:0.00%, 1.87 GHz:0.00%, 1.73 GHz:0.00%, 1.60 GHz:0.00%, 1.47 GHz:0.00%, 1.33 GHz:0.00%, 1.20 GHz:100.00% (1)
-----------------
This used to work, I tried with an older 2.6.32-9 which I still have installed:
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 2.53 GHz.
-----------------
I am pretty sure that it stopped working not so long time ago, maybe around one or two months ago.
Trying to change the frequency using the 'Gnome CPU Frequency Scaling Monitor' tool does not change anything.
Note that I tried 2.6.36 from experimental, there it does not work as well.
thank you for your work,
Florian
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (maks@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010
** Kernel log:
[ 10.595958] i915 0000:00:02.0: irq 34 for MSI/MSI-X
[ 10.595964] [drm] set up 31M of stolen space
[ 10.598927] phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 10.621628] USB Serial support registered for Qualcomm USB modem
[ 10.623579] qcserial 2-1.4:1.2: Qualcomm USB modem converter detected
[ 10.623670] usb 2-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[ 10.623706] usbcore: registered new interface driver qcserial
[ 10.715542] Synaptics Touchpad, model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd047b1/0xb40000/0xa0000
[ 10.715546] serio: Synaptics pass-through port at isa0060/serio1/input0
[ 10.766898] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
[ 10.771315] usbcore: registered new interface driver snd-usb-audio
[ 10.781469] Linux video capture interface: v2.00
[ 10.839241] uvcvideo: Found UVC 1.00 device Integrated Camera (17ef:4816)
[ 10.840352] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input11
[ 10.840408] usbcore: registered new interface driver uvcvideo
[ 10.840411] USB Video Class driver (v0.1.0)
[ 11.442413] Console: switching to colour frame buffer device 160x50
[ 11.445417] fb0: inteldrmfb frame buffer device
[ 11.445418] registered panic notifier
[ 11.450874] acpi device:01: registered as cooling_device4
[ 11.451078] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[ 11.451129] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 11.451179] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 11.451220] HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 11.451258] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 12.064531] loop: module loaded
[ 12.572042] Adding 4882424k swap on /dev/mapper/debian-swap. Priority:-1 extents:1 across:4882424k
[ 13.149153] EXT4-fs (dm-4): mounted filesystem with ordered data mode
[ 13.186916] EXT4-fs (dm-1): mounted filesystem with ordered data mode
[ 14.245065] fuse init (API version 7.13)
[ 14.706348] e1000e 0000:00:19.0: irq 31 for MSI/MSI-X
[ 14.766253] e1000e 0000:00:19.0: irq 31 for MSI/MSI-X
[ 14.766726] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 15.974257] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input13
[ 16.315682] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
[ 16.315687] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 16.317967] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 17.555012] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 17.829047] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
[ 18.226507] Bluetooth: Core ver 2.15
[ 18.226553] NET: Registered protocol family 31
[ 18.226555] Bluetooth: HCI device and connection manager initialized
[ 18.226557] Bluetooth: HCI socket layer initialized
[ 18.266118] Bluetooth: L2CAP ver 2.14
[ 18.266120] Bluetooth: L2CAP socket layer initialized
[ 18.458993] Bluetooth: RFCOMM TTY layer initialized
[ 18.459001] Bluetooth: RFCOMM socket layer initialized
[ 18.459004] Bluetooth: RFCOMM ver 1.11
[ 18.981851] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.981856] Bluetooth: BNEP filters: protocol multicast
[ 19.587866] Bridge firewalling registered
[ 19.764887] Bluetooth: SCO (Voice Link) ver 0.6
[ 19.764892] Bluetooth: SCO socket layer initialized
[ 22.451383] lp: driver loaded but no devices found
[ 22.530190] ppdev: user-space parallel port driver
[ 26.953025] eth0: no IPv6 routers present
[ 47.221262] CPU0 attaching NULL sched-domain.
[ 47.221268] CPU1 attaching NULL sched-domain.
[ 47.221272] CPU2 attaching NULL sched-domain.
[ 47.221275] CPU3 attaching NULL sched-domain.
[ 47.248768] CPU0 attaching sched-domain:
[ 47.248774] domain 0: span 0-1 level SIBLING
[ 47.248778] groups: 0 (cpu_power = 589) 1 (cpu_power = 589)
[ 47.248787] domain 1: span 0-3 level MC
[ 47.248790] groups: 0-1 (cpu_power = 1178) 2-3 (cpu_power = 1178)
[ 47.248800] CPU1 attaching sched-domain:
[ 47.248803] domain 0: span 0-1 level SIBLING
[ 47.248807] groups: 1 (cpu_power = 589) 0 (cpu_power = 589)
[ 47.248814] domain 1: span 0-3 level MC
[ 47.248818] groups: 0-1 (cpu_power = 1178) 2-3 (cpu_power = 1178)
[ 47.248827] CPU2 attaching sched-domain:
[ 47.248830] domain 0: span 2-3 level SIBLING
[ 47.248833] groups: 2 (cpu_power = 589) 3 (cpu_power = 589)
[ 47.248840] domain 1: span 0-3 level MC
[ 47.248843] groups: 2-3 (cpu_power = 1178) 0-1 (cpu_power = 1178)
[ 47.248852] CPU3 attaching sched-domain:
[ 47.248855] domain 0: span 2-3 level SIBLING
[ 47.248858] groups: 3 (cpu_power = 589) 2 (cpu_power = 589)
[ 47.248866] domain 1: span 0-3 level MC
[ 47.248869] groups: 2-3 (cpu_power = 1178) 0-1 (cpu_power = 1178)
[ 891.877931] tun: Universal TUN/TAP device driver, 1.6
[ 891.877936] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 901.259237] tun0: Disabled Privacy Extensions
** Model information
sys_vendor: LENOVO
product_name: 3680A78
product_version: ThinkPad X201
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 6QET52WW (1.22 )
board_vendor: LENOVO
board_name: 3680A78
board_version: Not Available
** USB devices:
Bus 002 Device 003: ID 05c6:9205 Qualcomm, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 010: ID 0763:2003 Midiman M Audio AudioPhile
Bus 001 Device 008: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 001 Device 007: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard
Bus 001 Device 005: ID 17ef:4816 Lenovo
Bus 001 Device 004: ID 17ef:1005 Lenovo
Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii debconf [debconf 1.5.36 Debian configuration management sy
ii initramfs-tools 0.98.5 tools for generating an initramfs
ii linux-base 2.6.36-1~experimental.1 Linux image base package
ii module-init-tool 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-amd64 recommends:
ii firmware-linux-f 2.6.36-1~experimental.1 Binary firmware for various driver
Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
ii firmware-iwlwifi 0.27 Binary firmware for Intel Wireless
ii firmware-linux 0.27 Binary firmware for various driver
ii firmware-linux-nonfree 0.27 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20101114164504.5003.94078.reportbug@debian">http://lists.debian.org/20101114164504.5003.94078.reportbug@debian
11-14-2010, 04:21 PM
Ben Hutchings
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)
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.
[...]
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
11-14-2010, 04:30 PM
fbugs
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)
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.
>
#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
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CE01CB0.1000902@gmx.net">http://lists.debian.org/4CE01CB0.1000902@gmx.net
11-15-2010, 12:23 AM
Ben Hutchings
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)
On Sun, 2010-11-14 at 18:30 +0100, fbugs wrote:
[...]
> #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.
OK. I can't find any change that would explain this. Please submit a
bug upstream at <https://bugzilla.kernel.org> under product 'ACPI',
component 'Power-Processor', and include:
- The precise model of computer and processor.
- The last version that worked, i.e. Debian's version 2.6.32-9. You can
specify that this is close to stable version 2.6.32.9.
- The information from cpufreq-info and the result of writing to
scaling_max_freq.
Let us know the bug number or URL so we can track it.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
11-15-2010, 09:35 PM
Florian
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)
On 11/15/2010 02:23 AM, Ben Hutchings wrote:
> On Sun, 2010-11-14 at 18:30 +0100, fbugs wrote:
> [...]
>> #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.
>
> OK. I can't find any change that would explain this. Please submit a
> bug upstream at <https://bugzilla.kernel.org> under product 'ACPI',
> component 'Power-Processor', and include:
>
> - The precise model of computer and processor.
> - The last version that worked, i.e. Debian's version 2.6.32-9. You can
> specify that this is close to stable version 2.6.32.9.
> - The information from cpufreq-info and the result of writing to
> scaling_max_freq.
>
> Let us know the bug number or URL so we can track it.
>
> Ben.
>
Ok. Before I go to kernel.org's bugzilla: I have found out with the help
of snapshot.debian.org that the last working debian kernel version was
2.6.32-20:
---
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 2.53 GHz.
---
>From 2.6.32-21 on it stopped working. Does this help and/or shall I
anyway submit an upstream bug report?
thanks,
Florian
Lenovo ThinkPad X201, model 3680A78
ThinkPad BIOS 6QET52WW (1.22 ), EC 6QHT30WW-1.11
Intel Core i5 CPU M 540 @ 2.53GHz stepping 02
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CE1B5CF.3090207@gmx.net">http://lists.debian.org/4CE1B5CF.3090207@gmx.net
11-15-2010, 11:58 PM
Ben Hutchings
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)
On Mon, 2010-11-15 at 23:35 +0100, Florian wrote:
[...]
> Ok. Before I go to kernel.org's bugzilla: I have found out with the help
> of snapshot.debian.org that the last working debian kernel version was
> 2.6.32-20:
Oh, good thinking.
> ---
> 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 2.53 GHz.
> ---
>
> From 2.6.32-21 on it stopped working. Does this help and/or shall I
> anyway submit an upstream bug report?
Can you try booting with the additional kernel parameter 'ignore_ppc=1'?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
11-16-2010, 12:20 PM
Yves-Alexis Perez
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)
On dim., 2010-11-14 at 17:45 +0100, Florian wrote:
> 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.
>
Just to be sure, is the battery installed in the system or do you run
from AC without battery?
Cheers,
--
Yves-Alexis
11-16-2010, 05:33 PM
Florian
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)
Ben,
> Can you try booting with the additional kernel parameter 'ignore_ppc=1'?
Unfortunately this doesn't seem to make any difference, neither with
2.6.32 nor with 2.6.36...
Yves-Alexis,
>
> Just to be sure, is the battery installed in the system or do you run
> from AC without battery?
>
Good guess! I was running from AC without the battery installed. When I
install the battery, but continue to run from AC, it works again. What
is causing the problem then? I guess a workaround would be to install
some laptop tools to prevent a full load of the battery; is there
another solution?
thanks! Florian
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CE2CE8E.40309@gmx.net">http://lists.debian.org/4CE2CE8E.40309@gmx.net
11-16-2010, 05:42 PM
Yves-Alexis Perez
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)
On mar., 2010-11-16 at 19:33 +0100, Florian wrote:
> > Just to be sure, is the battery installed in the system or do you run
> > from AC without battery?
> >
>
> Good guess! I was running from AC without the battery installed. When I
> install the battery, but continue to run from AC, it works again. What
> is causing the problem then? I guess a workaround would be to install
> some laptop tools to prevent a full load of the battery; is there
> another solution?
It's not a problem, it's a way to protect your system. In some cases,
when fully loaded, the system draws too much power and your AC adaptor
(65W I guess) can't provide enough, so the system just crash. So when
the embedded controller detects that no battery is present and the 65W
adapter is used, it'll limit the max cpu frequency to prevent crashes.
See that thread about all this:
http://article.gmane.org/gmane.linux.hardware.thinkpad/40883
You really should always use your thinkpad *with* battery, and use
tp-smapi to keep the battery charge between 30-40% and 60-70%.
apt-get install tp-smapi-dkms to get the module
and http://www.thinkwiki.org/wiki/Tp_smapi for more info on this (what
you want is {start,stop}_charge_thresh).