Date: Tue, 17 Sep 2002 21:33:09 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Martin Blapp <mb@imp.ch> Cc: Terry Lambert <tlambert2@mindspring.com>, Nate Lawson <nate@root.org>, current@freebsd.org, peter@freebsd.org Subject: Re: Crashdumps available for download ... please help Message-ID: <Pine.NEB.3.96L.1020917213054.75372E-100000@fledge.watson.org> In-Reply-To: <20020917222622.U52781-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Sep 2002, Martin Blapp wrote: > If you don't beleave it or not. I've taken out again (I've already > switched them once) one bank of 512M ram and since then I've not had any > panics anymore. > > Can a ram error occur after a system has been fine one month ? Chances are, if you change an important variable such as memory size, it will change the failure mode for this bug. Carefully marking the memory so you know which is which, find replacement memory of identical size and other characteristics, and see if the failure comes back. If the failure comes back with different memory, the chances of it being a problem with the memory are pretty low. However, if you're going to halve the available memory, you're going to substantially change the behavior of the system for large and parallel builds, because the swapping/paging behavior will probably be quite different, especially if your working set is larger than 512mb and smaller than 1gb. I.e., be careful that tweaks changing the behavior of your system aren't just masking the real bug. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020917213054.75372E-100000>