From: Russell King <rmk@arm.linux.org.uk>
To: Con Kolivas <kernel@kolivas.org>
Cc: Herman Oosthuysen <Herman@WirelessNetworksInc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux vs Windows temperature anomaly
Date: Wed, 5 Mar 2003 23:50:57 +0000 [thread overview]
Message-ID: <20030305235057.M20511@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200303061038.44872.kernel@kolivas.org>; from kernel@kolivas.org on Thu, Mar 06, 2003 at 10:38:44AM +1100
On Thu, Mar 06, 2003 at 10:38:44AM +1100, Con Kolivas wrote:
> On Thu, 6 Mar 2003 10:11 am, Herman Oosthuysen wrote:
> > Linux is more 'busy' than windoze and I have heard of boxes frying when
> > running Linux. The solution is to find a better motherboard
> > manufacturer...
>
> That doesn't make sense. His post said the temperature was 20 degrees lower
> when it failed.
It makes perfect sense. Components drawing power produce heat, which
causes a temperature rise above ambient. Put simply, if a chip that
fails at a case temperature of 50C and you have a 10C rise, it'll fail
at 40C. If you have a 20C rise, it'll fail at 30C.
PS, the efficiency of heatsinks is measured in degC/W - how many degrees
celcius the temperature rises for each watt of power dissipated. Double
the dissipated power, double the temperature rise.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-03-05 23:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1045784829.3821.10.camel@laptop-linux.cunninghams>
[not found] ` <20030223223757.GA120@elf.ucw.cz>
[not found] ` <1046136752.1784.15.camel@laptop-linux.cunninghams>
[not found] ` <20030227132024.GB27084@atrey.karlin.mff.cuni.cz>
2003-02-27 18:42 ` SWSUSP Discontiguous pagedirs Nigel Cunningham
2003-03-01 4:22 ` SWSUSP Discontiguous pagedir patch Nigel Cunningham
2003-03-02 23:55 ` Patrick Mochel
2003-03-03 2:06 ` Nigel Cunningham
2003-03-03 2:31 ` Nigel Cunningham
2003-03-03 12:30 ` Pavel Machek
2003-03-04 20:36 ` Patrick Mochel
2003-03-05 20:50 ` Pavel Machek
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
2003-03-05 23:38 ` Con Kolivas
2003-03-05 23:50 ` Russell King [this message]
2003-03-06 0:29 ` Ed Sweetman
2003-03-06 0:47 ` Trever L. Adams
2003-03-06 9:45 ` Russell King
2003-03-06 1:58 ` Jonathan Lundell
2003-03-06 7:18 ` Corvus Corax
2003-03-06 7:57 ` Ed Sweetman
2003-03-06 8:18 ` Corvus Corax
2003-03-06 8:58 ` Ed Sweetman
2003-03-06 15:41 ` Jesse Pollard
2003-03-06 14:27 ` Jesse Pollard
2003-03-06 2:57 ` David Rees
2003-03-06 6:12 ` Matthias Schniedermeyer
2003-03-06 16:07 ` Jonathan Lundell
2003-03-07 0:40 ` Horst von Brand
2003-03-05 18:02 ` SWSUSP Discontiguous pagedir patch Pavel Machek
2003-03-07 17:14 ` Patrick Mochel
2003-03-07 20:27 ` Pavel Machek
2003-03-09 19:39 ` Benjamin Herrenschmidt
2003-03-09 20:12 ` Pavel Machek
2003-03-10 16:49 ` Patrick Mochel
2003-03-10 19:23 ` Pavel Machek
2003-03-10 19:05 ` Patrick Mochel
2003-03-10 22:17 ` Nigel Cunningham
2003-03-10 23:20 ` Pavel Machek
2003-03-07 20:36 ` Pavel Machek
2003-03-10 16:51 ` Patrick Mochel
2003-03-10 19:12 ` Pavel Machek
2003-03-10 18:59 ` Patrick Mochel
2003-03-07 20:41 ` Pavel Machek
2003-03-06 17:29 Linux vs Windows temperature anomaly Ed Vance
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=20030305235057.M20511@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Herman@WirelessNetworksInc.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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