Date: Thu, 23 Nov 2017 08:40:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 223813] kernel panic in mps driver in 11.1-p4 Message-ID: <bug-223813-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223813 Bug ID: 223813 Summary: kernel panic in mps driver in 11.1-p4 Product: Base System Version: 11.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: daniel@blodan.se Created attachment 188209 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188209&action= =3Dedit Entire core dump Hi! I just upgraded our firewall from 11.0 to 11.1-p4, however after about ~35-= 45 minutes it panics. After some poking around i saw there were quite a bit of changes in the mps driver so I'm guessing a bug snuck in there somewhere. I'm happy to apply a debug patch to get you more information to sort this o= ut if you need to. It panics with this stracktrace: Unread portion of the kernel message buffer: panic: vm_fault: fault on nofault entry, addr: fffffe00003eb000 cpuid =3D 4 KDB: stack backtrace: #0 0xffffffff80aadac7 at kdb_backtrace+0x67 #1 0xffffffff80a6bba6 at vpanic+0x186 #2 0xffffffff80a6ba13 at panic+0x43 #3 0xffffffff80d58b90 at vm_fault_hold+0x2070 #4 0xffffffff80d56ad5 at vm_fault+0x75 #5 0xffffffff80edf927 at trap_pfault+0xe7 #6 0xffffffff80edf0c6 at trap+0x286 #7 0xffffffff80ec36d1 at calltrap+0x8 #8 0xffffffff8067b346 at mps_ioctl+0x2e86 #9 0xffffffff8093ae38 at devfs_ioctl_f+0x128 #10 0xffffffff80ac9415 at kern_ioctl+0x255 #11 0xffffffff80ac914f at sys_ioctl+0x16f #12 0xffffffff80ee0394 at amd64_syscall+0x6c4 #13 0xffffffff80ec39bb at Xfast_syscall+0xfb And here is the doadump log: (kgdb) #0 doadump (textdump=3D<value optimized out>) at pcpu.h:222 #1 0xffffffff80a6b721 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80a6bbe0 in vpanic (fmt=3D<value optimized out>, ap=3D<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80a6ba13 in panic (fmt=3D<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80d58b90 in vm_fault_hold (map=3D<value optimized out>, vaddr=3D<value optimized out>, fault_type=3D1 '\001', fault_flags=3D<value optimized out>, m_hold=3D0x0) at /usr/src/sys/vm/vm_fault.c:524 #5 0xffffffff80d56ad5 in vm_fault (map=3D0xfffff80003000000, vaddr=3D<value optimized out>, fault_type=3D1 '\001', fault_flags=3D0) at /usr/src/sys/vm/vm_fault.c:475 #6 0xffffffff80edf927 in trap_pfault (frame=3D0xfffffe08595cb510, usermode= =3D0) at /usr/src/sys/amd64/amd64/trap.c:708 #7 0xffffffff80edf0c6 in trap (frame=3D0xfffffe08595cb510) at /usr/src/sys/amd64/amd64/trap.c:421 #8 0xffffffff80ec36d1 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #9 0xffffffff80edd63f in copyout () at /usr/src/sys/amd64/amd64/support.S:= 255 #10 0xffffffff8067b346 in mps_ioctl () at /usr/src/sys/dev/mps/mps_user.c:1= 040 #11 0xffffffff8093ae38 in devfs_ioctl_f (fp=3D0xfffff80013466e10, com=3D3224914180, data=3D0xfffffe08595cb870, cred=3D0xfffff80013892500, td=3D0xfffff8000ab48000) at /usr/src/sys/fs/devfs/devfs_vnops.c:791 #12 0xffffffff80ac9415 in kern_ioctl (td=3D<value optimized out>, fd=3D3, com=3D<value optimized out>, data=3D<value optimized out>) at file.h:323 #13 0xffffffff80ac914f in sys_ioctl (td=3D<value optimized out>, uap=3D0xfffffe08595cba30) at /usr/src/sys/kern/sys_generic.c:745 #14 0xffffffff80ee0394 in amd64_syscall (td=3D0xfffff8000ab48000, traced=3D= 0) at subr_syscall.c:135 #15 0xffffffff80ec39bb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #16 0x0000000000446adc in ?? () Previous frame inner to this frame (corrupt stack?) --=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-223813-8>