From owner-freebsd-current  Sun Oct 27 01:06:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA13836
          for current-outgoing; Sun, 27 Oct 1996 01:06:23 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA13830
          for <current@freebsd.org>; Sun, 27 Oct 1996 01:06:19 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vHQEb-0000Jq-00; Sun, 27 Oct 1996 01:06:17 -0700
To: current@freebsd.org
Subject: FYI: Sept 21 kernel + panics
Date: Sun, 27 Oct 1996 01:06:16 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vHQEb-0000Jq-00@rover.village.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've had three panics that haven't left a core file running a -current
kernel from Sept 21.  I have kernel core dumps enabled, and savecore
enabled on boot, yet I get nothing from savecore :-(.  This is after
about 10 days of uptime.  This last time I noticed emacs getting slow
about 48 hours before the panic.

Is there something else that I can enable to find out where it is
dying?

Is it worth trying to track down in this rev, or should I do a cvs
update in my /usr/src/sys and see if that fixes the problem :-).

Warner