Date: Tue, 07 Jul 2015 21:43:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198208] FreeBSD 10.1 multiple kernel panics Message-ID: <bug-198208-8-WnQJA87lWQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198208-8@https.bugs.freebsd.org/bugzilla/> References: <bug-198208-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198208 --- Comment #16 from Dan <lists.dan@gmail.com> --- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198208-8-WnQJA87lWQ>