public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Corvus Corax <corvusvcorax@gemia.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux vs Windows temperature anomaly
Date: Thu, 06 Mar 2003 02:57:31 -0500	[thread overview]
Message-ID: <3E66FF6B.2060301@wmich.edu> (raw)
In-Reply-To: <20030306081804.4717d1c4.corvusvcorax@gemia.de>

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
>



  reply	other threads:[~2003-03-06  7:47 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
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 [this message]
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=3E66FF6B.2060301@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=corvusvcorax@gemia.de \
    --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