From owner-freebsd-stable  Mon Aug 10 21:01:28 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA28301
          for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:01:28 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28267
          for <freebsd-stable@FreeBSD.ORG>; Mon, 10 Aug 1998 21:01:17 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA27672;
	Mon, 10 Aug 1998 21:01:23 -0700 (PDT)
Message-Id: <199808110401.VAA27672@implode.root.com>
To: obrien@NUXI.com
cc: Tom <tom@uniserve.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: 2.2.7 crash 
In-reply-to: Your message of "Mon, 10 Aug 1998 20:27:58 PDT."
             <19980810202758.A29238@nuxi.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 10 Aug 1998 21:01:23 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> > What's the next step to figuring out this problem?
>> 
>>   What you are seeing is almost certainly a hardware failure.
>
>Would memory just start going bad?  This machine has been stable running
>the 2.2-STABLE branch for over a year not.

   Memory errors can often go unnoticed if they happend to occur in bits
that previously were unused. The layout of the 2.2.7 kernel could have
moved the defective bits to a sensitive spot.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message