Date: Fri, 23 Apr 2021 04:12:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255104] FreeBSD 13.0-RELEASE panic/crash with ipfw/dummynet/divert & wlan Message-ID: <bug-255104-227-GSwdwH6Knx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255104-227@https.bugs.freebsd.org/bugzilla/> References: <bug-255104-227@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=3D255104 Joshua Kinard <kumba@gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 551 | |64 Keywords| |crash, needs-patch, panic, | |regression Severity|Affects Only Me |Affects Some People --- Comment #5 from Joshua Kinard <kumba@gentoo.org> --- (In reply to Michael Meiszl from comment #4) Yeah, in my case, using a divert(4) rule seemed to be part of a trigger condition, and that may be related to a similar bug reported in Bug #255164, which has a commit (652908599b6f) that addresses issues in ipfw and divert = w/ the new unmapped mbuf feature. I tried applying that patch, along with sev= eral others (Bug #254309, 703419774f86; Bug #255041, 9bacbf1ae243). No dice. S= till able to reproduce random kernel crashes (not always a "panic" -- general protection fault this time). --=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-255104-227-GSwdwH6Knx>