Package: acpid Version: 1.0.6-10 Severity: grave Justification: renders package unusable
Even with hal turned off and gnome-power and all that crap not being installed, I have up until recently had laptop-mode-tools as the sole controller of my laptop's power management. laptop_mode is of course controlled through /etc/acpi/actions/lm_*. Lately, something has been limiting my CPU to 800Mhz only, when I go to battery: AC: > cpufreq-info | grep 'should be within' current policy: frequency should be within 800 MHz and 2.20 GHz. battery: > cpufreq-info | grep 'should be within' current policy: frequency should be within 800 MHz and 800 MHz. The CPU governor remains on ondemand. If I disable the calls to lm_* within the acpi directory, or if I tell laptop_mode to not touch anything CPU related (despite it being configged not to limit the CPU in such fashion), and even if I uninstall it, something is still telling the CPU to limit to 800MHz. So it's not laptop_mode. I don't have other cpufreq related tools installed (except cpufrequtils, which doesn't run anything that might change the governor behaviour on the fly). If I remove the acpi directory, then the goveror is still changed. If I stop the acpid daemon, then the govenor *isn't* changed. As I can't see anything else being run by acpid, it must therefore be acpi itself at fault, do you agree? Is there anything new that acpid is doing behind our back to change the CPU goveronr? Below, I show the order of events - first I generate an strace output on acpi, tail the strace output once things have settled down, unplug the laptop and terminate the logging once acpi has started polling for the next acpi event: 0-0-12:49:26, Fri Jul 18 [EMAIL PROTECTED]:/etc/acpi (bash) 51307,131> strace -o /tmp/acpi.txt -f /etc/init.d/acpid restart .... 0-0-13:03:26, Fri Jul 18 [EMAIL PROTECTED]:/home/tconnors (bash) > cpufreq-info | grep 'should be within' current policy: frequency should be within 800 MHz and 2.20 GHz. current policy: frequency should be within 800 MHz and 2.20 GHz. 0-0-13:03:38, Fri Jul 18 [EMAIL PROTECTED]:/home/tconnors (bash) 51301,42> tail -f /tmp/acpi.txt > /tmp/acpi-to-batt ################################### #unplug laptop here, and wait a bit ################################### ^C 130-0-13:03:50, Fri Jul 18 [EMAIL PROTECTED]:/home/tconnors (bash) 51302,43> cpufreq-info | grep 'should be within' current policy: frequency should be within 800 MHz and 800 MHz. current policy: frequency should be within 800 MHz and 800 MHz. The 330K of strace output has been placed on my webserver: http://rather.puzzling.org/~tconnors/tmp/acpi-to-batt I can't see anything incriminating in there, but since disabling acpi is sufficient to stop this happening, it must be in there somewhere... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages acpid depends on: ii libc6 2.7-12 GNU C Library: Shared libraries ii lsb-base 3.2-15 Linux Standard Base 3.2 init scrip ii module-init-tools 3.4-1 tools for managing Linux kernel mo acpid recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
