From: Claudio Martins <ctpm@ist.utl.pt>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Andreas Mohr" <andi@rhlx01.fht-esslingen.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/SERIOUS] grilling troubled CPUs for fun and profit?
Date: Mon, 19 Jun 2006 22:16:19 +0100 [thread overview]
Message-ID: <200606192216.20355.ctpm@ist.utl.pt> (raw)
In-Reply-To: <Pine.LNX.4.61.0606191542050.4926@chaos.analogic.com>
On Monday 19 June 2006 21:00, linux-os (Dick Johnson) wrote:
> 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. Try it. I have had
> broken plastic heat-sink hold-downs let the entire heat-sink fall off
> the CPU. The machine just stops. I didn't know why it was stopping
That may well be true for Intel Pentium 4 and AMD Ahtlon64/Opteron CPUs but
it is definitely *not* what happens on older AMD CPUs. Actually we have had a
case of smoke coming out of a box when the heatsink fan on an Ahtlon XP CPU
stopped. You could still smell the burnt plastic from the socket the next day
in the room ;-)
And I personally know of a least another case with an Athlon XP.
I think Intel used to be better than AMD concerning CPU casing and the size
of the area in thermal contact with the heatsink, but not anymore.
Opteron/Athlon64 case seems to be at least as good as Intel's, and the chips
should now have thermal throttling, though I haven't tried it!
Regards
Cláudio
next prev parent reply other threads:[~2006-06-19 21:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-06-19 22:16 ` Pavel Machek
2006-06-19 22:43 ` Dave Jones
2006-06-20 7:29 ` Andreas Mohr
[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
[not found] <fa.pC0NfRl4O1eOCqPOBXy8f+7gbqU@ifi.uio.no>
[not found] ` <fa.so5wrYE6MzA2swzlOE1Xjw9iqvk@ifi.uio.no>
2006-06-19 23:32 ` Robert Hancock
2006-06-20 3:30 Ken Ryan
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=200606192216.20355.ctpm@ist.utl.pt \
--to=ctpm@ist.utl.pt \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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
all inboxes | Powered by JetHome®