From owner-freebsd-stable Mon Aug 10 21:28:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03574 for freebsd-stable-outgoing; Mon, 10 Aug 1998 21:28:34 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03569 for ; Mon, 10 Aug 1998 21:28:32 -0700 (PDT) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id VAA03294; Mon, 10 Aug 1998 21:26:56 -0700 (PDT) (envelope-from jgrosch) Message-ID: <19980810212646.A3278@mooseriver.com> Date: Mon, 10 Aug 1998 21:26:46 -0700 From: Josef Grosch To: obrien@NUXI.com, Tom Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.7 crash Reply-To: jgrosch@mooseriver.com References: <19980810194311.A29027@nuxi.com> <19980810202758.A29238@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980810202758.A29238@nuxi.com>; from David O'Brien on Mon, Aug 10, 1998 at 08:27:58PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 10, 1998 at 08:27:58PM -0700, 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. Entropy, man. It's everywhere! Josef "Wow, trails!" Grosch -- Josef Grosch | Another day closer to a | FreeBSD 2.2.7 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message