On Mon, 2003-05-26 at 19:14, Josh McKinney wrote: > On approximately Mon, May 26, 2003 at 05:28:51PM -0400, Mark L. Kahnt wrote: > <snip> > > > > I run lm-sensors on hosehead here, and while the heatsink is smaller > > than I've found on most other systems, this box has been keeping the 800 > > MHz P3 at 112C. I don't feel that is bad, as the screenshot I got of the > > gkrellm sensor monitor indicated that the machine it was snapped from > > ran with a CPU at over 200C. BTW, those are Celsius temperatures, not > > hex values ;) > > > > I think you mean to say Fahrenheit temps. Even at Farhrenheit the temps > you mention are outrageous. Just for comparison my Athlon XP2000 runs > at 43C, or about 110F. > > -- > Josh McKinney | Webmaster: http://joshandangie.org > -------------------------------------------------------------------------- > Linux, the choice | They that can give up essential liberty > of a GNU generation -o) | to obtain a little temporary safety deserve > Kernel 2.4.20-ck6 /\ | neither liberty or safety. > on a Athlon-XP _\_v | -Benjamin Franklin Well, given that all of the other temperatures, such as the motherboard, are reporting values in the 25-30 range, and the software is tossing a C after them automatically, I am leaning to trusting the software, and presuming that the temperature is in the core of the cpu, which to me doesn't sound unreasonable when you consider the vast quantity of traces of current snaking all over the multiple layers of the chip in each and every second. The problem comes not from the specific core temperature if it is in an acceptable range for the processor design, but in temperature changes - uncontrolled escalations or sudden and significant cooling. -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: kahnt@hosehead.dyndns.org
Attachment:
signature.asc
Description: This is a digitally signed message part