From owner-freebsd-current Wed Apr 23 23:21:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18773 for current-outgoing; Wed, 23 Apr 1997 23:21:41 -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 XAA18766 for ; Wed, 23 Apr 1997 23:21:37 -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 QAA26785; Thu, 24 Apr 1997 16:21:15 +1000 (EST) Message-Id: <199704240621.QAA26785@unique.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Josh Howard 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 22:03:48 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Apr 1997 16:21:15 +1000 From: David Nugent Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, I was trying to find a link between Gary Clark's hardware/software and > mine, but there didn't seem to be one. I've got a 6x86-133, 64megs using IDE, > he was also using IDE, so, I would hate think this was some massive bug in the > IDE code. Actually, this is my suspect as well. I don't even think NFS can be blamed here. It is set up as an NFS server, but it is rarely used. I can't imagine that a couple of inactive daemons might be triggering it (although stranger things have happened :-)). It might even be a bug that's been there all along, but the lite2 merges have brought it to light. Come to think of it, all of the other -current machines I run and work fine are scsi, or in one case, mostly scsi - aha and aic types. Hmm. Ok, it looks like only a coredump will tell, and right now that's a matter of waiting it out. :)