[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#517804: marked as done (base: CPU scaling for the 2nd core stops working after suspend to RAM)

Your message dated Thu, 4 Feb 2010 11:08:33 +0100
with message-id <20100204100833.GB9721@stro.at>
and subject line Re: Bug#517804: base: CPU scaling for the 2nd core stops working after suspend to RAM
has caused the Debian Bug report #517804,
regarding base: CPU scaling for the 2nd core stops working after suspend to RAM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
517804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517804
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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@dell:~$ cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@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@dell:~$ cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@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

--- End Message ---
--- Begin Message --- 
On Tue, 08 Dec 2009, Moritz Muehlenhoff wrote:

> 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


closing as no activity since inital report.
most probably fixed by newer 2.6.32 in squeeze, can be reopened
if reproducible with it.

thanks for the report.

--- End Message ---
Reply to: