From owner-freebsd-bugs  Sat Dec  2 20:23:27 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id UAA17295
          for bugs-outgoing; Sat, 2 Dec 1995 20:23:27 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA17252
          for <bugs@freebsd.org>; Sat, 2 Dec 1995 20:22:55 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA07904; Sun, 3 Dec 1995 15:17:33 +1100
Date: Sun, 3 Dec 1995 15:17:33 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199512030417.PAA07904@godzilla.zeta.org.au>
To: bugs@freebsd.org, uhclem%nemesis@fw.ast.com
Subject: Re: Mission Impossible-style crashes on 2.1.0
Sender: owner-bugs@freebsd.org
Precedence: bulk

>Finally it happened in front of me on one of the systems.  The system was
>reasonably idle (tind was active and I was in vi writing and no X), when
>the console keyboard went dead.  All the keyboard lights turned off
>(NUM LOCK is normally on) and disk activity stopped.  I tried changing
>screens and hitting a few keys like NUM LOCK, but no action.  I then
>unplugged and reconnected the keyboard.  That didn't help either.
>Then around 15 seconds after the system went dead, the screen cleared and
>the system rebooted.

This seems to be a normal panic except there is no console output
(PANIC_REBOOT_WAIT_TIME) is 15 seconds).

>Since there is no visible panic and nothing in the logs, I am
>looking for suggestions on how to investigate this problem.  I don't
>think a triple-fault is occurring, because the system reset would occur
>instantly.   The odd thing is the 15-second delay is consistent,

Try using a serial console (connect a 9600 bps terminal to sio0 and
boot with -h).

Bruce