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

    Get a Crash report after upgrade my pfSense plus to 24.03-RELEASE (amd64) built on Wed Apr 24 16:38:00 -01 2024 FreeBSD 15.0-CURRENT

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 2 Posters 629 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.
    • E
      energyvortex
      last edited by

      Hi guys, hope i'm not wrong here.

      since upgrading i got a Netgate pfSense Plus has detected a crash report or programming bug MSG.

      reinstall again?? i can't belive.

      panic.txt:
      vm_fault_lookup: fault on nofault entry, addr: 0xffffffff836f6000

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

        Do you have the complete crash report?

        The panic string doesn't really tell us much.

        Steve

        1 Reply Last reply Reply Quote 0
        • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
        • E
          energyvortex
          last edited by

          Hi, here my dump files. hope this helps. Thank you!

          textdump.tar.0 info.0

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

            Backtrace:

            db:1:pfs> bt
            Tracing pid 1 tid 100002 td 0xfffff8000556a000
            kdb_enter() at kdb_enter+0x33/frame 0xfffffe0007f89940
            panic() at panic+0x43/frame 0xfffffe0007f899a0
            vm_fault() at vm_fault+0x15cc/frame 0xfffffe0007f89ac0
            vm_fault_trap() at vm_fault_trap+0xb0/frame 0xfffffe0007f89b10
            trap_pfault() at trap_pfault+0x1d6/frame 0xfffffe0007f89b70
            calltrap() at calltrap+0x8/frame 0xfffffe0007f89b70
            --- trap 0xc, rip = 0xffffffff836f6d10, rsp = 0xfffffe0007f89c48, rbp = 0xfffffe0007f89db0 ---
            kmem_size_val() at 0xffffffff836f6d10/frame 0xfffffe0007f89db0
            sys_reboot() at sys_reboot+0x29c/frame 0xfffffe0007f89e00
            amd64_syscall() at amd64_syscall+0x109/frame 0xfffffe0007f89f30
            fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe0007f89f30
            --- syscall (55, FreeBSD ELF64, reboot), rip = 0x272aea, rsp = 0x82064dbf8, rbp = 0x82064e020 ---
            

            Panic:

            <6>pflog0: promiscuous mode disabled
            Trying to mount root from ufs:/dev/ufsid/63d8688e46a209e3 [rw,noatime]...
            <6>igb0: link state changed to DOWN
            panic: vm_fault_lookup: fault on nofault entry, addr: 0xffffffff836f6000
            cpuid = 3
            time = 1714090557
            KDB: enter: panic
            

            Hmm, that seems familiar. It looks like the error was caused by trying to access the filesystem after shutdown was called. If that is the case I wouldn't expect an actual issue, it didn't crash during normal runtime?

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

              Ah, yes this: https://redmine.pfsense.org/issues/14685

              So probably a filesystem issue. Start by running an FSCK:
              https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check

              1 Reply Last reply Reply Quote 0
              • E
                energyvortex @stephenw10
                last edited by energyvortex

                @stephenw10 thank you, i was guessing the same. but not sure, can this happend because of my HW after a uprgrade and reboot? still got this error MSG but the firewall is running good! BTW, filesystem seems to be okay.

                E 1 Reply Last reply Reply Quote 0
                • E
                  energyvortex @energyvortex
                  last edited by energyvortex

                  @energyvortex after a reboot ( reroot) the error MSG is gone now, crazy! thank you!

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