From owner-freebsd-bugs@freebsd.org Tue Jul 7 21:43:12 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 B93C0995E6E for ; Tue, 7 Jul 2015 21:43:12 +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 A4FB219BC for ; Tue, 7 Jul 2015 21:43:12 +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 t67LhCYe014919 for ; Tue, 7 Jul 2015 21:43:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198208] FreeBSD 10.1 multiple kernel panics Date: Tue, 07 Jul 2015 21:43:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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 Many People X-Bugzilla-Who: lists.dan@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: Message-ID: In-Reply-To: References: 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: Tue, 07 Jul 2015 21:43:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198208 --- Comment #16 from Dan --- Removing all frag rules kept the box stable for a while, but now it is crashing again. I have going to have to go to 9.3. 10.1 is not usable for a production system. Here is an excerpt from core.txt: Fatal trap 12: page fault while in kernel mode cpuid = 11; apic id = 35 fault virtual address = 0x18 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80485761 stack pointer = 0x28:0xfffffe0467cbfa90 frame pointer = 0x28:0xfffffe0467cbfb20 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 = 12 (irq257: bce1) trap number = 12 panic: page fault cpuid = 11 KDB: stack backtrace: #0 0xffffffff80963000 at kdb_backtrace+0x60 #1 0xffffffff80928125 at panic+0x155 #2 0xffffffff80d258df at trap_fatal+0x38f #3 0xffffffff80d25bf8 at trap_pfault+0x308 #4 0xffffffff80d2525a at trap+0x47a #5 0xffffffff80d0b142 at calltrap+0x8 #6 0xffffffff808faf4b at intr_event_execute_handlers+0xab #7 0xffffffff808fb396 at ithread_loop+0x96 #8 0xffffffff808f8b6a at fork_exit+0x9a #9 0xffffffff80d0b67e at fork_trampoline+0xe Uptime: 3m3s -- You are receiving this mail because: You are the assignee for the bug.