public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Jensen <c-acpi-s2nexXcBJu3PC4JL755TaA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: ACPI Thermal Shutdown on Boot
Date: Tue, 10 Feb 2004 17:48:21 +1100	[thread overview]
Message-ID: <200402101748.21855.c-acpi@drspirograph.com> (raw)

Hi,
I've got a couple of problems with the ACPI thermal support in 2.6.2

I'm trying to install kernel 2.6.2. However, as soon  as the kernel starts 
init, I get a message along the lines of "Critical Temperature reached - 57C, 
shutting down" and init switches to runlevel 0.
(I got the same behaviour trying to install 2.6.1, but without the message 
telling me why)

The system had been powered on for 2 days straight, so I think it's safe to 
keep it running at that temp, I'd like to keep the thermal protection 
compiled into the kernel to protect against a really high temperature should 
a fan fail etc, so I'd like to adjust the critical temperature so it doesn't 
shutdown.

How can I adjust the critical temperature? I realise that there's a file 
in /proc that can be adjusted, but as init is shutting down immediately, 
there doesn't seem to be an oportunity to do this.


The other issue is that although the kernel said the temperature was 57C, if I 
reboot and jump into the BIOS settings, it says its 67C, so there seems to be 
some discrepency there.

I'm using a Gigabyte motherboard with a VIA KT133 chipset (VT82C686).
It has a shutdown threshold in the BIOS settings, which I've tried increasing, 
but it didn't help.

-- 
Chris Jensen
chris-s2nexXcBJu3PC4JL755TaA@public.gmane.org

Public Key: http://drspirograph.com/public_key/

Wait: Did you know that there's a direct correlation between the decline of
Spirograph and the rise in gang activity?  Think about it.
- Dr Spirograph (The Simpsons)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

             reply	other threads:[~2004-02-10  6:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10  6:48 Chris Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11  3:51 ACPI Thermal Shutdown on Boot 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-12  2:52 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB6A6-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-13 19:06   ` Pavel Machek
     [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

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=200402101748.21855.c-acpi@drspirograph.com \
    --to=c-acpi-s2nexxcbju3pc4jl755taa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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