Date: Wed, 28 Mar 2001 07:08:32 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: John Baldwin <jhb@FreeBSD.ORG> Cc: obrien@FreeBSD.ORG, alpha@FreeBSD.ORG, Andrew Gallatin <gallatin@cs.duke.edu>, markm@FreeBSD.ORG Subject: Re: dump(8) (vfs_object_create() panics: found the problem) Message-ID: <20010328070832.U26138@gsmx07.alcatel.com.au> In-Reply-To: <XFMail.010327115639.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on Tue, Mar 27, 2001 at 11:56:39AM -0800 References: <XFMail.010326172439.jhb@FreeBSD.org> <XFMail.010327115639.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010328070832.U26138>