From owner-freebsd-bugs@freebsd.org Sun Oct 11 05:21:57 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CB8AA11C0A for ; Sun, 11 Oct 2015 05:21:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 714657D0 for ; Sun, 11 Oct 2015 05:21:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9B5LvDG052051 for ; Sun, 11 Oct 2015 05:21:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203691] [panic] Fatal trap 12: page fault while in kernel mode (in function vfs_cache_lookup) Date: Sun, 11 Oct 2015 05:21:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: neovortex@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 05:21:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203691 Bug ID: 203691 Summary: [panic] Fatal trap 12: page fault while in kernel mode (in function vfs_cache_lookup) Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: neovortex@gmail.com A system that runs ZFS, a number of jails (some of which use nullfs across ZFS filesystems) and one bhyve VM is crashing every so often (crashes are usually occur with between a week and a couple of months). Running 10.2-RELEASE-p4 on amd64 with a GENERIC kernel installed from freebsd-update, although crashes have occurred on earlier 10.x versions as well although I can't recall exact version. Hardware has been tested (memtest and cpu stress tests) without issues. Disks are attached using a mix of AHCI and a LSI Logic SAS2008 card (mps driver). Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 06 fault virtual address = 0x10000002f fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff809d6e14 stack pointer = 0x28:0xfffffe0654b534e0 frame pointer = 0x28:0xfffffe0654b53560 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 = 8041 (find) trap number = 12 panic: page fault cpuid = 3 KDB: stack backtrace: #0 0xffffffff80984e30 at kdb_backtrace+0x60 #1 0xffffffff809489e6 at vpanic+0x126 #2 0xffffffff809488b3 at panic+0x43 #3 0xffffffff80d4aadb at trap_fatal+0x36b #4 0xffffffff80d4addd at trap_pfault+0x2ed #5 0xffffffff80d4a47a at trap+0x47a #6 0xffffffff80d307f2 at calltrap+0x8 #7 0xffffffff809d83dc at vfs_cache_lookup+0xac #8 0xffffffff80e71621 at VOP_LOOKUP_APV+0xa1 #9 0xffffffff809e0951 at lookup+0x5a1 #10 0xffffffff809e00b4 at namei+0x4d4 #11 0xffffffff809f471e at kern_statat_vnhook+0xae #12 0xffffffff809f462c at sys_fstatat+0x2c #13 0xffffffff80d4b3f7 at amd64_syscall+0x357 #14 0xffffffff80d30adb at Xfast_syscall+0xfb (kgdb) #0 doadump (textdump=) at pcpu.h:219 #1 0xffffffff80948642 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:451 #2 0xffffffff80948a25 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:758 #3 0xffffffff809488b3 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:687 #4 0xffffffff80d4aadb in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:851 #5 0xffffffff80d4addd in trap_pfault (frame=0xfffffe0654b53430, usermode=) at /usr/src/sys/amd64/amd64/trap.c:674 #6 0xffffffff80d4a47a in trap (frame=0xfffffe0654b53430) at /usr/src/sys/amd64/amd64/trap.c:440 #7 0xffffffff80d307f2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff809d6e14 in cache_lookup (dvp=0xfffff8059a1fbce8, vpp=0xfffffe0654b53858, cnp=0xfffffe0654b53880, tsp=0x0, ticksp=0x0) at /usr/src/sys/kern/vfs_cache.c:548 #9 0xffffffff809d83dc in vfs_cache_lookup (ap=) at /usr/src/sys/kern/vfs_cache.c:1039 #10 0xffffffff80e71621 in VOP_LOOKUP_APV (vop=, a=) at vnode_if.c:129 #11 0xffffffff809e0951 in lookup (ndp=0xfffffe0654b537f8) at vnode_if.h:54 #12 0xffffffff809e00b4 in namei (ndp=0xfffffe0654b537f8) at /usr/src/sys/kern/vfs_lookup.c:302 #13 0xffffffff809f471e in kern_statat_vnhook (td=0xfffff805d4e01000, flag=, fd=-100, path=0x801169a88
, pathseg=UIO_USERSPACE, sbp=0xfffffe0654b53910, hook=0xfffffe0000dcb000) at /usr/src/sys/kern/vfs_syscalls.c:2298 #14 0xffffffff809f462c in sys_fstatat (td=0x7e891088, uap=0xfffffe0654b53a40) at /usr/src/sys/kern/vfs_syscalls.c:2278 #15 0xffffffff80d4b3f7 in amd64_syscall (td=0xfffff805d4e01000, traced=0) at subr_syscall.c:134 #16 0xffffffff80d30adb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #17 0x00000008008b5f0a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) I have crash dumps enabled now, although only I only have the core from the most recent crash as mentioned above. Previous crashes have had the same backtrace. -- You are receiving this mail because: You are the assignee for the bug.