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

    Crash Report

    General pfSense Questions
    4
    8
    786
    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
      moto
      last edited by

      Hi my pfsense have been crashing randomly every 3 to 6 days lately. This is the first time I got an crash report from the GUI. Here the report if someone can help me out much thank.

      https://ghostbin.com/paste/x6RTM

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @moto
        last edited by

        @moto

        I'd suspect hardware. One thing you can do is run memtest for a while, to see if any errors turn up.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        M 1 Reply Last reply Reply Quote 1
        • M
          moto @JKnott
          last edited by

          @jknott said in Crash Report:

          @moto

          I'd suspect hardware. One thing you can do is run memtest for a while, to see if any errors turn up.

          I ran memtest last night so far the test come out ok. Is there any other thing I can do to troubleshoot it.

          4cc02561-ac02-42b5-94ec-0a02e9b24132-image.png

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @moto
            last edited by

            @moto

            Did you run memtest for a full pass? When I run it, I generally let it do at least 1 full pass. Sometimes I'll just let it run overnight.

            Your error report mentions a page fault. That would tend to indicate a CPU or memory problem. Either way, I suspect you're looking at new hardware.

            The system I was running pfsense on died recently. It also ran memtest properly, but pfsense wouldn't start up. I was getting error messages about a USB mouse or the NICs. I even tried installing Linux on it, as it previously ran a Linux based firewall. I couldn't even install it now. With the cost of hardware these days, you're often better tossing the failed hardware, unless you have the appropriate experience and test equipment to diagnose the problem. Then you would need the skills to replace the failed components, assuming you could even find them.

            BTW, many years ago, I used to be a computer technician, working on the old "mini computers". Back in those days, I would get right down to the chip and microcode (the software within the CPU) level. The first time I ran a memory test utility, on a Data General Nova, it was one I wrote myself. These days, there's no way you could afford to pay a tech to do the sort of things I used to do, as hardware is so cheap. Back then, the cost of a system would often cover my pay for a few years, so it was worth while to fix it.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            M 1 Reply Last reply Reply Quote 0
            • M
              moto @JKnott
              last edited by

              @jknott

              I ran 4 full test took about 14hrs. It all brand new equipment less then 6 month old (Protectli Vault – 4 Port). Actually when it first started to do random crash the age of the system was only 3 month old.

              Would it be issue relate to the hard drive?

              JKnottJ noplanN 2 Replies Last reply Reply Quote 0
              • JKnottJ
                JKnott @moto
                last edited by

                @moto

                Hard to say. I'm not familiar with that model. It's probably not software, but just to be sure, you could reinstall. Back up your config first.

                FWIW, I ran pfsense on my old firewall hardware for almost 5 years, until the computer died. I also ran a Linux firewall on it for a few years before that. It was always rock solid until now.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • noplanN
                  noplan @moto
                  last edited by

                  @moto

                  Filesystem? R u usin?
                  If not zfs maybe a hint.

                  But hmmm it's just a wild guess

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

                    Relevant crash report parts.

                    Backtrace:

                    db:0:kdb.enter.default>  bt
                    Tracing pid 11 tid 100003 td 0xfffff8000721c000
                    kdb_enter() at kdb_enter+0x3b/frame 0xfffffe0228ae2520
                    vpanic() at vpanic+0x19b/frame 0xfffffe0228ae2580
                    panic() at panic+0x43/frame 0xfffffe0228ae25e0
                    trap_pfault() at trap_pfault/frame 0xfffffe0228ae2630
                    trap_pfault() at trap_pfault+0x49/frame 0xfffffe0228ae2690
                    trap() at trap+0x29d/frame 0xfffffe0228ae27a0
                    calltrap() at calltrap+0x8/frame 0xfffffe0228ae27a0
                    --- trap 0xc, rip = 0xffffffff80cd5353, rsp = 0xfffffe0228ae2870, rbp = 0xfffffe0228ae2870 ---
                    runq_add() at runq_add+0x43/frame 0xfffffe0228ae2870
                    sched_add() at sched_add+0x150/frame 0xfffffe0228ae28b0
                    intr_event_schedule_thread() at intr_event_schedule_thread+0xa0/frame 0xfffffe0228ae28e0
                    intr_event_handle() at intr_event_handle+0xce/frame 0xfffffe0228ae2930
                    intr_execute_handlers() at intr_execute_handlers+0x48/frame 0xfffffe0228ae2960
                    lapic_handle_intr() at lapic_handle_intr+0x3e/frame 0xfffffe0228ae2980
                    Xapic_isr1() at Xapic_isr1+0xd3/frame 0xfffffe0228ae2980
                    --- interrupt, rip = 0xffffffff803f18c2, rsp = 0xfffffe0228ae2a50, rbp = 0xfffffe0228ae2a90 ---
                    acpi_cpu_idle() at acpi_cpu_idle+0x342/frame 0xfffffe0228ae2a90
                    cpu_idle_acpi() at cpu_idle_acpi+0x3f/frame 0xfffffe0228ae2ab0
                    cpu_idle() at cpu_idle+0x94/frame 0xfffffe0228ae2ad0
                    sched_idletd() at sched_idletd+0x476/frame 0xfffffe0228ae2bb0
                    fork_exit() at fork_exit+0x83/frame 0xfffffe0228ae2bf0
                    fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0228ae2bf0
                    --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
                    

                    Panic:

                    Fatal trap 12: page fault while in kernel mode
                    cpuid = 0; apic id = 00
                    fault virtual address	= 0xffffff378335cdc8
                    fault code		= supervisor write data, page not present
                    instruction pointer	= 0x20:0xffffffff80cd5353
                    stack pointer	        = 0x28:0xfffffe0228ae2870
                    frame pointer	        = 0x28:0xfffffe0228ae2870
                    code segment		= base 0x0, limit 0xfffff, type 0x1b
                    			= DPL 0, pres 1, long 1, def32 0, gran 1
                    processor eflags	= resume, IOPL = 0
                    current process		= 11 (idle: cpu0)
                    trap number		= 12
                    panic: page fault
                    cpuid = 0
                    KDB: enter: panic
                    

                    Do all the crash reports you see look like that?

                    If you had a hardware issue like RAM I would expect random crashes.

                    Steve

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