Date: Fri, 10 Aug 2018 09:17:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230498] Fatal trap 12: page fault while in kernel mode in sysctl_dumpentry from sysctl NET_RT_DUMP Message-ID: <bug-230498-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230498 Bug ID: 230498 Summary: Fatal trap 12: page fault while in kernel mode in sysctl_dumpentry from sysctl NET_RT_DUMP Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: ian@niw.com.au We have seen a repeatable kernel panic that seems to originate from a sysctl route table dump (as used in netstat -r) This is occuring daily since upgrade from 10.3 to 11.2 stable. There is an unstabl link causing a reasonable number of routing table updates. Backtrace shows Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 08 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80950356 stack pointer = 0x28:0xfffffe084f5353e0 frame pointer = 0x28:0xfffffe084f535520 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 9837 (nsgproxy) trap number = 12 panic: page fault cpuid = 4 Uptime: 1d1h14m45s Dumping 1712 out of 32431 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% #0 doadump (textdump=<value optimized out>) at pcpu.h:230 230 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=<value optimized out>) at pcpu.h:230 #1 0xffffffff8082b16b in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff8082b557 in vpanic (fmt=<value optimized out>, ap=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0xffffffff8082b3d3 in panic (fmt=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0xffffffff80bb66d7 in trap_fatal (frame=0xfffffe084f535320, eva=0) at /usr/src/sys/amd64/amd64/trap.c:877 #5 0xffffffff80bb6a5b in trap_pfault (frame=0xfffffe084f535320, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:787 #6 0xffffffff80bb5f88 in trap (frame=0xfffffe084f535320) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0xffffffff80b97aac in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0xffffffff80950356 in sysctl_dumpentry (rn=0xfffff8012bf4b410, vw=0xfffffe084f535688) at /usr/src/sys/net/rtsock.c:1559 #9 0xffffffff8094acc0 in rn_walktree (h=<value optimized out>, f=<value optimized out>, w=<value optimized out>) at /usr/src/sys/net/radix.c:1094 #10 0xffffffff8094fcdf in sysctl_rtsock (oidp=<value optimized out>, arg1=<value optimized out>, arg2=<value optimized out>, req=<value optimized out>) at /usr/src/sys/net/rtsock.c:1916 #11 0xffffffff8083854b in sysctl_root_handler_locked (oid=0xffffffff81433718, arg1=0xfffffe084f535908, arg2=5, req=0xfffffe084f535840, tracker=0xfffffe084f5357b8) at /usr/src/sys/kern/kern_sysctl.c:165 #12 0xffffffff80837da1 in sysctl_root (arg1=0xfffffe084f535908, arg2=5) at /usr/src/sys/kern/kern_sysctl.c:1913 #13 0xffffffff808382c6 in userland_sysctl (td=<value optimized out>, name=0xfffffe084f535900, namelen=7, old=0x8039e7540, oldlenp=<value optimized out>, inkernel=<value optimized out>, new=0x0, newlen=0, retval=0xfffffe084f535968, flags=0) at /usr/src/sys/kern/kern_sysctl.c:2009 #14 0xffffffff8083814f in sys___sysctl (td=0xfffff802b8974000, uap=0xfffff802b8974538) at /usr/src/sys/kern/kern_sysctl.c:1943 #15 0xffffffff80bb77e8 in amd64_syscall (td=0xfffff802b8974000, traced=0) at subr_syscall.c:132 #16 0xffffffff80b9838d in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:494 -- 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-230498-227>