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

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:
> > -----------
> > 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.
> 
> 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









Reply to: