* RE: Linux vs Windows temperature anomaly
@ 2003-03-06 17:29 Ed Vance
0 siblings, 0 replies; 19+ messages in thread
From: Ed Vance @ 2003-03-06 17:29 UTC (permalink / raw)
To: 'Ed Sweetman'; +Cc: Corvus Corax, linux-kernel
On Thu, March 06, 2003 at 12:58 AM, Ed Sweetman wrote:
>
> I believe the originator of the thread went back to check and
> see if he can find out exactly what his Windows drivers are
> enabling. the rest of the thread has been arguing over if
> linux can load hardware more than windows can and what puts
> off heat and what doesn't which is stupid.
>
> i think the topic of the thread is a bunch of BS because
> unless he has a driver that is for some reason changing the
> frequency of something or the voltage then linux is not going
> to stress the system more than windows. The whole thing wreaks
> of FUD whether intentional or not.
>
Well, here's _my_ stupid BS and (intentional) FUD question: 8)
Does anybody know if XP actively performs progressive power
management actions as the CPU temperature increases inside the
normal operating range? If this were done somewhat linearly
starting at "medium rare", instead of only at "well done" to
save the hardware, wouldn't it look like the reported anomaly?
Always suspicious ;)
Ed
----------------------------------------------------------------
Ed Vance edv (at) macrolink (dot) com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
` (2 preceding siblings ...)
2003-03-06 6:12 ` Matthias Schniedermeyer
@ 2003-03-07 0:40 ` Horst von Brand
3 siblings, 0 replies; 19+ messages in thread
From: Horst von Brand @ 2003-03-07 0:40 UTC (permalink / raw)
To: Jonathan Lundell; +Cc: Linux Kernel Mailing List
Jonathan Lundell <linux@lundell-bros.com> said:
> We've been seeing a curious phenomenon on some PIII/ServerWorks
> CNB30-LE systems.
>
> The systems fail at relatively low temperatures. While the failures
> are not specifically memory related (ECC errors are never a factor),
> we have a memory test that's pretty good at triggering them. Data is
> apparently getting corrupted on the front-side bus.
>
> Here's the curious thing: when we run the same memory test on a
> Windows 2000 system (same hardware; we just swap the disk), we can
> run the ambient temperature up to 60C with no problem at all; the
> test will run for days. (It occurred to us to try Win2K because the
> hardware vendor was using it to test systems at temperature without
> seeing problems.)
>
> Swap in the Linux disk, and at that temperature it'll barely run at
> all. The memory test fails quickly at 40C ambient.
Linux gives the hardware a _much_ harder workout than Windows.
My first PC was a P/100, overclocked to /120. WinNT worked fine, Linux
wouldn't even finish booting.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 6:12 ` Matthias Schniedermeyer
@ 2003-03-06 16:07 ` Jonathan Lundell
0 siblings, 0 replies; 19+ messages in thread
From: Jonathan Lundell @ 2003-03-06 16:07 UTC (permalink / raw)
To: Linux Kernel Mailing List
At 7:12am +0100 3/6/03, Matthias Schniedermeyer wrote:
>Hmmm. Wasn't there something with IDE and the LE-Chipset.
>
>Maybe you should try a current kernel. Don't know if this old-kernel has
>the fix.
It involved DMA, I think; I've disabled IDE DMA altogether.
My current plan is to run the tests with a more recent kernel, and to
compare PIII MSRs between a Linux and Windows boot.
--
/Jonathan Lundell.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 8:58 ` Ed Sweetman
@ 2003-03-06 15:41 ` Jesse Pollard
0 siblings, 0 replies; 19+ messages in thread
From: Jesse Pollard @ 2003-03-06 15:41 UTC (permalink / raw)
To: Ed Sweetman, Corvus Corax; +Cc: linux-kernel
On Thursday 06 March 2003 02:58 am, Ed Sweetman wrote:
snip
> i know for a fact my abit athlon motherboard's bus chip doesn't change
> temperature due to load in the system. The only time it fluctuates is
> when the temperature of the room changes and that change is not due to
> the chip (unless i got no air circulation in the room then the computer
> as a whole will heat up all the air and that feeds back on itself)
Only because you are removing the heat as fast as it is being generated.
Which speaks for a good motherboard, heat sink, and fan combination,
along with decent AC for the room.
Additional heat generation with the use of Linux has been documented
going back to the 486 days, when problems were traced to an insufficient
heat sink. (system works with windows, crashes with Linux... replaced heat
sink and all is well).
The entire thread has been about a burst of activity that causes a thermal
spike in one or two possible locations not in the CPU. The internal
ambient temperature takes at least 3-5 seconds to change before the
sensor can report it. If the chip is already operating just below it's
critical temperature (and that varies among chips, even in the same lot)
then it will work with windows.
Linux has a much higher demand on the hardware, partially due to the
ability to generate DMA requests faster. This adds extra heat to the
bridges, and COULD push the chip over the critical temperature for
brief times (I would guess it would be in the millisecond range). Sustained
DMA activity would be a suspect in something like this.
It would be an interesting research topic to put high precision sensors
on all of the important chips on a motherboard (say between the chip and
heat sink) and come up with a time sequence and thermal map of a
collection of motherboards....
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 7:18 ` Corvus Corax
2003-03-06 7:57 ` Ed Sweetman
@ 2003-03-06 14:27 ` Jesse Pollard
1 sibling, 0 replies; 19+ messages in thread
From: Jesse Pollard @ 2003-03-06 14:27 UTC (permalink / raw)
To: Corvus Corax, linux-kernel
On Thursday 06 March 2003 01:18 am, Corvus Corax wrote:
> Am Thu, 6 Mar 2003 10:38:44 +1100
>
> schrieb Con Kolivas <kernel@kolivas.org>:
> > That doesn't make sense. His post said the temperature was 20 degrees
> > lower when it failed.
> >
> > Con
>
> I think it does,
snip
> if the bridge has only a heatsink, its temperature is somewhat like
> (system TEMP)+ ( produced heatper time / heat given to the air by heatsink
> per time ) where the heatsinks capacity is dependent on the delta
> temperature, too, gets complicated ;)
>
> in short, the chips hotter than the rest of the system and if it has high
> load it gets even hotter, but its temp is still dependant on the main
> system TEMP. ;)
It is also referred to as thermal inertia. It takes time for the heat sink to
1. heat up
2. start transferring that head out
During that time delay the chip may easily overheat in a burst of activity.
Same thing happens to fuses... a "slow blow" fuse will blow faster in higher
ambient temperature, under conditions that are normal because the AC was
turned on...
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 0:47 ` Trever L. Adams
@ 2003-03-06 9:45 ` Russell King
0 siblings, 0 replies; 19+ messages in thread
From: Russell King @ 2003-03-06 9:45 UTC (permalink / raw)
To: Trever L. Adams
Cc: Ed Sweetman, Con Kolivas, Herman Oosthuysen, Linux Kernel Mailing List
On Wed, Mar 05, 2003 at 07:47:05PM -0500, Trever L. Adams wrote:
> You are the one mistaken. Most CPUs don't dissipate a constant amount
> of power as heat. That depends on what the CPU is doing.
Correct - each time a gate in the CPU switches state, it produces a
small amount of heat. Have enough gates switching, and you produce
a lot of heat (and your current consumption goes up.) This is basic
CMOS operation.
> I do believe the previous poster was incorrect about the mathematical
> relationship between case and CPU temperatures.
I never said there was a 1:1 relationship here - you misread my mail.
I talked about _heat sinks_, not the relationship between the temperature
on the silicon die and the external case temperature, with or without a
heatsink, with or without a fan. If you want to talk about the silicon
die, then you need to take into account thermal resistance between the
die and the case, the case and the heatsink, the heatsink and the
surrounding air, the fact that the heatsink is attached to one side
only, etc.
However, going into it in minute detail with all the maths is NOT a
subject for this list.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 8:18 ` Corvus Corax
@ 2003-03-06 8:58 ` Ed Sweetman
2003-03-06 15:41 ` Jesse Pollard
0 siblings, 1 reply; 19+ messages in thread
From: Ed Sweetman @ 2003-03-06 8:58 UTC (permalink / raw)
To: Corvus Corax; +Cc: linux-kernel
Corvus Corax wrote:
> Am Thu, 06 Mar 2003 02:57:31 -0500
> schrieb Ed Sweetman <ed.sweetman@wmich.edu>:
>
>
>>This is getting kicked like a deadhorse by now i think but.
>>
>
> even dead horses have the right of being kicked ;) but:
>
>
>>Unlike your cpu which gets idle commands from the OS and thus has an
>>idle loop where it turns off certain circuits and which can get acpi
>>commands to turn completely off the other chips in the computer do not
>>have such a luxury. they are always on like the cpus of yesteryear used
>>to be. It doesn't matter if they have data moving in them or not, no
>>big difference.
>
>
> I think this is not right so, doe to 2 reasons:
>
> 1st, i burned my finger on my bridge often enough that i should know that
> its temperature varies, at least on some chips to really huge amounts ;-)
> (on my new borad they dont even get hand warm)
>
> 2nd. the fact that the chip (or circuit) is on, doesnt mean that there flows current.
>
> all halfway new microchips (including those bridges of course) are build in CMOS
> or similar technology, meaning that there is no more static current flowing through
> the transistors, but only capacity dependant current, when the transistors change
> their state.
>
> if no data flows, little transistors change their state
> (only clock signals and some other idle work that is done),
> and the output drivers to the bus systems are turned low.
>
> so there is no static current on the bus and no dynamic current in the chip --> low overall current
> --> low temperature
>
> on the other hand if data flows, its being processed, and many transistors change their state with the data flow,
> as do the output driver blocks --> high static and dynamic current --> high temperature.
>
>
>
>>The reason why it seems like this is the case is for
>>you HSF cooled cpu guys, load on the system bus usually means high cpu
>>load and that means more heat put into the surrounding air and the
>>little usually passive cooled but regardless, less hot system bus gets
>>hotter along with the cpu and cooler when the cpu is idle. People
>>cooled by other methods that do not dump heat into the surrounding air
>>inside the case will notice that the system bus temp only varies with
>>ambient air temp changes, not data transfer going on between ram and cpu.
>>
>
>
> than this would be measurable as an higher mainboard or system temperature,
> which is not in our case, as described in the other mails
higher than what, the bus power output is constant, the internal
temperature of the case is dictated by the heat given off by all the
components, they're not separable. That's like saying i would be able
to tell if my cpu is putting a constant power output by seeing a higher
ambient air temp in the computer case...well no you wouldn't it becomes
a constant and all the other components that do have varying power
outputs dictate the fluctuations of ambient air. How you get a constant
as contributing to changes in ambient air is beyond me, and finding a
comparison in order to say it makes the air hotter is further beyond me.
The ambient air temp is the temp it is because of all the components
inside the case, including the system bus. The only way the system bus's
power output would be able to be measured as a higher ambient air temp
is if it worked the way you suggested (which i really dont think most
do). If you mean then the system bus should be hotter if it's always on
the way i suggest ...well you'd be wrong. They dont get hot if the
ambient temperature around the bus's heatsink stays cool. Most people
just run them passive when they have watercooling because without all
the heat from the cpu's heatsink, the ambient air around the bus is
sufficiently cool. otherwise a fan is usually needed.
i know for a fact my abit athlon motherboard's bus chip doesn't change
temperature due to load in the system. The only time it fluctuates is
when the temperature of the room changes and that change is not due to
the chip (unless i got no air circulation in the room then the computer
as a whole will heat up all the air and that feeds back on itself)
I believe the originator of the thread went back to check and see if he
can find out exactly what his Windows drivers are enabling. the rest of
the thread has been arguing over if linux can load hardware more than
windows can and what puts off heat and what doesn't which is stupid.
i think the topic of the thread is a bunch of BS because unless he has a
driver that is for some reason changing the frequency of something or
the voltage then linux is not going to stress the system more than
windows. The whole thing wreaks of FUD whether intentional or not.
> greetings,
>
>
> Corvus V Corax ;)
> -
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 7:57 ` Ed Sweetman
@ 2003-03-06 8:18 ` Corvus Corax
2003-03-06 8:58 ` Ed Sweetman
0 siblings, 1 reply; 19+ messages in thread
From: Corvus Corax @ 2003-03-06 8:18 UTC (permalink / raw)
To: Ed Sweetman; +Cc: linux-kernel
Am Thu, 06 Mar 2003 02:57:31 -0500
schrieb Ed Sweetman <ed.sweetman@wmich.edu>:
> This is getting kicked like a deadhorse by now i think but.
>
even dead horses have the right of being kicked ;) but:
>
> Unlike your cpu which gets idle commands from the OS and thus has an
> idle loop where it turns off certain circuits and which can get acpi
> commands to turn completely off the other chips in the computer do not
> have such a luxury. they are always on like the cpus of yesteryear used
> to be. It doesn't matter if they have data moving in them or not, no
> big difference.
I think this is not right so, doe to 2 reasons:
1st, i burned my finger on my bridge often enough that i should know that
its temperature varies, at least on some chips to really huge amounts ;-)
(on my new borad they dont even get hand warm)
2nd. the fact that the chip (or circuit) is on, doesnt mean that there flows current.
all halfway new microchips (including those bridges of course) are build in CMOS
or similar technology, meaning that there is no more static current flowing through
the transistors, but only capacity dependant current, when the transistors change
their state.
if no data flows, little transistors change their state
(only clock signals and some other idle work that is done),
and the output drivers to the bus systems are turned low.
so there is no static current on the bus and no dynamic current in the chip --> low overall current
--> low temperature
on the other hand if data flows, its being processed, and many transistors change their state with the data flow,
as do the output driver blocks --> high static and dynamic current --> high temperature.
> The reason why it seems like this is the case is for
> you HSF cooled cpu guys, load on the system bus usually means high cpu
> load and that means more heat put into the surrounding air and the
> little usually passive cooled but regardless, less hot system bus gets
> hotter along with the cpu and cooler when the cpu is idle. People
> cooled by other methods that do not dump heat into the surrounding air
> inside the case will notice that the system bus temp only varies with
> ambient air temp changes, not data transfer going on between ram and cpu.
>
than this would be measurable as an higher mainboard or system temperature,
which is not in our case, as described in the other mails
greetings,
Corvus V Corax ;)
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 7:18 ` Corvus Corax
@ 2003-03-06 7:57 ` Ed Sweetman
2003-03-06 8:18 ` Corvus Corax
2003-03-06 14:27 ` Jesse Pollard
1 sibling, 1 reply; 19+ messages in thread
From: Ed Sweetman @ 2003-03-06 7:57 UTC (permalink / raw)
To: Corvus Corax; +Cc: linux-kernel
This is getting kicked like a deadhorse by now i think but.
Unlike your cpu which gets idle commands from the OS and thus has an
idle loop where it turns off certain circuits and which can get acpi
commands to turn completely off the other chips in the computer do not
have such a luxury. they are always on like the cpus of yesteryear used
to be. It doesn't matter if they have data moving in them or not, no
big difference. The reason why it seems like this is the case is for
you HSF cooled cpu guys, load on the system bus usually means high cpu
load and that means more heat put into the surrounding air and the
little usually passive cooled but regardless, less hot system bus gets
hotter along with the cpu and cooler when the cpu is idle. People
cooled by other methods that do not dump heat into the surrounding air
inside the case will notice that the system bus temp only varies with
ambient air temp changes, not data transfer going on between ram and cpu.
Corvus Corax wrote:
> Am Thu, 6 Mar 2003 10:38:44 +1100
> schrieb Con Kolivas <kernel@kolivas.org>:
>
>
>>That doesn't make sense. His post said the temperature was 20 degrees lower
>>when it failed.
>>
>>Con
>
>
> I think it does,
>
> look at this:
>
> RAM
> ._____________________.
> _|| | | | | | | | | | ||_. ._/| ._/|
> / ||___________________|| |~\ ||/| ||/|
> | |O _____ O| |~\\ /||/| ||/|
> | | .-°| | |°-. | |\\\\ //|| | || |
> | | / \ |~| | / \ | |\\\\\ //=|| |=|| |
> | | /| |\| |~|/| |\ | |\\\\.________. ///=||/|=||/|
> | | * | | \_._/ |~| * | |\===| |==///==||/|=||/|
> | | |~|~| /CPU\ ~ | | | |====| north |==///==|| |=|| |
> | | | | |~\_ _/ | | | | |====| bridge |=======|| |=|| |
> | | * | | / ° \ | |~* | |/===| (MEM ) |=======||/|=||/|
> | | \| |/| |~|\|~|/ | |//==| (CTRL) |==\\\==||/|=||/|
> | | \ / |~| | \ / | |////°~~~~~~~~°==\\\==|| |=|| |
> | | °-.|_|_|.-° | |///// |||||| \\\=|| |=|| |
> | |O O| |//// |||||| \\=||/|=||/|
> | |~~~~~~~~~~~~~~~~~~~~~| |_// |||||| \\||/| ||/|
> °~|| | | | | | | | | | ||~°_/ |||||| \|| | || |
> °~~~~~~~~~~~~~~~~~~~~~° |||||| ||/ ||/
> CPU TEMP | |||||| |_| |_|
> | | voltage ||||||
> | ||| ||||||
> | ||| .________.
> Mainboard | ||| | |
> TEMP .,,,,,,. data | south |
> O | |=======| bridge |
> \\_____°''''''° | (BUS ) |
> °~~~~~~° | (CTRL) |
> TEMP & °~~~~~~~~°
> VOLTAGE ctrl ////|||\\\\\
> chip PCI & other BUS
>
>
> the sensor for the system temperature (somewhere on the board) is connected to a driver chip (usually on the i2c bus)
> like the w83781d (on my board)
>
> if something now causes the (often badly cooled) bridge to get hot (by more load between some periphery and the RAM for example)
> , the system temperature doesnt necessary have to increase.
>
> if the bridge has only a heatsink, its temperature is somewhat like
> (system TEMP)+ ( produced heatper time / heat given to the air by heatsink per time )
> where the heatsinks capacity is dependent on the delta temperature, too, gets complicated ;)
>
> in short, the chips hotter than the rest of the system and if it has high load it gets even hotter,
> but its temp is still dependant on the main system TEMP. ;)
>
> blahrgh forget what i talk, watch the ASCII art, and imagine the effect of much data running between
> BUS and RAM ;-) (or BUS and BUS if north and southbridge are on the same chip)
>
> CvC
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 23:38 ` Con Kolivas
2003-03-05 23:50 ` Russell King
@ 2003-03-06 7:18 ` Corvus Corax
2003-03-06 7:57 ` Ed Sweetman
2003-03-06 14:27 ` Jesse Pollard
1 sibling, 2 replies; 19+ messages in thread
From: Corvus Corax @ 2003-03-06 7:18 UTC (permalink / raw)
To: linux-kernel
Am Thu, 6 Mar 2003 10:38:44 +1100
schrieb Con Kolivas <kernel@kolivas.org>:
>
> That doesn't make sense. His post said the temperature was 20 degrees lower
> when it failed.
>
> Con
I think it does,
look at this:
RAM
._____________________.
_|| | | | | | | | | | ||_. ._/| ._/|
/ ||___________________|| |~\ ||/| ||/|
| |O _____ O| |~\\ /||/| ||/|
| | .-°| | |°-. | |\\\\ //|| | || |
| | / \ |~| | / \ | |\\\\\ //=|| |=|| |
| | /| |\| |~|/| |\ | |\\\\.________. ///=||/|=||/|
| | * | | \_._/ |~| * | |\===| |==///==||/|=||/|
| | |~|~| /CPU\ ~ | | | |====| north |==///==|| |=|| |
| | | | |~\_ _/ | | | | |====| bridge |=======|| |=|| |
| | * | | / ° \ | |~* | |/===| (MEM ) |=======||/|=||/|
| | \| |/| |~|\|~|/ | |//==| (CTRL) |==\\\==||/|=||/|
| | \ / |~| | \ / | |////°~~~~~~~~°==\\\==|| |=|| |
| | °-.|_|_|.-° | |///// |||||| \\\=|| |=|| |
| |O O| |//// |||||| \\=||/|=||/|
| |~~~~~~~~~~~~~~~~~~~~~| |_// |||||| \\||/| ||/|
°~|| | | | | | | | | | ||~°_/ |||||| \|| | || |
°~~~~~~~~~~~~~~~~~~~~~° |||||| ||/ ||/
CPU TEMP | |||||| |_| |_|
| | voltage ||||||
| ||| ||||||
| ||| .________.
Mainboard | ||| | |
TEMP .,,,,,,. data | south |
O | |=======| bridge |
\\_____°''''''° | (BUS ) |
°~~~~~~° | (CTRL) |
TEMP & °~~~~~~~~°
VOLTAGE ctrl ////|||\\\\\
chip PCI & other BUS
the sensor for the system temperature (somewhere on the board) is connected to a driver chip (usually on the i2c bus)
like the w83781d (on my board)
if something now causes the (often badly cooled) bridge to get hot (by more load between some periphery and the RAM for example)
, the system temperature doesnt necessary have to increase.
if the bridge has only a heatsink, its temperature is somewhat like
(system TEMP)+ ( produced heatper time / heat given to the air by heatsink per time )
where the heatsinks capacity is dependent on the delta temperature, too, gets complicated ;)
in short, the chips hotter than the rest of the system and if it has high load it gets even hotter,
but its temp is still dependant on the main system TEMP. ;)
blahrgh forget what i talk, watch the ASCII art, and imagine the effect of much data running between
BUS and RAM ;-) (or BUS and BUS if north and southbridge are on the same chip)
CvC
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
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
3 siblings, 1 reply; 19+ messages in thread
From: Matthias Schniedermeyer @ 2003-03-06 6:12 UTC (permalink / raw)
To: Jonathan Lundell; +Cc: Linux Kernel Mailing List
On Wed, Mar 05, 2003 at 01:52:16PM -0800, Jonathan Lundell wrote:
> We've been seeing a curious phenomenon on some PIII/ServerWorks
> CNB30-LE systems.
>
> So, the puzzle: what might account for temperature sensitivity, of
> all things, under Linux 2.4.9-31 (RH 7.2), but not Win2K?
Hmmm. Wasn't there something with IDE and the LE-Chipset.
Maybe you should try a current kernel. Don't know if this old-kernel has
the fix.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 21:52 ` Linux vs Windows temperature anomaly Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
@ 2003-03-06 2:57 ` David Rees
2003-03-06 6:12 ` Matthias Schniedermeyer
2003-03-07 0:40 ` Horst von Brand
3 siblings, 0 replies; 19+ messages in thread
From: David Rees @ 2003-03-06 2:57 UTC (permalink / raw)
To: Linux Kernel Mailing List
On Wed, Mar 05, 2003 at 01:52:16PM -0800, Jonathan Lundell wrote:
> We've been seeing a curious phenomenon on some PIII/ServerWorks
> CNB30-LE systems.
>
> The systems fail at relatively low temperatures. While the failures
> are not specifically memory related (ECC errors are never a factor),
> we have a memory test that's pretty good at triggering them. Data is
> apparently getting corrupted on the front-side bus.
>
> Here's the curious thing: when we run the same memory test on a
> Windows 2000 system (same hardware; we just swap the disk), we can
> run the ambient temperature up to 60C with no problem at all; the
> test will run for days. (It occurred to us to try Win2K because the
> hardware vendor was using it to test systems at temperature without
> seeing problems.)
>
> Swap in the Linux disk, and at that temperature it'll barely run at
> all. The memory test fails quickly at 40C ambient.
>
> FWIW, CPU cooling is pretty good in this box.
>
> So, the puzzle: what might account for temperature sensitivity, of
> all things, under Linux 2.4.9-31 (RH 7.2), but not Win2K?
Since it doesn't sound like this is a memory error, but a chipset driver
error it could be a Linux driver bug.
You are running a very old kernel, at the least upgrade to the latest
errata (which is currently 2.4.18-26.7. You are running the latest
security updates as well, right?
-Dave
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-06 0:29 ` Ed Sweetman
2003-03-06 0:47 ` Trever L. Adams
@ 2003-03-06 1:58 ` Jonathan Lundell
1 sibling, 0 replies; 19+ messages in thread
From: Jonathan Lundell @ 2003-03-06 1:58 UTC (permalink / raw)
To: linux-kernel
At 7:29pm -0500 3/5/03, Ed Sweetman wrote:
>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.
I don't think it's a case of "busy" per se. Both systems are 100%
occupied with a userland memory test (it just mallocs and locks a
biggish buffer, and does reads and writes of various patters). One
pass of the test takes about 104 seconds on both systems (presumably
it's memory-bound, so compiler differences aren't showing up).
It was suggested off-list that I compare the chipset config registers
to see if anything is different. I've been meaning to do that, but
just looking at the registers, I don't see anything that would affect
FSB timing, or the FSB at all, for that matter. Naetheless, I'll do
the comparison as soon as I dig up an lspci equivalent for Win2K.
As for temperature differences, the heat sink temperature (at least)
doesn't seem to differ appreciably between the systems, which is what
I'd expect with essentially the same load on each.
I'm wondering, somewhat ignorantly, if there might be some kind of
CPU configuration that Windows is adjusting, as some kind of
workaround or the like. I don't suppose that this is the best place
to ask how to read MSRs from Windows....
--
/Jonathan Lundell.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
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
1 sibling, 1 reply; 19+ messages in thread
From: Trever L. Adams @ 2003-03-06 0:47 UTC (permalink / raw)
To: Ed Sweetman
Cc: Russell King, Con Kolivas, Herman Oosthuysen, Linux Kernel Mailing List
> 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.
You are the one mistaken. Most CPUs don't dissipate a constant amount
of power as heat. That depends on what the CPU is doing. For example,
even the Athlon without disconnect will cool some when it is 'halt'ed.
If a CPU is working more, accomplishing more than it was at another
time, it will be needing to rid itself of more heat. Hence, the fact
that the external temperature becomes the limiting factor (along with
how good the heat exchange system is [i.e. heat sink/fan]).
I do believe the previous poster was incorrect about the mathematical
relationship between case and CPU temperatures. They are NOT a 1:1.
However, he is right, they are mathematically related. Just as the heat
dissipated and the work done are related.
You do not need to overclock a CPU to get this kind of a change. The
change in the efficiency (memory management, task switching, etc.) of
how the work is done can cause the CPU to be worked harder... and when
the CPU is worked harder, so is memory and quite often just about
everything else.
Trever
--
One O.S. to rule them all, One O.S. to find them. One O.S. to bring them
all and in the darkness bind them.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 23:50 ` Russell King
@ 2003-03-06 0:29 ` Ed Sweetman
2003-03-06 0:47 ` Trever L. Adams
2003-03-06 1:58 ` Jonathan Lundell
0 siblings, 2 replies; 19+ messages in thread
From: Ed Sweetman @ 2003-03-06 0:29 UTC (permalink / raw)
To: Russell King; +Cc: Con Kolivas, Herman Oosthuysen, Linux Kernel Mailing List
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.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 23:38 ` Con Kolivas
@ 2003-03-05 23:50 ` Russell King
2003-03-06 0:29 ` Ed Sweetman
2003-03-06 7:18 ` Corvus Corax
1 sibling, 1 reply; 19+ messages in thread
From: Russell King @ 2003-03-05 23:50 UTC (permalink / raw)
To: Con Kolivas; +Cc: Herman Oosthuysen, Linux Kernel Mailing List
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
2003-03-05 23:11 ` Herman Oosthuysen
@ 2003-03-05 23:38 ` Con Kolivas
2003-03-05 23:50 ` Russell King
2003-03-06 7:18 ` Corvus Corax
0 siblings, 2 replies; 19+ messages in thread
From: Con Kolivas @ 2003-03-05 23:38 UTC (permalink / raw)
To: Herman Oosthuysen, Linux Kernel Mailing List
On Thu, 6 Mar 2003 10:11 am, Herman Oosthuysen wrote:
> Jonathan Lundell wrote:
> > We've been seeing a curious phenomenon on some PIII/ServerWorks CNB30-LE
> > systems.
> >
> > The systems fail at relatively low temperatures. While the failures are
> > So, the puzzle: what might account for temperature sensitivity, of all
> > things, under Linux 2.4.9-31 (RH 7.2), but not Win2K?
>
> 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.
Con
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Linux vs Windows temperature anomaly
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-06 2:57 ` David Rees
` (2 subsequent siblings)
3 siblings, 1 reply; 19+ messages in thread
From: Herman Oosthuysen @ 2003-03-05 23:11 UTC (permalink / raw)
To: Linux Kernel Mailing List
Jonathan Lundell wrote:
> We've been seeing a curious phenomenon on some PIII/ServerWorks CNB30-LE
> systems.
>
> The systems fail at relatively low temperatures. While the failures are
> So, the puzzle: what might account for temperature sensitivity, of all
> things, under Linux 2.4.9-31 (RH 7.2), but not Win2K?
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...
Cheers,
--
------------------------------------------------------------------------
Herman Oosthuysen
B.Eng.(E), Member of IEEE
Wireless Networks Inc.
http://www.WirelessNetworksInc.com
E-mail: Herman@WirelessNetworksInc.com
Phone: 1.403.569-5687, Fax: 1.403.235-3965
------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 19+ messages in thread
* Linux vs Windows temperature anomaly
2003-03-05 20:50 ` Pavel Machek
@ 2003-03-05 21:52 ` Jonathan Lundell
2003-03-05 23:11 ` Herman Oosthuysen
` (3 more replies)
0 siblings, 4 replies; 19+ messages in thread
From: Jonathan Lundell @ 2003-03-05 21:52 UTC (permalink / raw)
To: Linux Kernel Mailing List
We've been seeing a curious phenomenon on some PIII/ServerWorks
CNB30-LE systems.
The systems fail at relatively low temperatures. While the failures
are not specifically memory related (ECC errors are never a factor),
we have a memory test that's pretty good at triggering them. Data is
apparently getting corrupted on the front-side bus.
Here's the curious thing: when we run the same memory test on a
Windows 2000 system (same hardware; we just swap the disk), we can
run the ambient temperature up to 60C with no problem at all; the
test will run for days. (It occurred to us to try Win2K because the
hardware vendor was using it to test systems at temperature without
seeing problems.)
Swap in the Linux disk, and at that temperature it'll barely run at
all. The memory test fails quickly at 40C ambient.
FWIW, CPU cooling is pretty good in this box.
So, the puzzle: what might account for temperature sensitivity, of
all things, under Linux 2.4.9-31 (RH 7.2), but not Win2K?
--
/Jonathan Lundell.
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2003-03-07 1:22 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-06 17:29 Linux vs Windows temperature anomaly Ed Vance
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 12:30 SWSUSP Discontiguous pagedir patch 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
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
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®