From owner-freebsd-stable@FreeBSD.ORG Fri Jul 25 07:59:06 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 1826837B401; Fri, 25 Jul 2003 07:59:06 -0700 (PDT) Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB18543F75; Fri, 25 Jul 2003 07:59:04 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta01-svc.ntlworld.comESMTP <20030725145903.DFJZ21249.mta01-svc.ntlworld.com@llama.fishballoon.org>; Fri, 25 Jul 2003 15:59:03 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19g41T-0002EC-0T; Fri, 25 Jul 2003 15:58:19 +0100 Date: Fri, 25 Jul 2003 15:58:18 +0100 From: Scott Mitchell To: Robert Watson Message-ID: <20030725145818.GC6218@llama.fishballoon.org> References: <20030725123959.GB6218@llama.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org cc: Brian Behlendorf 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:59:06 -0000 On Fri, Jul 25, 2003 at 10:28:52AM -0400, Robert Watson wrote: > 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 :-). Thanks Robert - assuming I can find the relevant tool, I'll try that. This is a 3-year old Intel LG440GX+ system. It's only 'new' in the sense that it hasn't been used for anything for 2.5 of those 3 years... There's probably a CD around somewhere with some diagnostic tools for it. I do have a GB of RAM sitting here to be distributed between this machine and its twin. I will try putting the whole lot in this machine and see if that makes any difference to the behaviour. Cheers, Scott