From: Thomas Renninger <trenn@suse.de>
To: Mattia Dongili <malattia@linux.it>
Cc: J Webster <jw.jwebster@gmail.com>, cpufreq@vger.kernel.org
Subject: Re: CPU throttled down to 800 after 15-30mins
Date: Mon, 7 Feb 2011 20:55:38 +0100 [thread overview]
Message-ID: <201102072055.38707.trenn@suse.de> (raw)
In-Reply-To: <20110206044123.GB2703@kamineko.org>
On Sunday 06 February 2011 05:41:23 Mattia Dongili wrote:
> Note that this is a kernel development related list, if your problem is
> specific to cpufreqd (note the "d" for deamon, a userspace application)
> please write/reply to me only or to cpufreqd related mailing lists.
>
> On Sat, Feb 05, 2011 at 08:56:26PM +0100, J Webster wrote:
> > My laptop is an Inpsiron 9300, which should be able to go up to 1.73GHz.
> > I am having an issue whereby when I first turn the computer on,
> > ondemand is selected and the speed moves between 800 and 1.73
> > successfully.
> > For no apparent reason, after 15mins it is throttled back to 800 and
> > I cannot change it back.
> > I tired manually editing the scaling_max_freq file to 1733000 but
> > when I go back to view it it has changed to 800000 again!
> > I thought it might be this issue:
> > ##
> > # Special Rules
> > ##
> > # CPU Too hot!
> > [Rule]
> > name=CPU Too Hot
> > acpi_temperature=55-100
> > cpu_interval=50-100
> > profile=Performance Low
> > [/Rule]
> >
> > So I changed it from 70-100 but on the last try the cpu did not
> > reach 70 and it still throttled it back to 800.
>
> Try to increase cpufreqd verbosity, it will tell you which and why a
> specific rule was selected. From there you can work on modifying your
> rules to better match your usage.
Also check whether your BIOS is the reason, if you get 800000 here:
/sys/devices/system/cpu/cpu0/cpufreq/bios_limit
you should check your BIOS settings.
Thomas
next prev parent reply other threads:[~2011-02-07 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 19:56 CPU throttled down to 800 after 15-30mins J Webster
2011-02-06 4:41 ` Mattia Dongili
2011-02-07 19:55 ` Thomas Renninger [this message]
2011-02-07 21:41 ` Mattia Dongili
2011-02-07 22:56 ` J Webster
2011-02-08 1:36 ` Michael Reinelt
2011-02-08 7:50 ` J Webster
2011-02-08 11:22 ` J Webster
2011-02-09 19:17 ` J Webster
2011-02-09 19:37 ` Thomas Renninger
2011-02-09 19:43 ` J Webster
2011-02-09 19:50 ` 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=201102072055.38707.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=jw.jwebster@gmail.com \
--cc=malattia@linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.