From: Pavel Machek <pavel@ucw.cz>
To: Dave Jones <davej@redhat.com>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/SERIOUS] grilling troubled CPUs for fun and profit?
Date: Tue, 20 Jun 2006 00:25:29 +0200 [thread overview]
Message-ID: <20060619222528.GC1648@openzaurus.ucw.cz> (raw)
In-Reply-To: <20060619202354.GD26759@redhat.com>
Hi!
> > Try it. I have had
> > broken plastic heat-sink hold-downs let the entire heat-sink fall off
> > the CPU. The machine just stops.
>
> Your single datapoint is just that, a single datapoint.
> There are a number of reported cases of CPUs frying themselves.
> Here's one: http://www.tomshardware.com/2001/09/17/hot_spot/page4.html
> Google no doubt has more.
>
> Another anecdote: Upon fan failure, I once had an athlon MP *completely shatter*
> (as in broke in two pieces) under extreme heat.
>
> This _does_ happen.
If it happens to you... you needed a new cpu anyway. Anything non-historical
*has* thermal protection.
BTW I doubt those old athlons can be saved by cli; hlt . (Someone willing to try if old
athlon can run cli; hlt code w/o heatsink?).
And no, we probably do not want to enter C2 or C3 from doublefault handler.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2006-06-19 22:32 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 [this message]
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
[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=20060619222528.GC1648@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=davej@redhat.com \
--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®