From: Segin <segin2005@gmail.com>
To: Richard Wallman <richard@wallman.org.uk>
Cc: linux-8086@vger.kernel.org
Subject: Re: Porting to different architectures
Date: Tue, 01 Aug 2006 13:15:09 -0400 [thread overview]
Message-ID: <44CF8C1D.9020205@gmail.com> (raw)
In-Reply-To: <44CEF992.3090502@wallman.org.uk>
Richard Wallman wrote:
> Jody Bruchon wrote:
>
>
>>My main machine (the host) had an Athlon XP barbecue.
>
>
> Heh - I had one over the weekend. Sorting out my Dad's computer, IDE cable got
> in the way of the CPU fan and I didn't notice until it started a reset loop.
> It took a couple of minutes before it cooled down enough for the motherboard
> to be willing/able to report the CPU temperature - apparently it can't report
> temperatures over 99 degrees C. Amazing thing it, it still works!
>
> Cup of tea, anyone? :P
I had a system do a similar thing cause the fan get it's power via the
disk drive power cables, and if the wires are put in a certain position,
the fan quits working. At any rate, when I rebooted, i got a "Power
Managemenr failure" from the BIOS, checking it out revealed that the CPU
was roasting at a good 253 degrees, while running. Luckly it didn't break.
--
The real problem with C++ for kernel modules is: the language just sucks.
-- Linus Torvalds
next prev parent reply other threads:[~2006-08-01 17:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans
2006-07-31 15:35 ` Richard Wallman
2006-07-31 16:03 ` David Given
2006-07-31 16:24 ` Richard Wallman
2006-07-31 16:32 ` David Given
2006-07-31 17:42 ` Jody Bruchon
2006-08-01 6:49 ` Richard Wallman
2006-08-01 17:15 ` Segin [this message]
2006-07-31 19:47 ` Javier Sedano
2006-07-31 21:44 ` Alan Cox
2006-08-01 2:57 ` Tom McCabe
2006-08-01 5:27 ` Jody Bruchon
2006-08-01 13:22 ` Alan Cox
2006-08-01 14:41 ` Vikas N Kumar
2006-08-01 15:28 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29 ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43 ` Petr Koval
2006-07-31 15:51 ` Petr Koval
2006-08-02 13:24 ` Mattia Jona-Lasinio
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=44CF8C1D.9020205@gmail.com \
--to=segin2005@gmail.com \
--cc=linux-8086@vger.kernel.org \
--cc=richard@wallman.org.uk \
/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