From owner-freebsd-bugs@freebsd.org Sun Jul 5 21:53: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 94B1E98EEE7 for ; Sun, 5 Jul 2015 21:53: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 71A831062 for ; Sun, 5 Jul 2015 21:53:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t65LrvYx076597 for ; Sun, 5 Jul 2015 21:53:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201368] Kernel panic vm_fault: fault on nofault entry Date: Sun, 05 Jul 2015 21:53: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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jake.guffey@jointheirstm.org 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: quoted-printable 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, 05 Jul 2015 21:53:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201368 Bug ID: 201368 Summary: Kernel panic vm_fault: fault on nofault entry Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jake.guffey@jointheirstm.org I just experienced a kernel panic/reboot due to a reported vm_fault. /var/log/messages provides: Jul 5 02:19:37 shemuel syslogd: kernel boot file is /boot/kernel/kernel Jul 5 02:19:37 shemuel kernel: panic: vm_fault: fault on nofault entry, ad= dr: c8f45000 Jul 5 02:19:37 shemuel kernel: KDB: stack backtrace: Jul 5 02:19:37 shemuel kernel: #0 0xc06f07e2 at kdb_backtrace+0x52 Jul 5 02:19:37 shemuel kernel: #1 0xc06bafe5 at panic+0x85 Jul 5 02:19:37 shemuel kernel: #2 0xc096439e at vm_fault_hold+0x211e Jul 5 02:19:37 shemuel kernel: #3 0xc0962241 at vm_fault+0x81 Jul 5 02:19:37 shemuel kernel: #4 0xc0a02931 at trap_pfault+0x291 Jul 5 02:19:37 shemuel kernel: #5 0xc0a020e1 at trap+0x5f1 Jul 5 02:19:37 shemuel kernel: #6 0xc09ee5ec at calltrap+0x6 Jul 5 02:19:37 shemuel kernel: #7 0xc085eb8a at sysctl_ip6_temppltime+0x3a Jul 5 02:19:37 shemuel kernel: #8 0xc06c5a4f at sysctl_root+0x2af Jul 5 02:19:37 shemuel kernel: #9 0xc06c6049 at userland_sysctl+0x1f9 Jul 5 02:19:37 shemuel kernel: #10 0xc06c5e08 at sys___sysctl+0x98 Jul 5 02:19:37 shemuel kernel: #11 0xc0a02f4e at syscall+0x38e Jul 5 02:19:37 shemuel kernel: #12 0xc09ee651 at Xint0x80_syscall+0x21 Jul 5 02:19:37 shemuel kernel: Uptime: 35d19h44m32s Jul 5 02:19:37 shemuel kernel: Physical memory: 787 MB Jul 5 02:19:37 shemuel kernel: Dumping 133 MB: 118 102 86 70 54 38 22 6=20 Jul 5 02:19:37 shemuel kernel: Dump complete Jul 5 02:19:37 shemuel kernel: Automatic reboot in 15 seconds - press a ke= y on the console to abort Jul 5 02:19:37 shemuel kernel: Rebooting... I do have a dump that I can provide if necessary. I have a custom kernel and can provide the configuration as well. This particular box runs two jails and that=E2=80=99s about it. At the time= of the panic, I issued "sysctl -a=E2=80=9D from within one of my jails. I was able= to reproduce the bug by doing the same thing after the reboot. This resulted i= n a corrupted filesystem which I'm fixing right now. --=20 You are receiving this mail because: You are the assignee for the bug.=