From owner-freebsd-current  Wed Jul 24 05:28:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA16530
          for current-outgoing; Wed, 24 Jul 1996 05:28:51 -0700 (PDT)
Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16525
          for <freebsd-current@freebsd.org>; Wed, 24 Jul 1996 05:28:48 -0700 (PDT)
Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id IAA00291; Wed, 24 Jul 1996 08:39:04 -0400 (EDT)
From: "Amir Y. Rosenblatt" <amir@neuron.net>
Message-Id: <199607241239.IAA00291@prozac.neuron.net>
Subject: Re: A new twist on the reboot problems
To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com)
Date: Wed, 24 Jul 1996 08:39:04 -0400 (EDT)
Cc: amir@neuron.net, freebsd-current@freebsd.org, amir@garpac.com
In-Reply-To: <199607240704.AAA11312@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jul 24, 96 00:04:49 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Incidentally, if you want to be *sure* you capture all panic output,
> you might consider putting a comconsole into your kernel and hooking a
> serial terminal with scrollback and/or logging (old PC running kermit
> works fine) up to be the console.  Then, no matter what gets written,
> or not written, before the machine freaks out, and before fsck
> "cleans" everything, you have it all logged on a separate machine.

Good idea.  I'll hav to see if I can drag another machine to within 
serial-cable range.

> Out of curiosity, do you have "options DIAGNOSTIC" in your kernel?  If
> so, remove it, rebuild, reinstall.

Nope -- it's gone.  Last night the thing started making those clicking 
noises again and constantly rebooting.  I took it down for a bit, brought 
it up and it had trouble even getting sd0 to start up.  The clicking 
sounded like it could have been a breaker or something -- every time I 
heard it, the disk would cut out for a few seconds and then start back up 
again.  All my errors have been on sd0 which leads me to believe that 
either my power supply or that disk is hosed.  I have a spare 'cuda on 
hand which I'll be installing shortly to see if that's the problem.

	-Amir