From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 09:04:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2FC9316A4CE; Wed, 3 Mar 2004 09:04:28 -0800 (PST) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.10/8.12.9) with ESMTP id i23H4Rws013058; Wed, 3 Mar 2004 12:04:27 -0500 (EST) (envelope-from green@green.homeunix.org) Received: from localhost (green@localhost)i23H4QYn013054; Wed, 3 Mar 2004 12:04:26 -0500 (EST) Message-Id: <200403031704.i23H4QYn013054@green.homeunix.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: avleeuwen@piwebs.com In-Reply-To: Message from Arjan van Leeuwen <200403021941.40072.avleeuwen@piwebs.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Mar 2004 12:04:26 -0500 Sender: green@green.homeunix.org cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: Colin Percival 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 17:04:28 -0000 Arjan van Leeuwen wrote: > On Tuesday 02 March 2004 16:03, Poul-Henning Kamp wrote: > > 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. > > I believe sysutils/cpuburn can do exactly that. It will generate a pretty maximal amount of heat, but won't actually tell you if something is "wrong" with the operations at that point. Using the "testing" mode of ports/math/mprime will, though. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\