From: Bodo Eggert <7eggert@elstempel.de>
To: "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: Mon, 19 Jun 2006 23:40:46 +0200 [thread overview]
Message-ID: <E1FsRUZ-0001Ll-0K@be1.lrz> (raw)
In-Reply-To: <6pyer-2Pt-1@gated-at.bofh.it>
linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
> On Mon, 19 Jun 2006, Andreas Mohr wrote:
>> while looking for loop places to apply cpu_relax() to, I found the
>> following gems:
>>
>> arch/i386/kernel/crash.c/crash_nmi_callback():
>>
>> /* Assume hlt works */
>> halt();
>> for(;;);
>>
>> return 1;
>> }
This will result in the processor burning energy again after the first
interrupt, won't it?
>> arch/i386/kernel/doublefault.c/doublefault_fn():
>>
>> for (;;) /* nothing */;
>> }
>>
>> Let's assume that we have a less than moderate fan failure that causes
>> the CPU to heat up beyond the critical limit...
>> That might result in - you guessed it - crashes or doublefaults.
>> In which case we enter the corresponding handler and do... what?
>
> The double-fault is just a place-holder. The CPU will actually
> reset without even executing this (try it).
If it does reset, you don't need that fuctions (you can use anything),
and if not, doing while(1) halt(); in both cases should DTRT even if the
system is FUBAR, and it should be even smaller.
>> Exactly, we accelerate the CPUs happy march into bit heaven by letting it
>> execute a busy-loop under a non-working fan.
>
> 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.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
http://david.woodhou.se/why-not-spf.html
next parent reply other threads:[~2006-06-19 21:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2006-06-19 21:44 ` Dave Jones
2006-06-20 3:30 Ken Ryan
[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-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=E1FsRUZ-0001Ll-0K@be1.lrz \
--to=7eggert@elstempel.de \
--cc=7eggert@gmx.de \
--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®