[Virtual-pkg-base-maintainers] Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM

[Holger Levsen]

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:
> -----------
> vlad at dell:~$ cpufreq-info
> cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to cpufreq at 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.
> -------------------------------------
> vlad at dell:~$ cpufreq-info
> cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to cpufreq at 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


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/virtual-pkg-base-maintainers/attachments/20090302/54ab80c6/attachment.pgp