Date: Wed, 03 Mar 2004 12:04:26 -0500 From: "Brian F. Feldman" <green@freebsd.org> To: avleeuwen@piwebs.com Cc: Colin Percival <colin.percival@wadham.ox.ac.uk> Subject: Re: detecting overheating processors? Message-ID: <200403031704.i23H4QYn013054@green.homeunix.org> In-Reply-To: Message from Arjan van Leeuwen <avleeuwen@piwebs.com> <200403021941.40072.avleeuwen@piwebs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Arjan van Leeuwen <avleeuwen@piwebs.com> 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. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403031704.i23H4QYn013054>