From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Con Kolivas <kernel@kolivas.org>,
Herman Oosthuysen <Herman@WirelessNetworksInc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux vs Windows temperature anomaly
Date: Wed, 05 Mar 2003 19:29:02 -0500 [thread overview]
Message-ID: <3E66964E.6050101@wmich.edu> (raw)
In-Reply-To: <20030305235057.M20511@flint.arm.linux.org.uk>
Russell King wrote:
> 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.
>
that doesn't make much sense.
a chip for a given power output fails at a certain chip temperature,
this temperature doesn't vary by the case temp. If the case temp
increases then the chip temp will increase as long as the cooling system
on the chip doesn't change. Hence if the case temp increases the chip
temperature will increase and that could put it into the range of
failure. If the case temp decreases then the chip temp decreases.
The behavior you describe is when you increase the power output of a
chip beyond normal specifications (overclocking) then the temperature of
failure is lowered. eg. A chip that would run normally at 50C now can
only run stable at 45-40.
chip temp sensors are usually located in a relatively cool area of the
chip, hence chip failure temps occur usually around 60C (max) when in
fact it's around 80-90C. Unfortunately for us, chip temperature is not
uniform across the chip.
Here is a nice little site to get some info on that stuff.
http://users.erols.com/chare/elec.htm
that being said.
I've never heard of running linux frying someone's cpu. I could see
frying a power supply because cheap power supplies will fail after a
while of idle/load cycles that linux is good at using. I really dont see
how else linux could be more "busy" than winows especially since windows
has 5 or 6 spyware ad programs running behind the scenes all the time
anyway and the virus scanner having to check every instruction would
definitly lead to a higher cpu average than a linux box ding the same
things minus the spyware and virus scanner. It just doesn't make any
sense. Erroring out more in linux than windows...possibly yes depending
on which version but not hardware damage under normal use.
next prev parent reply other threads:[~2003-03-06 0:18 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
2003-03-06 0:29 ` Ed Sweetman [this message]
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=3E66964E.6050101@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=Herman@WirelessNetworksInc.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.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