IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE!
sam at errno.com
Mon Mar 3 21:13:47 PST 2008
Marcel Moolenaar wrote:
> On Mar 3, 2008, at 6:18 PM, Maxim Sobolev wrote:
>> 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.
More information about the freebsd-current