On Tuesday 30 October 2001 03:10 pm, Guillaume Cottenceau wrote:
> Tom Brinkman <[EMAIL PROTECTED]> writes:
> > cpuburn http://users.ev1.net/~redelm/ severely tests
>
> This looks interesting; I'm thinking of puting that in the rescue;
> what would you advice? What's the procedure? Fork, launch the
> "burn*" program and monitor the process? It seems that burnBX would
> terminate on error but burnP5 would not, is it right? It's sad
> because it seems that burnP6 would terminate on error? Which
> "burn*" would be the best for a general-purpose test, burnP5 for
> processor and burnBX for memory, right?
My experience is that any of the various burn?? modules will run.
For instance, I've used 'burnP6' with my Tbird. I believe these
questions would be much better answered by the author tho.
Robert Redelmeier, HOUSTON USA [EMAIL PROTECTED] He's always been
very helpful on the newsgroups... and Texas friendly ;)
>
> > cpu/cache/ram. As a long time overclocker, I can say if your
> > system can run cpuburn for at least 30 mins, it's stable as can
> > be. Quicker and easier to use than memtest86 or settin up a
> > kernel compile loop. I'd strongly suggest havin continuous cpu
> > temp monitoring setup before runnin any of cpuburn's modules.
> > 'burnK7' will get my 1.4 at
>
> Why so? Physical damage only occurs when the processor is _really_
> hot, and the motherboard would prevent from that, isn't it?
With an Intel proceesor yes. The internal diode protects it. With
AMD's ... maybe. Only the new XP Palimino's have a internal temp
diode, but currently no motherboards that support (i2c) checking it
and shutting down.
Also, i2c reporting has been direct (internal core temp) from the
earliest Pentiums. With AMD cpu's, temp is reported from a mobo probe
(thermistor). Overclockers have always added at least 10�C to
probe temps in order to guess at the actual core temp. Recently AMD
said to add as much as 20�C (they said "10 to 20").
>
> > 1.55 ghz Tbird up to 52�C.
So my 52�C max could actually be a core temp of 70+� Since
Tbirds fry at 90� and generally start spitin errors in the 70's, you
wouldn't want to see 55�C from a Tbird probe temp under extreme load,
or more'n 50C during normal heavy operation (like a kernel compile).
My advice would be to abort burnK7 if the probe temp from a Tbird got
near to over 55�C. I'd abort an Intel processor at 50�C (most Intels
fry at 65, spit errors at 45). With either, going over what I'm
advising probly means you need better HS/fan and case ventilation.
> > BTW, thanks Guillaume for your Penguin Liberation rpms ;)
>
> As Blue told it, you're mixing the Guillaume's :-).
Mea Culpa, but thanks anyhow to the _real_ Guillaume ;)
--
��������Tom Brinkman � � � � � � � � Galveston Bay, USA
chmod +x /bin/Laden.al-Qaeda.Taliban
