Date: Mon, 4 Aug 2003 12:29:07 +0200 From: Holger Kipp <Holger.Kipp@alogis.com> To: Scott Mitchell <scott+freebsd@fishballoon.org> Cc: freebsd-stable@freebsd.org Subject: Re: cvs pserver sig11 on 4.8-R Message-ID: <20030804122907.A38327@intserv.int1.b.intern> In-Reply-To: <20030804101402.GB27179@llama.fishballoon.org>; from scott%2Bfreebsd@fishballoon.org on Mon, Aug 04, 2003 at 11:14:02AM %2B0100 References: <20030725123959.GB6218@llama.fishballoon.org> <Pine.NEB.3.96L.1030725102648.31689B-100000@fledge.watson.org> <20030725145818.GC6218@llama.fishballoon.org> <51260000.1059145481@lerlaptop-red.iadfw.net> <20030804101402.GB27179@llama.fishballoon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030804122907.A38327>