From: Ken Ryan <linuxryan@leesburg-geeks.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC/SERIOUS] grilling troubled CPUs for fun and profit?
Date: Mon, 19 Jun 2006 23:30:53 -0400 [thread overview]
Message-ID: <44976BED.4050600@leesburg-geeks.org> (raw)
> > You accelerate nothing. Bit heaven? A CPU without a fan will go into
> > a cold, cold, shutdown, requiring a hardware reset to get it out of
> > that latched, no internal clock running, mode.
>
> Some CPU may do this, others will go via the random-generator mode
> into the self-deformation-mode instead.
A few years ago Tom's Hardware Guide made a cool video as part of an
article on thermal emergencies. The article is here:
http://www.tomshardware.com/2001/09/17/hot_spot/index.html
The test was pulling off the CPU fan and heatsink while playing Quake.
Granted it's not entirely realistic; I don't imagine the heatsink would
come of during heavy gameplay (a more reasonable scenario THG mentions
is the fan/heatsink coming off during shipping) however considering the
preposterous little tabs AMD specs for their sockets I think sudden
breakage is not out of the question.
The video shows a PIII coping (halting), a P4 gracefully slowing down,
and two variants of Athlon self-destructing (smoke and running solder).
Evidently this set of tests convinced AMD to alter how they handled
overtemp on their processors. The mobos in the test were built
according to spec in terms of the thermal sensors and protection code in
the BIOS. It didn't help; the exposed die of the Athlon ramped up its
temperature way faster than the sensor could react.
As for the ceramic package cracking, it is certainly possible, The
ceramic is indeed designed for very high temperatures, but only if
heated evenly. Give the package a 200C temperature differential within
a second or two and thermal expansion is going to do some damage...
I can certainly believe modern processors deal with sudden thermal rise
better than the ones in the THG video. However not all of us can afford
to always have the latest 'n' greatest... :-(
ken
next reply other threads:[~2006-06-20 3:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 3:30 Ken Ryan [this message]
[not found] <fa.pC0NfRl4O1eOCqPOBXy8f+7gbqU@ifi.uio.no>
[not found] ` <fa.so5wrYE6MzA2swzlOE1Xjw9iqvk@ifi.uio.no>
2006-06-19 23:32 ` [RFC/SERIOUS] grilling troubled CPUs for fun and profit? Robert Hancock
[not found] <6pxs2-1AR-5@gated-at.bofh.it>
[not found] ` <6pyer-2Pt-1@gated-at.bofh.it>
2006-06-19 21:40 ` Bodo Eggert
2006-06-19 21:44 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-06-19 19:15 Andreas Mohr
2006-06-19 19:39 ` John Richard Moser
2006-06-19 20:00 ` linux-os (Dick Johnson)
2006-06-19 20:23 ` Dave Jones
2006-06-19 20:47 ` linux-os (Dick Johnson)
2006-06-19 20:59 ` Dave Jones
2006-06-19 22:25 ` Pavel Machek
2006-06-19 22:41 ` Dave Jones
2006-06-20 11:39 ` linux-os (Dick Johnson)
2006-06-21 17:16 ` Ian Romanick
2006-06-21 17:57 ` linux-os (Dick Johnson)
2006-06-22 17:47 ` Pavel Machek
2006-06-20 9:58 ` Jan Engelhardt
2006-06-22 18:16 ` Pavel Machek
2006-06-23 17:32 ` Jan Engelhardt
2006-06-24 19:54 ` Pavel Machek
2006-06-25 11:01 ` Jan Engelhardt
2006-06-20 9:54 ` Jan Engelhardt
2006-06-19 21:16 ` Claudio Martins
2006-06-19 22:16 ` Pavel Machek
2006-06-19 22:43 ` Dave Jones
2006-06-20 7:29 ` Andreas Mohr
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=44976BED.4050600@leesburg-geeks.org \
--to=linuxryan@leesburg-geeks.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox