Date: Thu, 24 Jun 2004 14:22:44 -0500 (CDT) From: "Conrad J. Sabatier" <conrads@cox.net> To: Damian Gerow <dgerow@afflictions.org> Cc: freebsd-current@freebsd.org Subject: Re: Panic on today's -current Message-ID: <XFMail.20040624142244.conrads@cox.net> In-Reply-To: <20040624142347.GD28051@afflictions.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24-Jun-2004 Damian Gerow wrote: > Thus spake Conrad J. Sabatier (conrads@cox.net) [24/06/04 10:18]: >: On 24-Jun-2004 Beecher Rintoul wrote: >: > Hi, >: > >: > I'm getting a panic on today's -current kernel. I don't have a >: > serial >: > cable so >: > I couldn't save the message, but it panics after loading lo0. >: >: Same here. Just after, or during, the configuration of lo0. >: >: On a normal boot, the next thing to appear just after lo0 is: >: >: filter sync'd >: starting dhclient >: >: Perhaps it has something to do with ipf and/or pf? I have both >: configured into my kernel. > > See my thread 'ipf 3.4.35 woes' -- I'm using ipf, but not pf, and > seeing exactly the same thing. And if I turn off the loading of ipf > rulesets on boot, the panic goes away. Reloading them manually > afterwards doesn't cause the panic. Just upgraded the system and tried this. It worked without the loading of any ipf/ipnat stuff at boot time. Manually loading the rules after the system was up was fine, just as you said. I removed pf from my kernel, btw, since I wasn't using it anyway, but still have ipf (obviously). -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20040624142244.conrads>