From owner-freebsd-stable Fri Feb 15 5:29:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5879637B402 for ; Fri, 15 Feb 2002 05:29:17 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Feb 2002 13:29:16 +0000 (GMT) Date: Fri, 15 Feb 2002 13:29:15 +0000 From: David Malone To: Kris Kennaway Cc: charon@seektruth.org, Baldur Gislason , freebsd-stable@FreeBSD.ORG Subject: Re: Spontanious reboots Message-ID: <20020215132915.GA7865@walton.maths.tcd.ie> References: <02021417352704.04045@germanium> <20020214094353.A12018@xor.obsecurity.org> <200202150311.g1F3Brh29217@midway.uchicago.edu> <20020215002655.A19761@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020215002655.A19761@xor.obsecurity.org> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 15, 2002 at 12:26:55AM -0800, Kris Kennaway wrote: > In particular, memtest isn't a foolproof method of testing > memory..there are just too many things it cannot pick up. Physically > swap out the memory..it's the only way to eliminate that possibility. For example... We had a system which occasionally exhibited memory corruption (bit twiddling in certain parts of 4KB pages) and spent months trying to track it down. It happily passed a few days of running memtest. After replacing each bit of hardware in turn, we eventually replaced the motherboard and the problem went away. As far as I could see, the main difference between the working and non-working motherboard was a heat sink on top of the memory controler chip. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message