From owner-freebsd-current  Wed Apr 23 21:19:28 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA14293
          for current-outgoing; Wed, 23 Apr 1997 21:19:28 -0700 (PDT)
Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA14287
          for <freebsd-current@freebsd.org>; Wed, 23 Apr 1997 21:19:23 -0700 (PDT)
Received: from unique.usn.blaze.net.au (local [127.0.0.1])
	by unique.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id OAA24934;
	Thu, 24 Apr 1997 14:18:48 +1000 (EST)
Message-Id: <199704240418.OAA24934@unique.usn.blaze.net.au>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Josh Howard <obiwan@zeppelin.net>
cc: freebsd-current@freebsd.org
Subject: Re: Upgrading from 3.0-19970209-SNAP to -current 
In-reply-to: Your message of "Wed, 23 Apr 1997 20:54:45 MST."
             <XFMail.970423205637.obiwan@zeppelin.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 24 Apr 1997 14:18:48 +1000
From: David Nugent <davidn@unique.usn.blaze.net.au>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Kernel after the make world. I certainly hope you don't run in to the same
> random reboots I do..everyday. (an attempt to scare folks :-) I think I'm
> going to downgrade from -current to that snap...

FWIW, I'm seeing the same thing, on one machine out of 6 I run or
manage that are -current. And its the only one I haven't got DDB
enabled and where I don't have convenient physical access to the
machine. :)  [ok, swapcore on!]

I've been trying to reproduce the problem on the other machines,
but be damned if I can even see a pattern. It is a very uncomplicated
system P166/32mb RAM, 2 large EIDE drives, no X, just ppp dialin lines
with a digiboard card. Anyone else wish to exchange notes?