From mboxrd@z Thu Jan 1 00:00:00 1970 From: Segin Subject: Re: Porting to different architectures Date: Tue, 01 Aug 2006 13:15:09 -0400 Message-ID: <44CF8C1D.9020205@gmail.com> References: <20060731140941.IIPE1187.ibm68aec.bellsouth.net@mail.bellsouth.net> <01ad01c6b4b2$07e4c790$6502a8c0@dionysus> <44CE232F.4080606@wallman.org.uk> <44CE411F.3090003@nc.rr.com> <44CEF992.3090502@wallman.org.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <44CEF992.3090502@wallman.org.uk> Sender: linux-8086-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Richard Wallman Cc: linux-8086@vger.kernel.org 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