public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT overheat] How to cause shutdown on overheat
Date: Sat, 30 Sep 2006 10:13:51 -0300	[thread overview]
Message-ID: <342e1090609300613x2a7e52aeoc9a4f4aeae8eda31@mail.gmail.com> (raw)
In-Reply-To: <87r6xtmtwf.fsf@newsguy.com>

On 9/30/06, reader@newsguy.com <reader@newsguy.com> wrote:
> Group, I recently built a ventilated stucture around my 4 desktops to
> try to quiet things down and get rid of the heat.
>
> I made no provision for forced shutdown in case of overheat, which is
> quite likely to happen if, for example the main ventilation fan went
> down for some reason.
>
> Well, that happened due to stupidity on my part with getting used to
> the new setup.  I fired up a computer and neglected to turn the fan
> on.  Then left it running overnight.
>
> Well, given the confined space and very little/no ventilation (of my
> homemade structure) the computer got hot...
>
> Sometime this morning I see syslog messages written to tty that say:
>
>   Message from syslogd@reader at Sat Sep 30 04:41:32 2006 ...
>   reader kernel: CPU0: Temperature above threshold
>
>   Message from syslogd@reader at Sat Sep 30 04:41:32 2006 ...
>   reader kernel: CPU0: Running in modulated clock mode
>
> [...]
>
> Some kind of attempt by kernel to cool things down.  But will it
> actually shutdown if it gets dangerously hot?
>
> Further, how can I discover what temperatures were involved when this
> happened?
>
> Or can I set something to make a shutdown happen at a specific
> temperature?
>
> A nicer solution would be somekind of added stand alone temperature
> monitor in the enclosure that causes a controlled shutdown like one
> gets with `shutdown -h now'.
>
> Anyone here with some experience in this kind of thing that can steer me
> to some good information?
>

If you have built your kernel with ACPI options for THERMAL or some
kind of frequency changer, you can use a daemon like cpufreqd to
monitor the temperature and take actions like reduce the clock and
voltage to avoid damage to the processor.

http://www.gentoo.org/doc/en/power-management-guide.xml

When my computer reaches the limit (wich in my case is 73 degrees C)
it automatically shutdown, I didn't have to configure anything, it is
builtin with the thermal ACPI module. I'm talking about a Pentium IV
Northwood here, and they tend to get really hot. It used to happen to
my Athlon XP also... To monitor the temperature, you can read the
/proc entries created by ACPI, for example
/proc/acpi/thermal/TZ0/info.

-- 
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-30 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 12:16 [gentoo-user] [OT overheat] How to cause shutdown on overheat reader
2006-09-30 13:13 ` Daniel da Veiga [this message]
2006-09-30 16:24 ` Richard Fish
2006-10-01 16:31 ` Michael Gisbers
2006-10-12 12:56   ` Joost Roeleveld

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=342e1090609300613x2a7e52aeoc9a4f4aeae8eda31@mail.gmail.com \
    --to=danieldaveiga@gmail.com \
    --cc=gentoo-user@lists.gentoo.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