Date: Fri, 25 Jul 2003 15:58:18 +0100 From: Scott Mitchell <scott+freebsd@fishballoon.org> To: Robert Watson <rwatson@freebsd.org> Cc: Brian Behlendorf <brian@collab.net> Subject: Re: cvs pserver sig11 on 4.8-R Message-ID: <20030725145818.GC6218@llama.fishballoon.org> In-Reply-To: <Pine.NEB.3.96L.1030725102648.31689B-100000@fledge.watson.org> References: <20030725123959.GB6218@llama.fishballoon.org> <Pine.NEB.3.96L.1030725102648.31689B-100000@fledge.watson.org>
index | next in thread | previous in thread | raw e-mail
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, Scotthelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030725145818.GC6218>