Date: Wed, 19 Jul 2017 10:12:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220830] STABLE/11 (11.1-RC3, with ZFS bootstrap loader r1.1) kernel (GENERIC) panic; integer divide fault, trap number 18, current process 16 (pf purge) Message-ID: <bug-220830-8-bSnxZ4Gb1X@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220830-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220830-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220830 pherman@frenchfries.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pherman@frenchfries.net --- Comment #4 from pherman@frenchfries.net --- Hi, I can reproduce this. This is a divide by zero in sys/netpfil/pf/pf.c=20 pf_purge_thread().=20 https://svnweb.freebsd.org/base/stable/11/sys/netpfil/pf/pf.c?annotate=3D31= 6640#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 or= der, or how to enforce this type of "dependency"? It smells like a race condition, which could be why not everyone can reprod= uce 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 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220830-8-bSnxZ4Gb1X>