From owner-freebsd-stable Sat Jun 8 21:14:51 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12640 for stable-outgoing; Sat, 8 Jun 1996 21:14:51 -0700 (PDT) Received: from solar.os.com (root@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12630 for ; Sat, 8 Jun 1996 21:14:48 -0700 (PDT) Received: from jupiter (jupiter.os.com [199.232.136.66]) by solar.os.com (8.7/8.7.0) with SMTP id AAA03784; Sun, 9 Jun 1996 00:15:34 -0400 Message-Id: <199606090415.AAA03784@solar.os.com> X-Sender: craigs@solar X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 09 Jun 1996 00:11:54 -0400 To: Nate Williams From: craigs@os.com (Craig Shrimpton) Subject: Re: PANIC with Stable June 7th (bad dir?) Cc: stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >SRAM cache. If this is a fairly new system, this is often caused by bad >cache RAM. The easiest way to check it is to disable cache and see if >crashes occur again. > Hmmm... I wonder if this is what's been happening to me lately. I'm getting random re-boots without any log messages. I was attributing it to the "blown" sups over the last couple of weeks. -Craig =================================================================== Orbit Internet Email: craigs@os.com 400 Grove Street Phone: (508) 753-8776 Worcester, MA 01605 http://www.os.com/