Date: Mon, 26 May 2008 14:28:21 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Marko Zec <zec@icir.org> Cc: "Bjoern A. Zeeb" <bz@freebsd.org>, Julian Elischer <julian@elischer.org>, freebsd-virtualization@freebsd.org Subject: Re: vimage kernel broken Message-ID: <483AACE5.3070207@FreeBSD.org> In-Reply-To: <200805261423.27766.zec@icir.org> References: <483834AD.9050208@FreeBSD.org> <200805261304.20497.zec@icir.org> <483AA979.5060504@FreeBSD.org> <200805261423.27766.zec@icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marko Zec wrote: > On Monday 26 May 2008 14:13:45 Kris Kennaway wrote: > ... >> Maybe I am using the wrong branch, can you confirm which is current? > > //depot/user/zec/vimage_7/... tracks RELENG_7 > //depot/projects/vimage/... tracks HEAD OK, that is the branch I was using. > I couldn't reproduce this panic on neither of the above branches, at > least not by solely enabling IPv6 and rpc.lockd. Try with a vimage kernel but CVS userland (I only rebuilt the kernel). It is possible that there was an ABI change that is causing the kernel to panic from unexpected input from userland. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483AACE5.3070207>