Date: Mon, 11 Nov 2013 10:29:49 -0700 From: Tom Everett <tom@khubla.com> To: freebsd-questions@freebsd.org Subject: FreeBSD 9.2 crash under load Message-ID: <CAB3ij4CL14Kj6QGB-Zz8XPn8ycJUgW4QuhKThRy6kg_vN1aNBw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I'm experiencing a fairly repeatable crash under load. Most recently the crash under load was during numerous rsync jobs, at the same time as cross-compiling NetBSD in a jail. I have the crash log from dmesg (below). What do people typically do in situations like to, to determine if the problem is due to overheating, bad hardware, a kernel bug, bad RAM, etc? Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0xc > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80b7442d > stack pointer = 0x28:0xffffff846d11a780 > frame pointer = 0x28:0xffffff846d11a7c0 > 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 = 55420 (rsync) > trap number = 12 > panic: page fault > cpuid = 1 > KDB: stack backtrace: > #0 0xffffffff80947986 at kdb_backtrace+0x66 > #1 0xffffffff8090d9ae at panic+0x1ce > #2 0xffffffff80cf20d0 at trap_fatal+0x290 > #3 0xffffffff80cf2431 at trap_pfault+0x211 > #4 0xffffffff80cf29e4 at trap+0x344 > #5 0xffffffff80cdbd13 at calltrap+0x8 > #6 0xffffffff80b7473e at zone_fetch_slab+0x3e > #7 0xffffffff80b75b8d at uma_zalloc_arg+0x31d > #8 0xffffffff80959f84 at selfdalloc+0x64 > #9 0xffffffff8095bf34 at kern_select+0x594 > #10 0xffffffff8095c32d at sys_select+0x5d > #11 0xffffffff80cf187a at amd64_syscall+0x5ea -- A better world shall emerge based on faith and understanding - Douglas MacArthur
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB3ij4CL14Kj6QGB-Zz8XPn8ycJUgW4QuhKThRy6kg_vN1aNBw>