From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-52128-garchives=archives.gentoo.org@gentoo.org>)
id 1GThip-0003Kc-OP
for garchives@archives.gentoo.org; Sat, 30 Sep 2006 16:29:52 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8UGSh8k007517;
Sat, 30 Sep 2006 16:28:43 GMT
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185])
by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8UGOU8a003318
for <gentoo-user@lists.gentoo.org>; Sat, 30 Sep 2006 16:24:30 GMT
Received: by nf-out-0910.google.com with SMTP id p46so1641807nfa
for <gentoo-user@lists.gentoo.org>; Sat, 30 Sep 2006 09:24:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
b=gwL+9Fv66YG7HQcaGYwTGWw0O99iNdOjrJIGhzSjfQ+wRajgR2WmNwcGPf9fk8q64kyMuv3Snx//TtkFRrecqebt4ZpUtPTatsSsOwW+6Bf6yQQd6VlvP1dI3FUtoUGEHUpAOwqKVaaTkaYT/dfqUroUSF7ySEh452tnfsXW/wA=
Received: by 10.82.111.8 with SMTP id j8mr90559buc;
Sat, 30 Sep 2006 09:24:29 -0700 (PDT)
Received: by 10.82.126.14 with HTTP; Sat, 30 Sep 2006 09:24:29 -0700 (PDT)
Message-ID: <7573e9640609300924u40a61a59t8fbdf06f5bad4bd8@mail.gmail.com>
Date: Sat, 30 Sep 2006 09:24:29 -0700
From: "Richard Fish" <bigfish@asmallpond.org>
Sender: richard.j.fish@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT overheat] How to cause shutdown on overheat
In-Reply-To: <87r6xtmtwf.fsf@newsguy.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <87r6xtmtwf.fsf@newsguy.com>
X-Google-Sender-Auth: 32b32f0573be024d
X-Archives-Salt: dd2e34f6-b0d4-48d0-b325-cb9468b6e7e4
X-Archives-Hash: 4a416ad8cb1a35f9cea1ec7765df7257
On 9/30/06, reader@newsguy.com <reader@newsguy.com> wrote:
> 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?
Nope, not the kernel. Modern CPUs have built-in thermal
throttling...if they get too hot, they reduce their clocks until
things cool down. They generate an exception when this occurs, which
the kernel sees and logs if you have the right ACPI options enabled.
They will also simply shutdown if the temperature gets too warm.
However, this would generally be bad, as no clean shutdown or even
disk sync would occur.
> Further, how can I discover what temperatures were involved when this
> happened?
Download the processor specs from the manufacturer's web site....that
should list the throttle and shutdown temperatures.
> Or can I set something to make a shutdown happen at a specific
> temperature?
Install and run acpid, and you should get ACPI temperature events
passed through to /etc/acpi/default.sh, which you can edit to handle
in whatever way you see fit.
-Richard
--
gentoo-user@gentoo.org mailing list