Date: Wed, 21 Apr 2021 09:44:30 +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-FP0owiT92a@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 Michael Meiszl <michael@meiszl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael@meiszl.de --- Comment #2 from Michael Meiszl <michael@meiszl.de> --- (In reply to Joshua Kinard from comment #1) I just reported an error that seems to be alike to yours. Here its more than just a router, so its harder to locate. But basically I = have also tracked it down to ipfw panicing on incoming packets. Fatal trap 12: page fault while in kernel mode cpuid =3D 4; apic id =3D 04 fault virtual address =3D 0x388 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80d3fa67 stack pointer =3D 0x28:0xfffffe00df2feac0 frame pointer =3D 0x28:0xfffffe00df2feb20 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (swi1: netisr 0) trap number =3D 12 panic: page fault cpuid =3D 4 time =3D 1618988377 KDB: stack backtrace: #0 0xffffffff80c57345 at kdb_backtrace+0x65 #1 0xffffffff80c09d21 at vpanic+0x181 #2 0xffffffff80c09b93 at panic+0x43 #3 0xffffffff8108b187 at trap_fatal+0x387 #4 0xffffffff8108b1df at trap_pfault+0x4f #5 0xffffffff8108a83d at trap+0x27d #6 0xffffffff810617a8 at calltrap+0x8 #7 0xffffffff80bcae5d at ithread_loop+0x24d #8 0xffffffff80bc7c5e at fork_exit+0x7e #9 0xffffffff8106282e at fork_trampoline+0xe Uptime: 2m6s Runtime is random (seems to depend on how much traffic is incoming and since this is a central router and tunnel endpoint, it does not take long to cras= h) The system stays alive with ipfw disabled, but of course, this is no valid option for this machine (at least we are TWO now with this problem....) --=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-FP0owiT92a>