From owner-freebsd-stable Tue Sep 23 09:47:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA20427 for stable-outgoing; Tue, 23 Sep 1997 09:47:20 -0700 (PDT) Received: from ganymede.frii.com (ganymede.frii.com [208.146.240.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA20408 for ; Tue, 23 Sep 1997 09:47:14 -0700 (PDT) From: gnat@frii.com Received: from elara.frii.com (elara.frii.com [208.146.240.9]) by ganymede.frii.com (8.8.5/8.8.4) with ESMTP id KAA22789; Tue, 23 Sep 1997 10:47:38 -0600 (MDT) Received: (from gnat@localhost) by elara.frii.com (8.8.5/8.6.9) id KAA15511; Tue, 23 Sep 1997 10:47:09 -0600 (MDT) Date: Tue, 23 Sep 1997 10:47:09 -0600 (MDT) Message-Id: <199709231647.KAA15511@elara.frii.com> To: Tom Cc: stable@FreeBSD.ORG Subject: Re: Dying -STABLE machine In-Reply-To: References: <199709222133.PAA02262@elara.frii.com> Mime-Version: 1.0 (generated by tm-edit 7.103) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom writes: > Sounds like hardware. I bet you don't use parity memory do you? It turned out to be a dead power fan. It's replaced, but we're still getting the panics. Your question suggests you think the RAM is at fault. Is this a common thing? Nat