Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Crash Report

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 525 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      mhowland24
      last edited by

      Hey guys, I just noticed I'm having some connectivity issues on my unraid server so I logged into pfsense and noticed that a crash report was available. Hopefully a dev can have a look and let me know whats going on, thanks

      textdump.tar.0

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        Important part of that is:

        db:0:kdb.enter.default>  show pcpu
        cpuid        = 7
        dynamic pcpu = 0xfffffe02a8822580
        curthread    = 0xfffff80006621620: pid 12 "irq264: bce0"
        curpcb       = 0xfffffe000031cb80
        fpcurthread  = none
        idlethread   = 0xfffff8000623d620: tid 100010 "idle: cpu7"
        curpmap      = 0xffffffff834f1c40
        tssp         = 0xffffffff835a35a8
        commontssp   = 0xffffffff835a35a8
        rsp0         = 0xfffffe000031cb80
        gs32p        = 0xffffffff835aa200
        ldt          = 0xffffffff835aa240
        tss          = 0xffffffff835aa230
        tlb gen      = 896087
        db:0:kdb.enter.default>  bt
        Tracing pid 12 tid 100107 td 0xfffff80006621620
        kdb_enter() at kdb_enter+0x3b/frame 0xfffffe000031c600
        vpanic() at vpanic+0x19b/frame 0xfffffe000031c660
        panic() at panic+0x43/frame 0xfffffe000031c6c0
        trap_pfault() at trap_pfault/frame 0xfffffe000031c710
        trap_pfault() at trap_pfault+0x49/frame 0xfffffe000031c770
        trap() at trap+0x29d/frame 0xfffffe000031c880
        calltrap() at calltrap+0x8/frame 0xfffffe000031c880
        --- trap 0xc, rip = 0xffffffff80520cf0, rsp = 0xfffffe000031c950, rbp = 0xfffffe000031c9e0 ---
        bce_intr() at bce_intr+0x420/frame 0xfffffe000031c9e0
        intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe000031ca20
        ithread_loop() at ithread_loop+0xe7/frame 0xfffffe000031ca70
        fork_exit() at fork_exit+0x83/frame 0xfffffe000031cab0
        fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe000031cab0
        --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
        

        So something in the bce(4) driver. Strangely it appears to have hit that as it was shutting down:

        <6>pflog0: promiscuous mode disabled
        Waiting (max 60 seconds) for system process `vnlru' to stop... done
        Waiting (max 60 seconds) for system process `bufdaemon' to stop... done
        Waiting (max 60 seconds) for system process `syncer' to stop... 
        Syncing disks, vnodes remaining... 0 0 done
        All buffers synced.
        Uptime: 6d23h24m52s
        ukbd0: detached
        uhid0: detached
        uhub4: detached
        uhub3: detached
        
        
        Fatal trap 12: page fault while in kernel mode
        cpuid = 7; apic id = 07
        fault virtual address	= 0x10
        fault code		= supervisor read data, page not present
        instruction pointer	= 0x20:0xffffffff80520cf0
        stack pointer	        = 0x28:0xfffffe000031c950
        frame pointer	        = 0x28:0xfffffe000031c9e0
        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 (irq264: bce0)
        trap number		= 12
        panic: page fault
        cpuid = 7
        KDB: enter: panic
        

        No time stamps to be sure though, is that right?

        Any reason you're still running 2.4.5p1?

        Steve

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          mhowland24 @stephenw10
          last edited by

          @stephenw10 I actually just updated to 2.5.2, but the notification for the crash report was still there so I decided to post it here. Should I clear it and hope for the best?

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.