From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 03:29:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 794CD37B401; Mon, 4 Aug 2003 03:29:55 -0700 (PDT) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84FDB43F3F; Mon, 4 Aug 2003 03:29:53 -0700 (PDT) (envelope-from Holger.Kipp@alogis.com) Received: (from hk@localhost) by alogis.com (8.11.1/8.9.3) id h74AT7h38477; Mon, 4 Aug 2003 12:29:07 +0200 (CEST) (envelope-from hk) Date: Mon, 4 Aug 2003 12:29:07 +0200 From: Holger Kipp To: Scott Mitchell Message-ID: <20030804122907.A38327@intserv.int1.b.intern> References: <20030725123959.GB6218@llama.fishballoon.org> <20030725145818.GC6218@llama.fishballoon.org> <51260000.1059145481@lerlaptop-red.iadfw.net> <20030804101402.GB27179@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20030804101402.GB27179@llama.fishballoon.org>; from scott+freebsd@fishballoon.org on Mon, Aug 04, 2003 at 11:14:02AM +0100 cc: Robert Watson cc: Brian Behlendorf cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 10:29:55 -0000 On Mon, Aug 04, 2003 at 11:14:02AM +0100, Scott Mitchell wrote: > On Fri, Jul 25, 2003 at 10:04:41AM -0500, Larry Rosenman wrote: > > you might also look at http://www.memtest86.com/ for a free memtest > > diagnostic. > > I let the server run memtest86 for most of the last weekend - it got > through 37 loops of its extended test sequence over ~45 hours of > testing. No errors were reported, so I guess the hardware is clean. memtest86 might not find all hardware/memory related problems, whilst make -j8 buildworld still gives problems. We had this problem once and it took some time to find out that the high-quality memory-chips and the high-quality mainboard were not exactly compatible. In fact we did speak with the technicians of both companies (those providing the RAM modules and those responsible for the board). memtest didn't show anything, but exchanging RAM modules (or board) got rid of the errors. Regards, Holger Kipp