From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Dave Jones <davej@redhat.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/SERIOUS] grilling troubled CPUs for fun and profit?
Date: Tue, 20 Jun 2006 09:29:33 +0200 [thread overview]
Message-ID: <20060620072933.GA3030@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060619224312.GB17134@redhat.com>
Hi,
[whoa, maybe I shouldn't have used such an inflammatory subject,
the mail volume would suggest that ;-)]
On Mon, Jun 19, 2006 at 06:43:12PM -0400, Dave Jones wrote:
> On Tue, Jun 20, 2006 at 12:16:55AM +0200, Pavel Machek wrote:
>
> > > Am I completely missing something here?
> >
> > Yes. You are missing that modern hw already protects itself. See my blog on planet.kernel.org.
>
> And you are missing that not everyone is running linux on the latest CPUs.
Darn right. Intel has been having thermal protection for a somewhat longer
time, but Athlon had serious issues with missing or incompletely functioning
thermal sensors on many not too outdated (let's say it was 4 years ago, ok?)
motherboard/CPU combos.
And I don't really want to know about thermal protection status of various
Cyrix, VIA or even Winchip CPUs (you've been a nic^H^Hïve believer of
competition in a healthy marketplace and bought some of those, right?
I know I did... ;).
But since Pavel's blog mentions that thermal protection is an ACPI
specification, there's hope that it may actually work half-decently
after all.
Andreas Mohr
next prev parent reply other threads:[~2006-06-20 7:29 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
2006-06-19 22:16 ` Pavel Machek
2006-06-19 22:43 ` Dave Jones
2006-06-20 7:29 ` Andreas Mohr [this message]
[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=20060620072933.GA3030@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome