https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220830
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from [email protected] --- Hi, I can reproduce this. This is a divide by zero in sys/netpfil/pf/pf.c pf_purge_thread(). https://svnweb.freebsd.org/base/stable/11/sys/netpfil/pf/pf.c?annotate=316640#l1446 The V_pf_default_rule.timeout array hasn't been initialized yet. This happens presumably because pf_load() is getting called before pfattach_vnet() (i.e. pf_load_vnet()). Anyone know what determines the order, or how to enforce this type of "dependency"? It smells like a race condition, which could be why not everyone can reproduce it, but on my hardware it's 100%. I also suspect this has to do with EARLY_AP_STARTUP, because I have yet to see the same panic with EARLY_AP_STARTUP disabled. Still testing. BTW, my kernel config is simple: include GENERIC device carp device pf #nooptions EARLY_AP_STARTUP -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
