Date: Sat, 23 Jun 2007 00:43:27 -0700 From: "Kevin Gerry" <sfpoof@gmail.com> To: "Kip Macy" <kip.macy@gmail.com> Cc: Attilio Rao <attilio@freebsd.org>, Jeff Roberson <jroberson@chesapeake.net>, freebsd-current@freebsd.org Subject: Re: Kernel Panic in latest -CURRENT Message-ID: <c027a39a0706230043l52bc4159v4374d0fcccd0692f@mail.gmail.com> In-Reply-To: <c027a39a0706222245le9d63daj8ca92db352bb0e16@mail.gmail.com> References: <c027a39a0706201141v4eba45a4vb815f130264b9e28@mail.gmail.com> <467A3869.3020706@FreeBSD.org> <20070622121008.T542@10.0.0.1> <c027a39a0706222057g508a3170naf3b9ce3148e8d62@mail.gmail.com> <b1fa29170706222107y28b53638ndd437aa8a9b2cbfe@mail.gmail.com> <c027a39a0706222133i6e4a23bek3e905a6f9c42c8b3@mail.gmail.com> <b1fa29170706222142s52c4f639p9577c21c36be9457@mail.gmail.com> <c027a39a0706222204t50694192ja2ae9baaacda58e0@mail.gmail.com> <c027a39a0706222245le9d63daj8ca92db352bb0e16@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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. > > So, recompiling with those two options removed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c027a39a0706230043l52bc4159v4374d0fcccd0692f>