Pfsense 2.2.4 panic/crash – submitted crash dump



  • as per https://doc.pfsense.org/index.php/Obtaining_Panic_Information_for_Developers, my WAN ip is 24.93.187.29 and the dump was submitted as of about 23:12 EST.

    Not sure what other information would be useful, I've seen this crash a few times over the past week or so and reading the crash dump seems not so easy.

    I can attach the crash dump here if necessary.


  • Rebel Alliance Developer Netgate

    I don't see anything from that IP address at all, do you have IPv6 perhaps? Or a second WAN?  I see a couple things near that time but nothing near the IP address given.



  • I do have ipv6 on WAN actually, address is 2605:a000:ffc0:69:48b8:d8e9:bcbb:fa5a

    does that bring up any results?


  • Rebel Alliance Developer Netgate

    Yep, that one was there.

    db:0:kdb.enter.default>  show pcpu
    cpuid        = 0
    dynamic pcpu = 0x5bf480
    curthread    = 0xc6700000: pid 11 "idle: cpu0"
    curpcb       = 0xe038ad60
    fpcurthread  = none
    idlethread   = 0xc6700000: tid 100003 "idle: cpu0"
    APIC ID      = 0
    currentldt   = 0x50
    db:0:kdb.enter.default>  bt
    Tracing pid 11 tid 100003 td 0xc6700000
    intr_execute_handlers(c66def38,e038ab98,0) at intr_execute_handlers+0x11/frame 0xe038ab70
    lapic_handle_intr(39,e038ab98) at lapic_handle_intr+0x40/frame 0xe038ab88
    Xapic_isr1() at Xapic_isr1+0x35/frame 0xe038ab88
    --- interrupt, eip = 0xc12abbd5, esp = 0xe038abd8, ebp = 0xe038abd8 ---
    acpi_cpu_c1(0,0,c6700000,b36f5cee,2a6c,...) at acpi_cpu_c1+0x5/frame 0xe038abd8
    acpi_cpu_idle(ffffffff,ffffffff,ffffffff,e038ac48,c12b5a6a,...) at acpi_cpu_idle+0x13a/frame 0xe038ac18
    cpu_idle_acpi(ffffffff,ffffffff,c1f31e84,c1f31e88,c1f31e94,...) at cpu_idle_acpi+0x3f/frame 0xe038ac2c
    cpu_idle(0,0,c14553be,a3b,0,...) at cpu_idle+0x9a/frame 0xe038ac48
    sched_idletd(0,e038ad08,0,0,0,...) at sched_idletd+0x1dd/frame 0xe038acc4
    fork_exit(c0d36bb0,0,e038ad08) at fork_exit+0xa3/frame 0xe038acf4
    fork_trampoline() at fork_trampoline+0x8/frame 0xe038acf4
    --- trap 0, eip = 0, esp = 0xe038ad40, ebp = 0 ---
    
    
    kernel trap 12 with interrupts disabled
    
    Fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address	= 0x27cf1a9
    fault code		= supervisor write, page not present
    instruction pointer	= 0x20:0xc12dee41
    stack pointer	        = 0x28:0xe038ab58
    frame pointer	        = 0x28:0xe038ab70
    code segment		= base 0x0, limit 0xfffff, type 0x1b
    			= DPL 0, pres 1, def32 1, gran 1
    processor eflags	= resume, IOPL = 0
    current process		= 11 (idle: cpu0)
    

    All of the crashes were the same. That's a pretty odd place for it to crash, I'm inclined to point toward the BIOS or hardware (specifically, power management) but that's just a guess.



  • Hm, Ok. The hardware is a Checkpoint UTM-1 270. I believe the original manufacturer has a hardware diagnostic tool that I can try running.

    Is there any pfsense specific hardware diagnostic tool that I could run?

    I'm aware of memtest, but if it's a bios/power management issue i'm not sure how I would go about diagnosing that.


  • Rebel Alliance Developer Netgate

    No, we don't have any hardware tests of that nature currently. OS-independent testing tools like memtest86 are best.


Log in to reply