Date: Mon, 3 Mar 2008 20:32:26 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: "George V. Neville-Neil" <gnn@FreeBSD.org>, re@FreeBSD.org, "current@freebsd.org" <current@FreeBSD.org> Subject: Re: IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE! Message-ID: <723D012C-7907-4CFC-B134-C5E5A0B486D9@mac.com> In-Reply-To: <47CCB187.8070808@FreeBSD.org> References: <47CCB187.8070808@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 3, 2008, at 6:18 PM, Maxim Sobolev wrote: > Hi, > > It appears to be that "options IPSEC" along with "device crypto" > breaks FreeBSD/powerpc kernel badly. When enabling these options, > apparently kernel doesn't perform any initialization tasks (I don't > see usual probe/init sequence output) but jumps straight into root > fs mounting after initing crypto(4) and ipsec(4), which is not > usable since no devices has been attached. Keyboard is not working > either. The problem is with device crypto. It attaches to nexus(4) and expects to be the only child. As you can see from the log, all children of nexus suddenly become instantiations of cryptosoft(4) rather then the usual drivers that attach. The swcr_probe() function should check that the device it gets is really the one created for it. FYI, -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?723D012C-7907-4CFC-B134-C5E5A0B486D9>