Marcel Moolenaar wrote: > > 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. > Don't know about "expects to be the only child" but I did was jhb said was right. If you know otherwise please fix it. SamReceived on Tue Mar 04 2008 - 04:13:47 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:28 UTC