Date: Sun, 10 Dec 2017 21:13:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224231] [ipfw] kernel panic when using ipfw nat Message-ID: <bug-224231-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224231 Bug ID: 224231 Summary: [ipfw] kernel panic when using ipfw nat Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: me@rin.cat Fatal trap 9: general protection fault while in kernel mode cpuid =3D 6: apic id =3D 06=20 instruction pointer =3D Ox20:8xffffffff80ae9aa3=20 stack pointer =3D Ox28:8xfffffe085620e370=20 frame pointer =3D Ox28:0xfffffe085620e3a0=20 code segment =3D base 0x0, limit 0xfffff, type 0x1b=20 =3D DPL 0, pres 1, long 1, def32 0. gran 1=20 processor eflags =3D interrupt enabled, resume, IOPL =3D 0=20 current process =3D 952 (syncthing)=20 trap number =3D 9=20 panic: general protection fault=20 cpuid =3D 6=20 KDB: stack backtrace:=20 #0 0xffffffff80aadac7 at kdb_backtrace+0x67=20 #1 0xffffffff80a6bba6 at vpanic+0x186=20 #2 0xffffffff80a6ba13 at panic+0x43=20 #3 0xffffffff80edf832 at trap_fatal+0x322=20 #4 0xffffffff80edee9e at trap+0x5e=20 #5 0xffffffff88ec36d1 at calltrap+0x8=20 #6 0xffffffff80c80d37 at ip6_fragment+0x2e7=20 #7 0xffffffff80c82bce at ip6_output+0x1d5e=20 #8 0xffffffff80c532f9 at tcp_output+0x1939=20 #9 0xffffffff80c60fab at tcp6_usr_connect+0x2bb=20 #10 0xffffffff80af9c7f at kern_connectat+Ox11f=20 #11 0xffffffff80af9b37 at sys connect+0x77=20 #12 0xffffffff80ee0394 at amd64_sysca11+0x6c4=20 #13 0xffffffff8Oec39bb at Xfast_syscall+Oxfb This happened repeatedly when I do in-kernel nat with ipfw. When I disabled nat, no more panic. Memory dump available if needed (over 1GB). --=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-224231-8>