Derek Jennings wrote:
SNIP
Checking cpu temp in bios is absolutely the worst indicator.
The system is under very little load. lm_sensors while the OS an
software are up an running is the only way to check for extreme
temps under high load. As, for example, with (torture test)
ftp://mersenne.org/gimps/mprime2413.tar.gz
I disagree. The temperature read out of lm_sensors has to be set up for each
motherboard. The readings from an install of lm_sensors is often wildly
inaccurate. The mobo manufacturer will have set up the BIOS temp readings to
be accurate (if they have done their job properly) When configuring
lm_sensors the readout should be compared to the BIOS and a temperature probe
if available.
I disagree with all that. lm_sensors is good out of the box for
most chipsets/motherboards. In some cases, a read of sensors.conf
will reveal that cpu an chipset temps may be reversed. It happens in
Win$ux's Motherboard Monitor too. I would think that any user,
however newbie, with HW an temp problems would recognize that
chipset temp is always the lower one. Both tho, are very important.
As I said, bios temps are for the system under low load, often
after a warm, or even cold boot. An have little to no relevance to
when the system is up an running. Particularly under high load, an
specially with a real OS. Low temps are only for braggin rights,
highest temps under high to extreme loads are the only ones that are
meaningful.
Another caveat; most chipsets, particularly AMD's, don't have an
internal diode, or a mobo implementation that will directly report
internal cpu core temps. AMD's white paper says to add 10 to 20C to
probe (thermistor) temps. Likewise, Intel cautions to add 10C to
diode reported temps, in order to approximate _actual_ internal core
temp. Failure temp specified by either vendor is for actual internal
die temp, an really means FUBAR'd.
Which is why I said that 70C is way too high for either one,
Intel or AMD. It's actually more than 80 to 90C an close to failure.
Also constant or repeated visits to this core temp range will weaken
or damage the processor. Repeated normal temps, rapidly reduced to
cool temps, as with software hacks like athcool, or Winblows apps
like Rain, will accelerate the situation, masking it in the meantime.
SNIP
Going back to what I've said above **, software attempts at
cpu cooling are a very bad strategy. When the system is under high
to 100% load they have no effect, as no HLTS are being sent to the
processor. When the system is under light load, HLTS are sent
directly, an the cpu cools rapidly to an artificially low core temp.
This increases the range of the heat/cool cycle that can cause cpu
core trace migration, an can result in permanent damage. Also the
chipset is not being artificially cooled, an motherboard damage is
more likely. This is why, using athcool as an example, the author
issues this disclaimer :
True, both Athcool and speedstepping will cause the CPU temperature to vary,
but that is better than having the OPs computer shut itself down after 30
mins.
Really! Put'n blinders on an stick your head in the sand is
better than seeking the root cause of the problem? (see my comments
above)
I note also that Athcool's author does not list "Core trace migration" as a
risk when using athcool.
Traces are the 'wires' that connect the various processes in a
cpu. They're made of metal an are subject to physical contraction an
expansion. No matter how small their size (ie, 13nm in most newer
chips). As metal, they have a different coefficient of expansion
than the medium (silicon) that they're imbedded in. Repeated
contraction an expansion weakens them, an increases the electrical
resistance. Which leads to system lockups or instability.
'Migration' is used to describe the shifting between the medium
an the traces. Actually, constant or repeated over heating that
causes increased electrical resistance in the traces, is an equal
problem.
Athcool's author does address this. Particularly in the
" !!!WARNING!!! * system locks or instability ".
If you have continued success usin a software hack to mask HW
problems in the short term, then more power to ya! BUT, I wouldn't
advise newbies to follow suit. Which is the only reason I bothered
to reply in the first place.
Y'alls MMV
--
Tom Brinkman Corpus Christi, Texas
____________________________________________________
Want to buy your Pack or Services from Mandriva?
Go to http://store.mandriva.com
Join the Club : http://www.mandrivaclub.com
____________________________________________________
