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

    crash report after each reboot

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 436 Views
    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.
    • R
      rakhsh
      last edited by

      Hi Everyone,
      I have pfsense on this machine for more than 3 years. after upgrading to 2.5.0 encountered a crash report on the dashboard after each reboot. Today I have rebooted the machine and it prints infinite dashes on plugged screen. Downloaded the 2.5.2 and installed it but the problem persist. Could someone help me interpret this one. Appreciate so much to those who will reply and suggest what will I gonna do with it.

      crash report: https://pastebin.com/xTQwChhc

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

        Relevant crash data:

        db:0:kdb.enter.default>  bt
        Tracing pid 12 tid 100109 td 0xfffff8000631c740
        kdb_enter() at kdb_enter+0x37/frame 0xfffffe004aa9f830
        vpanic() at vpanic+0x197/frame 0xfffffe004aa9f880
        panic() at panic+0x43/frame 0xfffffe004aa9f8e0
        trap_fatal() at trap_fatal+0x391/frame 0xfffffe004aa9f940
        trap_pfault() at trap_pfault+0x4f/frame 0xfffffe004aa9f990
        trap() at trap+0x286/frame 0xfffffe004aa9faa0
        calltrap() at calltrap+0x8/frame 0xfffffe004aa9faa0
        --- trap 0xc, rip = 0xffffffff810a6786, rsp = 0xfffffe004aa9fb70, rbp = 0xfffffe004aa9fb90 ---
        pfsync_state_export() at pfsync_state_export+0x26/frame 0xfffffe004aa9fb90
        pfsync_sendout() at pfsync_sendout+0x280/frame 0xfffffe004aa9fc40
        pfsyncintr() at pfsyncintr+0xd1/frame 0xfffffe004aa9fc90
        ithread_loop() at ithread_loop+0x23c/frame 0xfffffe004aa9fcf0
        fork_exit() at fork_exit+0x7e/frame 0xfffffe004aa9fd30
        fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe004aa9fd30
        --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
        
        Fatal trap 12: page fault while in kernel mode
        cpuid = 3; apic id = 06
        fault virtual address	= 0x0
        fault code		= supervisor read data, page not present
        instruction pointer	= 0x20:0xffffffff810a6786
        stack pointer	        = 0x28:0xfffffe004aa9fb70
        frame pointer	        = 0x28:0xfffffe004aa9fb90
        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 (swi1: pfsync)
        trap number		= 12
        panic: page fault
        cpuid = 3
        time = 1627922357
        KDB: enter: panic
        panic.txt0600001214102017665  7133 ustarrootwheelpage faultversion.txt0600006714102017665  7540 ustarrootwheelFreeBSD 12.2-STABLE fd0f54f44b5c(RELENG_2_5_0) pfSense
        

        A crash in pfSync like that is odd. Is this actually in an HA pair?

        Can you get a screenshot of how it fails when you try to install clean?

        Can you try a 2.6 snapshot?

        Steve

        R 1 Reply Last reply Reply Quote 0
        • R
          rakhsh @stephenw10
          last edited by

          @stephenw10
          Thank you for your answer.
          It is a single pfsense box. not part of HA.
          No error during installation. The problem begins after rebooting the box.
          I am downloading snapshot of 2.6 and will share the results.

          R 1 Reply Last reply Reply Quote 0
          • R
            rakhsh @rakhsh
            last edited by

            Here is the screen output:
            https://youtu.be/qDfHEfohsVQ

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

              That just looks like the same crash. It happens at 'configuring firewall'. Do you have any odd rules that might apply to the pfsync intercace? Floating rules for example?

              Does the 'infinite dashes' appear differently to this?

              Steve

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