public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
	Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI Thermal Shutdown on Boot
Date: Fri, 13 Feb 2004 20:06:46 +0100	[thread overview]
Message-ID: <20040213190646.GH6804@openzaurus.ucw.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401CBB6A6-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hi!

> > > If I understand you correctly, 30 seconds is certainly 
> > enough time to burn
> > > a CPU when the fan has failed, isn't it?
> > 
> > Our old default poll interval was 30 seconds so this doesn't change
> > anything.  I know DeadRat takes more than 30 seconds from "shutdown -h
> > now" to power off.  All modern CPUs have a thermal shutdown builtin.
> > Think of _CRT as more of "system temp too high, shut down as 
> > soon as you
> > can."
> 
>   If I didn't miss something,  Chris Jensen was unable to adjust
> critical trip point due
> to current policy. Anyway, 57C isn't a real critical temperature. It
> doesn't make sense to
> enter emergent shutdown/power.So we need sane checking here.( A sane
> _CRT ?)
>   If FAN is broken, at least we can use throttling to guarantee it will
> not be over heated.
> So, throttling should be included into policy about handling critical
> trip point.

At critical trip point, we have to shut down, according
to specs. No choice here.

If their ACPI BIOS is b0rken, blacklist them.
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-02-13 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12  2:52 ACPI Thermal Shutdown on Boot Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6A6-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-13 19:06   ` Pavel Machek [this message]
     [not found]     ` <20040213190646.GH6804-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-02-15 20:24       ` Nate Lawson
     [not found]         ` <20040215122249.V20266-Y6VGUYTwhu0@public.gmane.org>
2004-02-15 20:29           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11  3:51 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB690-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-11  6:01   ` Nate Lawson
     [not found]     ` <20040210215906.H85854-Y6VGUYTwhu0@public.gmane.org>
2004-02-11 10:59       ` Karol Kozimor
     [not found]         ` <20040211105908.GB30647-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-02-11 17:48           ` Nate Lawson
2004-02-10  6:48 Chris Jensen

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=20040213190646.GH6804@openzaurus.ucw.cz \
    --to=pavel-alswssmvlrq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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