crash report help



  • Hello folks,
    I'm looking into some assistance as to why my pfSense keeps crashing. It's appears to be random, any advice/feedback is appreciated. It is an older system, aside from the 4 port NIC, just bought that so I wouldn't be surprised if it turns out to be the ram or something like that.

    Thanks

    textdump.tar.0


  • LAYER 8

    yeah my 2 cent is on bad ram, check with memtest
    if it is so old I would also check if there are some inflated capacitors


  • Netgate Administrator

    Relevant part of ther crash log is:

    db:0:kdb.enter.default>  show pcpu
    cpuid        = 0
    dynamic pcpu = 0xc26380
    curthread    = 0xfffff80004d22000: pid 0 "bge0 taskq"
    curpcb       = 0xfffffe011a584cc0
    fpcurthread  = none
    idlethread   = 0xfffff8000495c000: tid 100003 "idle: cpu0"
    curpmap      = 0xffffffff82b85998
    tssp         = 0xffffffff82bb6810
    commontssp   = 0xffffffff82bb6810
    rsp0         = 0xfffffe011a584cc0
    gs32p        = 0xffffffff82bbd068
    ldt          = 0xffffffff82bbd0a8
    tss          = 0xffffffff82bbd098
    db:0:kdb.enter.default>  bt
    Tracing pid 0 tid 100079 td 0xfffff80004d22000
    kdb_enter() at kdb_enter+0x3b/frame 0xffffffff82b0e840
    vpanic() at vpanic+0x194/frame 0xffffffff82b0e8a0
    panic() at panic+0x43/frame 0xffffffff82b0e900
    dblfault_handler() at dblfault_handler+0x1de/frame 0xffffffff82b0e9d0
    Xdblfault() at Xdblfault+0xba/frame 0xffffffff82b0e9d0
    --- trap 0x17, rip = 0xffffffff8051823e, rsp = 0xf958e0fffff8007f, rbp = 0xfffffe011a584b20 ---
    bge_intr_task() at bge_intr_task+0x13e/frame 0xfffffe011a584b20
    taskqueue_run_locked() at taskqueue_run_locked+0x154/frame 0xfffffe011a584b80
    taskqueue_thread_loop() at taskqueue_thread_loop+0x98/frame 0xfffffe011a584bb0
    fork_exit() at fork_exit+0x83/frame 0xfffffe011a584bf0
    fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe011a584bf0
    --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
    db:0:kdb.enter.default>  ps
    

    So something with a bge interrupt or very near it. Double fault can be hard to pin down though.

    If this the first time you have seen in crash? Does it appear to be the same crash?

    Can you disable or remove the bge NIC as a test?

    Steve



  • Thanks for the replies. I've ordered new ram just to eliminate that being an issue.

    I have 2 other crash logs

    Here's the first (happened about 6 days after OP):

    db:0:kdb.enter.default>  show pcpu
    cpuid        = 1
    dynamic pcpu = 0xfffffe0193727380
    curthread    = 0xfffff80016510620: pid 58027 "unbound-control"
    curpcb       = 0xfffffe011d3c0cc0
    fpcurthread  = 0xfffff80016510620: pid 58027 "unbound-control"
    idlethread   = 0xfffff8000495b620: tid 100004 "idle: cpu1"
    curpmap      = 0xffffffff82b85998
    tssp         = 0xffffffff82bb6878
    commontssp   = 0xffffffff82bb6878
    rsp0         = 0xfffffe011d3c0cc0
    gs32p        = 0xffffffff82bbd0d0
    ldt          = 0xffffffff82bbd110
    tss          = 0xffffffff82bbd100
    db:0:kdb.enter.default>  bt
    Tracing pid 58027 tid 100435 td 0xfffff80016510620
    vm_object_terminate() at vm_object_terminate+0x332/frame 0xfffffe011d3c0950
    vm_object_deallocate() at vm_object_deallocate+0x28/frame 0xfffffe011d3c09b0
    _vm_map_unlock() at _vm_map_unlock+0xd9/frame 0xfffffe011d3c09d0
    vm_map_remove() at vm_map_remove+0xb2/frame 0xfffffe011d3c0a00
    vmspace_exit() at vmspace_exit+0xc9/frame 0xfffffe011d3c0a40
    exit1() at exit1+0x5c9/frame 0xfffffe011d3c0ab0
    sys_sys_exit() at sys_sys_exit+0xd/frame 0xfffffe011d3c0ac0
    amd64_syscall() at amd64_syscall+0xa38/frame 0xfffffe011d3c0bf0
    fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe011d3c0bf0
    --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x801b7c32a, rsp = 0x7fffffffec38, rbp = 0x7fffffffec50 ---
    

    Here's the other (1 day after the one above) - this also has a panic.txt (vm_fault: fault on nofault entry, addr: fffffe00de340000):

    db:0:kdb.enter.default>  show pcpu
    cpuid        = 0
    dynamic pcpu = 0xc26380
    curthread    = 0xfffff801285ce000: pid 15614 "unbound-control"
    curpcb       = 0xfffffe011d508cc0
    fpcurthread  = 0xfffff801285ce000: pid 15614 "unbound-control"
    idlethread   = 0xfffff8000495c000: tid 100003 "idle: cpu0"
    curpmap      = 0xfffff80128614138
    tssp         = 0xffffffff82bb6810
    commontssp   = 0xffffffff82bb6810
    rsp0         = 0xfffffe011d508cc0
    gs32p        = 0xffffffff82bbd068
    ldt          = 0xffffffff82bbd0a8
    tss          = 0xffffffff82bbd098
    db:0:kdb.enter.default>  bt
    Tracing pid 15614 tid 100505 td 0xfffff801285ce000
    kdb_enter() at kdb_enter+0x3b/frame 0xfffffe011d508140
    vpanic() at vpanic+0x194/frame 0xfffffe011d5081a0
    panic() at panic+0x43/frame 0xfffffe011d508200
    vm_fault_hold() at vm_fault_hold+0x244a/frame 0xfffffe011d508330
    vm_fault() at vm_fault+0x75/frame 0xfffffe011d508370
    trap_pfault() at trap_pfault+0x14c/frame 0xfffffe011d5083d0
    trap() at trap+0x2c7/frame 0xfffffe011d5084e0
    calltrap() at calltrap+0x8/frame 0xfffffe011d5084e0
    --- trap 0xc, rip = 0xffffffff830cd41f, rsp = 0xfffffe011d5085b0, rbp = 0xfffffe011d5085f0 ---
    zfs_freebsd_access() at zfs_freebsd_access+0x1f/frame 0xfffffe011d5085f0
    VOP_ACCESS_APV() at VOP_ACCESS_APV+0x7c/frame 0xfffffe011d508620
    vfs_cache_lookup() at vfs_cache_lookup+0x91/frame 0xfffffe011d508680
    VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x7c/frame 0xfffffe011d5086b0
    lookup() at lookup+0x6a1/frame 0xfffffe011d508740
    namei() at namei+0x489/frame 0xfffffe011d508810
    vn_open_cred() at vn_open_cred+0x231/frame 0xfffffe011d508950
    kern_openat() at kern_openat+0x20c/frame 0xfffffe011d508ac0
    amd64_syscall() at amd64_syscall+0xa38/frame 0xfffffe011d508bf0
    fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe011d508bf0
    --- syscall (5, FreeBSD ELF64, sys_open), rip = 0x801be12aa, rsp = 0x7fffffffdd88, rbp = 0x7fffffffddc0 ---
    

  • Netgate Administrator

    Those look more like ram errors. They are completely different the earlier crash.


Log in to reply