From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Allow userspace do something special on overtemp
Date: Thu, 12 Aug 2004 22:22:58 -0600 [thread overview]
Message-ID: <00fe01c480ed$36a08330$6401a8c0@northbrook> (raw)
In-Reply-To: fa.g1p407b.1c569pj@ifi.uio.no
----- Original Message -----
From: "Pavel Machek" <pavel@suse.cz>
Newsgroups: fa.linux.kernel
To: "Len Brown" <len.brown@intel.com>
Cc: "Dax Kelson" <dax@gurulabs.com>; <trenn@suse.de>; <seife@suse.de>;
"Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Thursday, August 12, 2004 5:25 PM
Subject: Re: Allow userspace do something special on overtemp
> Ouch and btw I've done some torturing on one prototype (AMD). It had
> thermal at 98Celsius (specs for this cpu said 95C max), and I ended my
> test at 105Celsius. I do not know about TM1/TM2 etc, but in this case
> hardware clearly failed to do the right thing.
This is dependent on the CPU/motherboard in use - AMD CPUs (up to the last
ones I heard about, anyway) don't have any built in thermal protection, they
rely on the motherboard to shut down the CPU in the event of
over-temperature. Intel CPUs since the Pentium II all shut down on excessive
over-temperature; Pentium 4s will also clock-throttle to continue operating
before they get to this point.
next parent reply other threads:[~2004-08-13 4:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fd8nc62.oig6ao@ifi.uio.no>
[not found] ` <fa.g1p407b.1c569pj@ifi.uio.no>
2004-08-13 4:22 ` Robert Hancock [this message]
2004-08-11 8:53 Allow userspace do something special on overtemp Pavel Machek
2004-08-11 9:03 ` Arjan van de Ven
2004-08-11 9:06 ` Pavel Machek
2004-08-11 14:49 ` Len Brown
2004-08-11 14:52 ` Wichert Akkerman
2004-08-11 15:28 ` Thomas Renninger
2004-08-11 21:08 ` Kronos
2004-08-11 20:26 ` Pavel Machek
2004-08-11 9:18 ` Måns Rullgård
2004-08-11 18:22 ` Olaf Hering
[not found] ` <411A239C.8060606@blue-labs.org>
2004-08-11 20:22 ` Pavel Machek
2004-08-12 0:08 ` Dax Kelson
2004-08-12 3:29 ` Len Brown
2004-08-12 7:40 ` Pavel Machek
2004-08-12 14:28 ` Len Brown
2004-08-12 20:24 ` Pavel Machek
2004-08-12 22:51 ` Len Brown
2004-08-12 23:21 ` Pavel Machek
2004-08-12 7:35 ` Pavel Machek
2004-08-12 15:19 ` Len Brown
2004-08-12 15:16 ` Randy.Dunlap
2004-08-12 15:50 ` Stefan Seyfried
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='00fe01c480ed$36a08330$6401a8c0@northbrook' \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.