From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 20:52:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.bikeshed.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 82FC016A4CE; Thu, 8 Jan 2004 20:52:41 -0800 (PST) Received: from green.bikeshed.org (green@localhost [127.0.0.1]) by green.bikeshed.org (8.12.10/8.12.9) with ESMTP id i094qenU026528; Thu, 8 Jan 2004 23:52:41 -0500 (EST) (envelope-from green@green.bikeshed.org) Received: from localhost (green@localhost)i094qUP9026525; Thu, 8 Jan 2004 23:52:34 -0500 (EST) Message-Id: <200401090452.i094qUP9026525@green.bikeshed.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Bakul Shah In-Reply-To: Message from Bakul Shah <200401070921.i079LVic070520@gate.bitblocks.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jan 2004 23:52:30 -0500 Sender: green@green.bikeshed.org cc: Don Lewis cc: freebsd-current@freebsd.org cc: yurtesen@ispro.net.tr Subject: Re: FreeBSD Crashes with AMD 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: Fri, 09 Jan 2004 04:52:41 -0000 Bakul Shah wrote: > > I just thought my idea was pretty cute, it would also be nice to say to people > > with mystery SIGSEGV's that the break into the loader type 'memtest' and see > > if they get errors :) > > It was creative alright! > > My experience has been that memtest like tests do not help > with nasty, marginal power/timing related errors that only up > on a heavily loaded multiuser os. Start a few compiles, > finds, pure number crunching programs, throw in a few crashme > kind of tests and see how well things stand up. Then run the > same load at highest/lowest rated temperatures and for 24 > hours or more. Commonly referred to as "Prime95" in the Windows/OCers world, the Great Internet Mersennes Prime Search client is a very good indicator of system stability. It has a generic "burn in" mode you can run and a mode that actually searches for primes; it can be found in ports/math/mprime. I run an instance for each CPU on my A7M266-D (w/ECC), and it's pretty damn stable: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 55725 green 155 36 17372K 15104K RUN 0 606.1H 78.91% 78.91% mprime-real 27850 green 155 36 14532K 12228K CPU1 0 662.7H 76.81% 76.81% mprime-real -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\