public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: 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: Thu, 22 Jun 2006 20:16:58 +0200	[thread overview]
Message-ID: <20060622181658.GA4193@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0606201156080.2481@yvahk01.tjqt.qr>

Hi!

> >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?).
> 
> K6 run cooler even with the regular kernel HLT (sti/hlt I presume). 
> Difference to full load can be up to 10 deg, depending on ambient (room) 
> temperature. In winter (read 2005-12-31) it ran between 28 celsius and 34 
> celsius. The fan even stopped and I thought it was a fan failure, but 
> luckily it was just hw-controlled :)

Okay, so you've got a point. The patch is useful on k6 in the winter
:-). (Actually, to show you've got a point, you'd have to stop the fan
and show that cpu badly overheats under for(;;) conditions).

Yes, we probably want to consolidate various for(;;) loops... and
maybe it will helpsomeone. If overheating causes reboot instead of
panic, you probably still loose, as BIOS is close to for(;;)...

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-06-22 18:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 19:15 [RFC/SERIOUS] grilling troubled CPUs for fun and profit? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=20060622181658.GA4193@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=davej@redhat.com \
    --cc=jengelh@linux01.gwdg.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