public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: jfrey-Mmb7MZpHnFY@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
Subject: Re: ACPI throttling to death?
Date: Thu, 07 Apr 2005 13:12:34 +0200	[thread overview]
Message-ID: <425515A2.3080103@suse.de> (raw)
In-Reply-To: <200504051813.28983.jfrey-Mmb7MZpHnFY@public.gmane.org>

Jan Frey wrote:
> On Tuesday 05 April 2005 18:38, Stefan Dösinger wrote:
>>Am Montag, 4. April 2005 20:14 schrieb Jan Frey:
>>>Hi,
>>>
>>>I'm observing strange behaviour with a Gericom notebook running a
>>>2.6.9 vanilla kernel with custom configuration. The processor used is
>>>a P III (Tualatin) with 1.2GHz (which is quite rarely used). It is
>>>*not* a mobile processor (no speedstep etc.), instead it supports 16
>>>throttling levels.
>>>
>>>Sometimes (I guess when the machine is getting overheated - the
>>>notebook design is really bad and the fan is quite lousy) ACPI
>>>temperature monitor shows >70 degrees (Celsius) and the system starts
>>>throttling.
>>>
>>>Until here everything is fine IMO.
>>>But what happens next is that the systems slows down continuously (you
>>>can monitor the current throttling level going up and up) until it
>>>reaches the last level (12%). Soon after that the whole machine is
>>>locked up hard, display still showing the current graphics. I guess it
>>>throttled to a "deathly" 0%...
>>>
>>>Is this more a linux acpi problem or a fault in this particular
>>>machine? What could be done about it? how can I debug further?
>>My desktop machine locked up if it got to hot(70-75 degrees, amd duron
>>processor). I bought a better CPU fan and the problem is gone. Well,
>>that's impossible on notebooks.
>>
>>Is there a 0% throttling level? What happens if you stop processor
>>hungry tasks to allow the machine to cool down?
> 
> No, there is no 0% level. Unfortunately this also does not seem to be 
> related to any level of CPU utilization: sometimes the machines locks up 
> even if it is nearly idle, e.g. writing/sending email...
> 
> Really astonishing: CPU temperature seems to go up to roughly 70 degrees 
> quite quickly and then it stays there nearly forever: it does not matter 
> whether CPU load is 0 or 1.. And: throttling also does not lower CPU temp, 
> I thought this would be main reason...

The temperature is fixed to exactly 70 C?
I saw machines where a fixed temperature is returned depending on some bit/byte
in EC/SystemIO.
Sounds like this one does the same?
You'll find out by going back the _TMP code in the DSDT.
The value should be about 0xD66 ((70+273)*10, right?)

     Thomas


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

  parent reply	other threads:[~2005-04-07 11:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 20:14 ACPI throttling to death? Jan Frey
     [not found] ` <200504042214.15648.jfrey-Mmb7MZpHnFY@public.gmane.org>
2005-04-05 15:59   ` Bruno Ducrot
     [not found]     ` <20050405155910.GT2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-05 16:16       ` Jan Frey
2005-04-05 16:38   ` Stefan Dösinger
     [not found]     ` <200504051638.22705.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-04-05 16:13       ` Jan Frey
     [not found]         ` <200504051813.28983.jfrey-Mmb7MZpHnFY@public.gmane.org>
2005-04-05 18:08           ` Bruno Ducrot
     [not found]             ` <20050405180826.GU2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-05 20:23               ` Jan Frey
     [not found]                 ` <200504052223.17547.jfrey-Mmb7MZpHnFY@public.gmane.org>
2005-04-06 14:19                   ` Bruno Ducrot
     [not found]                     ` <20050406141923.GZ2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-08  9:53                       ` Jan Frey
     [not found]                         ` <200504081153.30624.janfrey-S0/GAf8tV78@public.gmane.org>
2005-04-08 10:10                           ` Bruno Ducrot
     [not found]                             ` <20050408101028.GH2298-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-04-08 10:34                               ` Bruno Ducrot
2005-04-07 11:12           ` Thomas Renninger [this message]
     [not found]             ` <425515A2.3080103-l3A5Bk7waGM@public.gmane.org>
2005-04-07 11:41               ` Jan Frey
2005-04-07 13:12               ` Bruno Ducrot
2005-09-22  9:46 ` Matthias Otto

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=425515A2.3080103@suse.de \
    --to=trenn-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=jfrey-Mmb7MZpHnFY@public.gmane.org \
    --cc=stefandoesinger-RbZlAiThDcE@public.gmane.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