Date: Wed, 04 Nov 2015 11:05:33 -0600 From: Mark Felder <feld@FreeBSD.org> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-current@freebsd.org Subject: Re: IPFW panic on boot Message-ID: <1446656733.2229984.429118665.5D1022A5@webmail.messagingengine.com> In-Reply-To: <20151104032910.GA21127@albert.catwhisker.org> References: <1446606508.4146764.428513625.0863258A@webmail.messagingengine.com> <20151104032910.GA21127@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 3, 2015, at 21:29, David Wolfskill wrote: > On Tue, Nov 03, 2015 at 09:08:28PM -0600, Mark Felder wrote: > > Recent ipfw commits now cause my firewall to panic on boot. I had to > > revert them and only pull in Adrian's ath fix which was to fix yet a > > different panic I was encountering... :-) > > > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe01226a33e0 > > vpanic() at vpanic+0x182/frame 0xfffffe01226a3460 > > kassert_panic() at kassert_panic+0x126/frame 0xfffffe01226a34d0 > > ipfw_rewrite_rule_uidx() at ipfw_rewrite_rule_uidx+0x258/frame > > 0xfffffe01226a356 > > 0 > > .... > > Yes; ref. <http://docs.FreeBSD.org/cgi/mid.cgi?20151103140436.GJ21127>; > et seq. > > For me, the problem was with r290334; r290345 fixed it (again, for me). > Mine was at r290340, so I was caught in the middle :-) -- Mark Felder ports-secteam member feld@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1446656733.2229984.429118665.5D1022A5>