public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adachi, Kenichi" <aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org>
To: 'Faye Pearson' <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: constant processor 0x80 events
Date: Wed, 1 Jan 2003 21:30:25 +0900	[thread overview]
Message-ID: <000101c2b191$93b74130$2d2202d3@sayonara> (raw)
In-Reply-To: <20021231211259.GA28810-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>

> When the machine becomes under load for a while, or is hot 
> already and the processor is under load, then the CPU time in 
> system becomes very high, /proc/acpi/event is constantly 
> printing: processor CPU0 00000080 00000000 processor CPU0 
> 00000080 00000000 processor CPU0 00000080 00000000
> 
Your system board triggers GPE upon some hardware condition (most likely
thermal in your case) and GPE handler for that event (run by OS) issues
Notify 0x80 on processor object. This eventually causes OS to reevaluate
your _PPC object to flip the highest performance state (P-State) of your
processor and update the supported P-State table.

I suspect that, on your machine, first current temperature crosses the
trip point (not for passive/active cooling but for P-State update), the
newly selected lower P-State cools down the box for a while, but sooner
or later it starts to heat again, ending up under the "yo-yo" situation.
This might bring about high CPU demand for repeated event handling.  

 
> I added this CHTR call (it wasn't being called before) and 
> that seems to stave off the problem for a while.. while 
> programs are running, there isn't a steady rise in 
> temperature, the temperature is seemingly all over the place. 
>  It will get up to 82 and then suddenly drop to 59. Even when 
> the load is going mad now, the fan is only on its high, not 
> critical level.
> 
It looks to me like your CHTR ("CH"ange "TR"ip point?) method adjusts
(enable/disable) trip point for P-State update depending on the passed
Arg0 and the caller of this CHTR Method is expected to pass current
temperature. If so, adding a call to CHTR in _TMP could make sense to
some extent. It dynamically changes trip point for P-State update and
somehow keeps box from overheating, resulting in the cooler and quiet
environment. But we can't be sure unless we have input from BIOS writer.


BTW, your BIOS seemingly doesn't support active cooling, that possibly
means the control of FAN is done by hardware modules and not exposed to
OS. Which make/model is your machine?




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-01-01 12:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 21:12 constant processor 0x80 events Faye Pearson
     [not found] ` <20021231211259.GA28810-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-01 12:30   ` Adachi, Kenichi [this message]
     [not found]     ` <000101c2b191$93b74130$2d2202d3-F8JvWDuGsZU@public.gmane.org>
2003-01-01 13:55       ` Adachi, Kenichi
2003-01-01 16:40       ` 'Faye Pearson'
     [not found]         ` <20030101164052.GA31172-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-01 17:58           ` Adachi, Kenichi
     [not found]             ` <20030101192644.GA31476@clara.net>
     [not found]               ` <20030101192644.GA31476-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 10:15                 ` Faye Pearson
     [not found]                   ` <20030102101513.GA947-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 13:52                     ` Adachi, Kenichi
2003-01-02 13:59                     ` Faye Pearson
     [not found]                       ` <20030102135937.GA9257-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-01-02 17:29                         ` Adachi, Kenichi
     [not found]                           ` <000201c2b284$89a033c0$232202d3-F8JvWDuGsZU@public.gmane.org>
2003-01-02 22:03                             ` Faye Pearson

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='000101c2b191$93b74130$2d2202d3@sayonara' \
    --to=aileenja-dtzodq2u+/yavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=faye-6JSjyQ0Qj1ReoWH0uzbU5w@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