From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 07:29:41 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 3188637B401 for ; Fri, 25 Jul 2003 07:29:41 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 505F643FBD for ; Fri, 25 Jul 2003 07:29:40 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h6PESrai032145; Fri, 25 Jul 2003 10:28:53 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h6PESqr6032142; Fri, 25 Jul 2003 10:28:52 -0400 (EDT) Date: Fri, 25 Jul 2003 10:28:52 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Scott Mitchell In-Reply-To: <20030725123959.GB6218@llama.fishballoon.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Fri, 25 Jul 2003 14:29:41 -0000 On Fri, 25 Jul 2003, Scott Mitchell wrote: > On Wed, Jul 23, 2003 at 02:02:55PM -0700, Doug White wrote: > > > > Does the new machine have ECC memory? If not, it could be something as > > simple as bad RAM in the new system. > > I've just done four successive buildworlds on this machine, one with > -j4, just for fun. They all completed without complaint, so I'm > reasonably confident there's no dodgy RAM here. > > I'll send bug reports to FreeBSD and cvshome, and stick with the 4.6R > binary in the meantime. I'd actually download your system vendor's memory diagnostic tool and run it in "No, really find the problem" mode, just to be on the safe side. I had a machine that had a one bit memory error that I didn't discover for years -- occasionally I'd see an odd segfault, but it turned out the page of memory usually got allocated to a bit of the kernel that didn't notice/care. Once in a while I'd recompile the kernel and the page would get used for something else, and turned up most frequently in Pine, and I would assume it was a Pine bug. I'd have saved myself a lot of trouble if I'd run the memory check the first time, so that's usually the solution I push on people now :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories