On Fri, 3 Jul 2009, Ian J Hart wrote:
Is this likely to be hardware? Details will follow if not.
This looks like a kernel NULL pointer deference (faulting address 0x0), which means it is most likely a kernel bug, although it could be triggered by a hardare problem. If this early in the boot or a diskless box, hence no dump device?
Robert N M Watson Computer Laboratory University of Cambridge
[copied from a screen dump] Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff807c6c12 stack pointer = 0x10:0xffffffff510e7890 frame pointer = 0x10:0xffffff00054a6c90 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 = 75372 (printf) trap number = 12 panic: page fault cpuid = 1 uptime: 8m2s Cannot dump. No dump device defined. -- ian j hart ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
