All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Webster <jw.jwebster@gmail.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Mattia Dongili <malattia@linux.it>, cpufreq@vger.kernel.org
Subject: Re: CPU throttled down to 800 after 15-30mins
Date: Mon, 07 Feb 2011 23:56:21 +0100	[thread overview]
Message-ID: <4D507895.70204@gmail.com> (raw)
In-Reply-To: <201102072055.38707.trenn@suse.de>

The BIOS is BIOS revision A05, which has not been updated since 2005.
The BIOS only has settings to turn speedstep on or off. If it is turned 
off then the computer will not run higher than 800MHz so that won't 
solve the issue.
I have attached the results below when it throttles down to 800 and the 
cpu limit says: 80000 but it starts off at 1733000.

The only thing it could be is a temperature sensor that has gone faulty. 
NHC in windows seems to be able to bypass this issue and ramp it up to 
1.73 but there doesn't seem to be an equivalent in Ubuntu that I know of.

when running at 1.73Ghz correctly:
j@j-Inspiron-9300:~$ date
Mon Feb  7 22:44:49 CET 2011
j@j-Inspiron-9300:~$ sudo cat 
/sys/devices/system/cpu/cpu0/cpufreq/bios_limit
1733000
j@j-Inspiron-9300:~$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
   driver: acpi-cpufreq
   CPUs which run at the same hardware frequency: 0
   CPUs which need to have their frequency coordinated by software: 0
   maximum transition latency: 10.0 us.
   hardware limits: 800 MHz - 1.73 GHz
   available frequency steps: 1.73 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
   available cpufreq governors: conservative, ondemand, userspace, 
powersave, performance
   current policy: frequency should be within 1.73 GHz and 1.73 GHz.
                   The governor "performance" may decide which speed to use
                   within this range.
   current CPU frequency is 1.73 GHz.
   cpufreq stats: 1.73 GHz:99.46%, 1.33 GHz:0.00%, 1.07 GHz:0.00%, 800 
MHz:0.54%  (16)

when limited to 800MHz:
j@j-Inspiron-9300:~$ date
Mon Feb  7 23:54:45 CET 2011
j@j-Inspiron-9300:~$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
   driver: acpi-cpufreq
   CPUs which run at the same hardware frequency: 0
   CPUs which need to have their frequency coordinated by software: 0
   maximum transition latency: 10.0 us.
   hardware limits: 800 MHz - 1.73 GHz
   available frequency steps: 1.73 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
   available cpufreq governors: conservative, ondemand, userspace, 
powersave, 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.
   cpufreq stats: 1.73 GHz:69.73%, 1.33 GHz:0.00%, 1.07 GHz:0.00%, 800 
MHz:30.27%  (17)
j@j-Inspiron-9300:~$ sudo cat 
/sys/devices/system/cpu/cpu0/cpufreq/bios_limit
800000





On 07/02/11 20:55, Thomas Renninger wrote:
> 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

  parent reply	other threads:[~2011-02-07 22:56 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
2011-02-07 21:41     ` Mattia Dongili
2011-02-07 22:56     ` J Webster [this message]
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=4D507895.70204@gmail.com \
    --to=jw.jwebster@gmail.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=malattia@linux.it \
    --cc=trenn@suse.de \
    /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.