Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Mar 2004 16:03:18 +0100
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Colin Percival <colin.percival@wadham.ox.ac.uk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: detecting overheating processors? 
Message-ID:  <78841.1078239798@critter.freebsd.dk>
In-Reply-To: Your message of "Tue, 02 Mar 2004 12:57:26 GMT." <6.0.1.1.1.20040302124613.03af9150@imap.sfu.ca> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <6.0.1.1.1.20040302124613.03af9150@imap.sfu.ca>, Colin Percival writes:
>   I'm seeing something very interesting with FreeBSD Update: Lots
>of overheating processors.  FreeBSD Update operates by checking
>MD5 hashes, applying patches, and checking the MD5 hashes of the
>patched files.  If the file is wrong after patching, it downloads
>the entire file (and verifies its hash).

In my experience MD5 does seem to be a really good CPU heater.

Rather than putting any "burn-in-test" functionality into any one
program, be it sysinstall or otherwise, I would prefer to have a
program called "stress" which could be run at any time to test
hardware.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78841.1078239798>