Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
Hi, I am not the OP but I have the same problem, in my case affecting a Dell Latitude D830 running linux-image-2.6.26-2-686 (lenny). In fact for me the first CPU seemed to be stuck on lowest CPU frequency as well after I resumed. I wasn't able to test with kernel 2.6.32 because, though it boots and suspends to RAM, it will not resume for me. I hazard a guess that some userspace tools might need upgrading from my Lenny versions. However I can confirm that the problem was already fixed in 2.6.30, as thanks to your hints I have now tested using the backports.org kernel 2.6.30-bpo.2-686, and suspend-to-RAM now no longer causes the second CPU to lose scaling. I think this is the applicable kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=10734 I hope the confirmation is useful. Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
On Sat, Sep 12, 2009 at 08:26:42PM +0200, Moritz Muehlenhoff wrote: On Mon, Mar 02, 2009 at 09:57:36AM +0300, Vladimir Zamiussky wrote: Package: base Severity: normal I don't exactly know wether this bug related to base system or to linux kernel or cpufreq subsystem I'm using cpufreq for dynamic CPU scaling on my notebook Dell D630. After resuming from suspend2ram cpu scaling is lost for core #1. Below is the cpufreq-info output before and after suspend2ram: --- v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. - v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU manual reloading acpi_cpufreq kernel module helps to turn CPU 1 scaling on. Could you try a 2.6.30 kernel from backports.org? Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
On Mon, Mar 02, 2009 at 09:57:36AM +0300, Vladimir Zamiussky wrote: Package: base Severity: normal I don't exactly know wether this bug related to base system or to linux kernel or cpufreq subsystem I'm using cpufreq for dynamic CPU scaling on my notebook Dell D630. After resuming from suspend2ram cpu scaling is lost for core #1. Below is the cpufreq-info output before and after suspend2ram: --- v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. - v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU manual reloading acpi_cpufreq kernel module helps to turn CPU 1 scaling on. Could you try a 2.6.30 kernel from backports.org? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
reassign 517804 linux-2.6 thanks Hi Vladimir, thanks for your bugreport. base is definitly the wrong package :) I'm also not sure if this is really linux-2.6 or uswsusp or initramfs-tools to reassign at, so I'm reassigning to the kernel people as I'm confident they know better than me ;-) (Thanks for that, too!) regards, Holger On Montag, 2. März 2009, Vladimir Zamiussky wrote: Package: base Severity: normal I don't exactly know wether this bug related to base system or to linux kernel or cpufreq subsystem I'm using cpufreq for dynamic CPU scaling on my notebook Dell D630. After resuming from suspend2ram cpu scaling is lost for core #1. Below is the cpufreq-info output before and after suspend2ram: --- v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. - v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU manual reloading acpi_cpufreq kernel module helps to turn CPU 1 scaling on. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: This is a digitally signed message part.
Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
Package: base Severity: normal I don't exactly know wether this bug related to base system or to linux kernel or cpufreq subsystem I'm using cpufreq for dynamic CPU scaling on my notebook Dell D630. After resuming from suspend2ram cpu scaling is lost for core #1. Below is the cpufreq-info output before and after suspend2ram: --- v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. - v...@dell:~$ cpufreq-info cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@lists.linux.org.uk, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.20 GHz available frequency steps: 2.20 GHz, 2.20 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 800 MHz and 2.20 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU manual reloading acpi_cpufreq kernel module helps to turn CPU 1 scaling on. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
