public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 14:39:54 -0400	[thread overview]
Message-ID: <20060811183954.GH26930@redhat.com> (raw)
In-Reply-To: <44DCCB96.5080801@rtr.ca>

On Fri, Aug 11, 2006 at 02:25:26PM -0400, Mark Lord wrote:
 > One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor.
 > This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
 > 
 > I use speedstep-centrino with it, and after boot all is usually okay.
 > But after a few hours of operation, it stops shifting to the highest frequency
 > even under continuous 100% load (or not).  Eventually it gets stuck at 600Mhz
 > and stays there until I reboot.
 > 
 > Sometimes rebooting doesn't even restore it.
 > 
 > /sys/devices/system/cpu/cpu0/cpufreq is all very normal looking,
 > showing the available frequencies and other info.  All of the attribs
 > there look fine, except for "scaling_max_freq", which is what seems
 > to gradually get set smaller.  For instance, right now it is set to 800000,
 > and it won't let me change it (echo 11000000 > scaling_max_freq has no effect.
 > 
 > WHY?  And how can I fix it?

boot with cpufreq.debug=7, and capture dmesg output after it fails
to transition.  This might be another manifestation of the mysterious
"highest frequency isnt accessable" bug, that seems to come from
some recent change in acpi.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-08-11 18:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 18:25 cpufreq stops working after a while Mark Lord
2006-08-11 18:39 ` Dave Jones [this message]
2006-08-11 19:41   ` Mark Lord
2006-08-11 20:01     ` Mark Lord
2006-08-11 20:12       ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01   ` Mark Lord
2006-08-11 19:10   ` Mark Lord
2006-08-11 19:18     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 19:55 Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39   ` Mark Lord
2006-08-11 21:01     ` Dave Jones
2006-08-11 21:09       ` Mark Lord
2006-08-11 21:15       ` Mark Lord
2006-08-11 21:17         ` Mark Lord
2006-08-11 21:25         ` Mark Lord
2006-08-18 15:11           ` Pavel Machek
2006-08-24 14:44             ` Mark Lord
2006-08-24 16:15               ` Matthew Garrett
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 21:38 Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
2006-08-11 22:18 Pallipadi, Venkatesh

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=20060811183954.GH26930@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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