cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq limits avilable frequencies to 800MHz on git kernel
Date: Fri, 23 May 2008 18:25:07 -0700	[thread overview]
Message-ID: <20080523182507.29a2b10c.akpm@linux-foundation.org> (raw)
In-Reply-To: <200805231944.57320.arekm@maven.pl>

On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz <arekm@maven.pl> wrote:

> thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git from 
> 1-2 days ago. 
> 
> Unfortunately it seems that suspend to ram/resume causes frequency
> to be limited to 800MHz only. I can't set it to 2GHz again :-/
> 
> scaling_max_freq is then 800000 and cannot be changed.
> 
> reboot and the problem disappears until new suspend/resume cycle.
> 
> cpufreq stuff is driven by acpi-cpufreq
> 
> $ cpufreq-info
> cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to linux@brodo.de, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which need to switch frequency at the same time: 0
>   hardware limits: 800 MHz - 2.00 GHz
>   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
>   available cpufreq governors: powersave, userspace, 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.
> 
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:2000000 
> 1600000 1333000 1066000 800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersave 
> userspace ondemand performance
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>

Thanks.  Is this a newly-occurring bug or did earlier kernels do this also?

If it was newly added, do you know in which kernel version we might
have added it?

  reply	other threads:[~2008-05-24  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 17:44 cpufreq limits avilable frequencies to 800MHz on git kernel Arkadiusz Miskiewicz
2008-05-24  1:25 ` Andrew Morton [this message]
2008-05-25  9:36   ` Arkadiusz Miskiewicz
2008-05-25 15:03     ` Thomas Renninger
2008-05-26  7:07       ` Arkadiusz Miskiewicz
2008-05-26 11:37         ` Thomas Renninger
2008-05-26 16:15           ` Arkadiusz Miskiewicz
2008-05-26 16:23             ` Arkadiusz Miskiewicz
2008-07-17 13:48               ` [PATCH] " Thomas Renninger
2008-07-17 21:40                 ` Andrew Morton
2008-07-18  2:46                   ` Thomas Renninger
2008-07-18 10:41                 ` Laurence Darby
2008-07-18 10:36                   ` Thomas Renninger
2008-07-18 11:38                     ` Laurence Darby
2008-05-27  9:35             ` Thomas Renninger
2008-05-26 12:28         ` Thomas Renninger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080523182507.29a2b10c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arekm@maven.pl \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox