Re: IPFW panic on boot

[Mark Felder]

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
> > 0xfe01226a33e0
> > vpanic() at vpanic+0x182/frame 0xfe01226a3460
> > kassert_panic() at kassert_panic+0x126/frame 0xfe01226a34d0
> > ipfw_rewrite_rule_uidx() at ipfw_rewrite_rule_uidx+0x258/frame
> > 0xfe01226a356
> > 0
> > 
> 
> Yes; ref. 
> 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
  f...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IPFW panic on boot

[David Wolfskill]

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
> 0xfe01226a33e0
> vpanic() at vpanic+0x182/frame 0xfe01226a3460
> kassert_panic() at kassert_panic+0x126/frame 0xfe01226a34d0
> ipfw_rewrite_rule_uidx() at ipfw_rewrite_rule_uidx+0x258/frame
> 0xfe01226a356
> 0
> 

Yes; ref. 
et seq.

For me, the problem was with r290334; r290345 fixed it (again, for me).

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature