From owner-freebsd-current@FreeBSD.ORG  Tue Mar  2 07:03:24 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D418516A4CE
	for <freebsd-current@freebsd.org>;
	Tue,  2 Mar 2004 07:03:24 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7DCE743D3F
	for <freebsd-current@freebsd.org>;
	Tue,  2 Mar 2004 07:03:23 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i22F3Ikp078842;
	Tue, 2 Mar 2004 16:03:18 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Colin Percival <colin.percival@wadham.ox.ac.uk>
From: "Poul-Henning Kamp" <phk@phk.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> 
Date: Tue, 02 Mar 2004 16:03:18 +0100
Message-ID: <78841.1078239798@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: detecting overheating processors? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2004 15:03:25 -0000

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.