From owner-freebsd-stable Mon Aug 10 22:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13519 for freebsd-stable-outgoing; Mon, 10 Aug 1998 22:59:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA13511 for ; Mon, 10 Aug 1998 22:59:44 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z67Si-0000MW-00; Mon, 10 Aug 1998 22:59:12 -0700 Date: Mon, 10 Aug 1998 22:59:08 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "David O'Brien" cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash In-Reply-To: <19980810202758.A29238@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 10 Aug 1998, David O'Brien wrote: > > > 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. Why not? Memory doesn't exactly give you warning signs before it fails, it just fails. Probably just a marginal component to begin within. Could also be a contact problem (ex. corrosion). > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message