From owner-freebsd-alpha  Tue Mar 27 13: 9:22 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0142637B718; Tue, 27 Mar 2001 13:09:18 -0800 (PST)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1])
	by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA06037;
	Wed, 28 Mar 2001 07:08:37 +1000 (EST)
Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au
 (PMDF V5.2-32 #37645) with ESMTP id <01K1PZKI7NQ8S3CYQU@cim.alcatel.com.au>;
 Wed, 28 Mar 2001 07:08:34 +1100
Received: (from jeremyp@localhost)	by gsmx07.alcatel.com.au (8.11.1/8.11.1)
 id f2RL8WR46094; Wed, 28 Mar 2001 07:08:32 +1000 (EST envelope-from jeremyp)
Content-return: prohibited
Date: Wed, 28 Mar 2001 07:08:32 +1000
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: dump(8)  (vfs_object_create() panics: found the problem)
In-reply-to: <XFMail.010327115639.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on
 Tue, Mar 27, 2001 at 11:56:39AM -0800
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: obrien@FreeBSD.ORG, alpha@FreeBSD.ORG,
	Andrew Gallatin <gallatin@cs.duke.edu>, markm@FreeBSD.ORG
Mail-Followup-To: John Baldwin <jhb@FreeBSD.ORG>, obrien@FreeBSD.ORG,
	alpha@FreeBSD.ORG, Andrew Gallatin <gallatin@cs.duke.edu>,
	markm@FreeBSD.ORG
Message-id: <20010328070832.U26138@gsmx07.alcatel.com.au>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
User-Agent: Mutt/1.2.5i
References: <XFMail.010326172439.jhb@FreeBSD.org>
 <XFMail.010327115639.jhb@FreeBSD.org>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On 2001-Mar-27 11:56:39 -0800, John Baldwin <jhb@FreeBSD.ORG> wrote:
>Ok, as I said earlier, only the pointer to the vnop function table is
>spammed, the rest of the vnode is ok.  I tracked this down to the big
>/dev/random overhaul commits of March 11.  Removing 'device random'
>from my kernel gets rid of the panic but breaks ssh. :( A kernel just
>before the Mar 11 /dev/random commits boots fine, and one just after
>panics. :(

This isn't the signal-related problem that Drew and I are seeing:
I'm still running a kernel from before the /dev/random overhaul.
It's possible that the real problem is elsewhere and the changes
to /dev/random just made it more visible.

Peter

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message