Bug#491394: More information
I just received this additional information from Farokh Khajuee: -- Hi Regarding this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491394 I found a solution. It is a bug for Dell not Linux. http://woolie.co.uk/technology/dell-laptop-stuck-at-800mhz-ubuntu-fix Farokh -- Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491394: [Pkg-acpi-devel] Bug#491394: My system limited to 800 MHz and 800 MHz too
On Tue, Jun 22, 2010 at 07:19:44AM +1000, Mark Purcell wrote: Happy to help with any further details/ debug required. Again, I honestly doubt that acpid is at fault here as I cannot see a way for acpid to influence this behaviour. Please restart your system with acpid disabled and configured to not load any module. Then load the modules one at a time and check the frequency setting. Once all modules are loaded you can start acpid to see whether that causes any change but I wouldn't be surprised if insmod'ing one of the modules causes the problem. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491394: My system limited to 800 MHz and 800 MHz too
Package: acpid Version: 1:2.0.6-1 Severity: normal I too am seeing this issue on an HP Compaq 6710b: $ cpufreq-info cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@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: 800 MHz - 2.40 GHz available frequency steps: 2.40 GHz, 2.40 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor userspace may decide which speed to use within this range. current CPU frequency is 800 MHz. 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: 800 MHz - 2.40 GHz available frequency steps: 2.40 GHz, 2.40 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, conservative, ondemand, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor userspace may decide which speed to use within this range. current CPU frequency is 800 MHz. Happy to help with any further details/ debug required. Mark -- System Information: Debian Release: squeeze/sid APT prefers maverick APT policy: (500, 'maverick'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpid depends on: ii libc62.11.2-1Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.1Linux Standard Base 3.2 init scrip ii module-init-tools3.12~pre2-3 tools for managing Linux kernel mo Versions of packages acpid recommends: ii acpi-support-base 0.136-4scripts for handling base ACPI eve acpid suggests no packages. -- Configuration Files: /etc/default/acpid changed: MODULES=all -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491394: Does the bug still exist?
On Tue, 17 Feb 2009, Michael Meskes wrote: Does the bug still exist? I still cannot see how acpid itself can cause this problem. However, I could see a module being the culprit, although it should not stop when acpid is stopped then. Still exists (kernel 2.6.30) Anyway, if the problem is still there, could you please disable automatic module loading by acpid (/etc/default/acpid, should be disabled in newer version anyway). Yep, that's the case here. Also, if stopping acpid stops that behaviour, does it come back if you restart acpid with an empty /etc/acpi? Now it gets confusing. If I stop acpid, then the bug still exists now. I haven't tried freshly booting without allowing acpid to start. I could have sworn this was the case in the past, and now I can't find any processes running that I would point a suspicious finger towards. Also, it doesn't happen on a nearly identical install (but concievably I could have hacked acpi in a different way there) on a differnt dell laptop (dell vostro 1710 doesn't change its clock, whereas an dell inspiron 1520 does) Well, I don't know that this is an acpid bug, but damned if I know what's at fault, and my workaround still works... -- TimC We are no longer the knights who say ni We are the knights who say icky icky (Comet) Ikeya-Zhang zoooboing! --Lord Ender on /. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491394: Does the bug still exist?
Does the bug still exist? I still cannot see how acpid itself can cause this problem. However, I could see a module being the culprit, although it should not stop when acpid is stopped then. Anyway, if the problem is still there, could you please disable automatic module loading by acpid (/etc/default/acpid, should be disabled in newer version anyway). Also, if stopping acpid stops that behaviour, does it come back if you restart acpid with an empty /etc/acpi? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491394: acpid causes CPUfreq to be limited to 800MHz - 800Mhz
I now suspect the hardware to be at fault - insufficient power to run process at higher speeds rather then acpid My normal power supply connector is not operating and I have to power the laptop via a docking station. The cheap generic (non-dell) power supply is aging and now appears to be not supplying enough power to power the laptop and the docking station. On boot-up I get a warning regarding insufficent power and have the the load the BIOS using battery power. This is related to other users experiences, [1][2] 1: http://bugs.archlinux.org/task/10106 2: https://bugzilla.redhat.com/show_bug.cgi?id=+403651 Regards, Brendan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: acpid causes CPUfreq to be limited to 800MHz - 800Mhz
On Mon, 18 Aug 2008, Brendan Sleight wrote: I now suspect the hardware to be at fault - insufficient power to run process at higher speeds rather then acpid My normal power supply connector is not operating and I have to power the laptop via a docking station. The cheap generic (non-dell) power supply is aging and now appears to be not supplying enough power to power the laptop and the docking station. On boot-up I get a warning regarding insufficent power and have the the load the BIOS using battery power. This is related to other users experiences, [1][2] 1: http://bugs.archlinux.org/task/10106 2: https://bugzilla.redhat.com/show_bug.cgi?id=+403651 Not mine, however. Note also that I can and do manually set the max frequency back to 2201MHz by tweaking /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq by invoking 'laptop_mode force auto'. -- TimC 'Vegetarian' -- it's an old Indian word meaning 'lousy hunter'. -- Red Green 'tofu' -- Old Eskimo word. Means whale snot. -- GB in ASR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: acpid causes CPUfreq to be limited to 800MHz - 800Mhz
2008/8/18 Tim Connors wrote: invoking 'l e auto'. Thanks for the suggestion, however this does not work for me. Regards, Brendan [EMAIL PROTECTED]:~$ sudo laptop_mode force auto Laptop mode enabled, active [EMAIL PROTECTED]:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 1.60 GHz available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz available cpufreq governors: powersave, userspace, conservative, ondemand, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. cpufreq stats: 1.60 GHz:0.00%, 1.33 GHz:0.00%, 1.07 GHz:0.00%, 800 MHz:100.00% [EMAIL PROTECTED]:~$ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: acpid causes CPUfreq to be limited to 800MHz - 800Mhz
Package: acpid Version: 1.0.6-10 Followup-For: Bug #491394 If the problem exists on more systems please report. Also affecting my fresh installation of testing. On AC power, No battery available - Dell Latitude D410 cpufreq-info is limited 800 MHz to 800 MHz [EMAIL PROTECTED]:/tmp$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 1.60 GHz available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz available cpufreq governors: powersave, userspace, conservative, ondemand, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor performance may decide which speed to use within this range. current CPU frequency is 800 MHz. cpufreq stats: 1.60 GHz:0.00%, 1.33 GHz:0.00%, 1.07 GHz:0.00%, 800 MHz:[EMAIL PROTECTED]:/tmp$ [EMAIL PROTECTED]:/tmp$ sudo cpufreq-set -u 1.60 GHz [EMAIL PROTECTED]:/tmp$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 1.60 GHz available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz available cpufreq governors: powersave, userspace, conservative, ondemand, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor performance may decide which speed to use within this range. current CPU frequency is 800 MHz. cpufreq stats: 1.60 GHz:0.00%, 1.33 GHz:0.00%, 1.07 GHz:0.00%, 800 MHz:[EMAIL PROTECTED]:/tmp$ [EMAIL PROTECTED]:/tmp$ Suggest Severity - grave ? Regards, Brendan -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages acpid depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii lsb-base 3.2-12 Linux Standard Base 3.2 init scrip ii module-init-tools 3.4-1 tools for managing Linux kernel mo acpid recommends no packages. acpid suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: hardware?
On Fri, 25 Jul 2008 10:15:16 +0200, Marco Cogoni [EMAIL PROTECTED] wrote: I checked on my thinkpad X31 and this does not happen, everything works as expected. I am using pure testing. so it should be some interaction with other packages. I have deliberately never installed anything from gnome or kde, and have rigourously checked every other package that might conceivably affect cpufreq. It may be a hardware interaction. I tried installing a new bios after this bug appeared, but that doesn't change any behaviour. I ended up installing a workaround in battery.d: ( ( sleep 20 ; laptop_mode force auto ) /tmp/powerchange.txt 21 ) The long sleep seems to be necessary, since something is not only causing a jump to 800Mhz as soon as the power is unplugged, but something causes it to jump to 800MHz 10 seconds afterwards too. So 10 seconds after that, I force laptop_mode to apply its policy again (it having already applied it 20 seconds earlier, if I didn't say force, then it would just exit immediately, thinking the policy is still currently applied), which is the conservative governor, and the full 800-2201Mhz speed range. I tried strace -f on the acpid process, but nothing enlightening in the gobs of logs. Still, I'm pretty sure this didn't happen in the past, and I hadn't done an upgrade of the bios until after this all started happening. -- TimC The only thing more dangerous than a hardware guy with a code patch is a programmer with a soldering iron. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394:
severity 491394 important tag 491394 moreinfo tag 491394 unreproducible thanks As it seems this bug is not easily reproducable I downgrade it to important so it doesn't affect Lenny's release cycle. If the problem exists on more systems please report. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: (no subject)
hi, I checked on my thinkpad X31 and this does not happen, everything works as expected. I am using pure testing. so it should be some interaction with other packages. marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491394: acpid causes CPUfreq to be limited to 800MHz - 800Mhz
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]
