Kernel Panic in latest -CURRENT

Kevin Gerry sfpoof at gmail.com
Sat Jun 23 17:48:13 UTC 2007


Thanks. Seems that Manfred's crashing may have to do with options IPSEC as
well. At least, he has that in his kernel config. At least the issue seems
to be resolved.

On 6/23/07, Rong-en Fan <grafan at gmail.com> wrote:
>
> On 6/23/07, Kevin Gerry <sfpoof at gmail.com> wrote:
> > Well, so far, it doesn't crashed. I'm starting to wonder if the issue
> was
> > originally caused by including IPSEC in the kernel...
> >
> > Anyway, I'll be attempting to crash it in the ways it worked before...
> > (buildworld is awesome that way...)
> >
> > On 6/22/07, Kevin Gerry <sfpoof at gmail.com> wrote:
> > >
> > > Alright, I have run it with that in the loader.conf and tried removing
> > > everything from both.
> > >
> > > However, I also found while reading the boot mesages, the reason why
> > > mpsafenet is unset is because I have
> > > options         IPSEC
> > > options         IPSEC_ESP
> > > in the kernel.
>
> Try to use
>
> options FAST_IPSEC
> device crypto
>
> It currently only supports IPv4, IPv6 is being working on.
> FAST_IPSEC is mpsafe.
>
> Regards,
> Rong-En Fan
>
>
> > >
> > > So, recompiling with those two options removed.
> > _______________________________________________
> > freebsd-current at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscribe at freebsd.org"
> >
>


More information about the freebsd-current mailing list