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

    Crash report / programming bug

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 501 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.
    • M
      MarshonAU81
      last edited by

      Hello everyone,

      I'll start off by saying I am a complete noob when it comes to networking, firewalls, cyber security and pretty much everything in between. I have been blindly stumbling my way through setting up a home network that is spread across 3 buildings, with a Wireless NBN connection which first goes into the TPG supplied Archer VR-1600 which i cant put into bridge mode because its operating on ewan and i cant replace it with something better as I need the VOIP phone component. Next is a Protectli VP2420 and behind that is my network of assorted components, 2x Unifi 8 port switches, 4x Unifi AP's, a TP Link 5 port managed switch and Netgear 8 port POE unmanaged switch. The non Unifi switch's will be replaced with Unifi soon enough.
      As far as I can tell, the crash and/or programming bug isnt causing any continued issues but I really cant be sure of that. Any help or feedback on what the report means would be greatly appreciated, many thanks in advance.

      info.0

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

        We need to see at least the backtrace from the other part of the crash report. You can upload it here: https://nc.netgate.com/nextcloud/s/KxqyEzqfpMdLRZL

        Steve

        M 1 Reply Last reply Reply Quote 0
        • M
          MarshonAU81
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • M
            MarshonAU81 @stephenw10
            last edited by

            @stephenw10 Thanks steve, i have uploaded the textdump file. Is that all you need?

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

              Yup I see it. Unfortunately the backtrace isn't particularly revealing:

              db:0:kdb.enter.default>  bt
              Tracing pid 1 tid 100002 td 0xfffffe0012117ac0
              kdb_enter() at kdb_enter+0x32/frame 0xfffffe00109b4820
              vpanic() at vpanic+0x163/frame 0xfffffe00109b4950
              panic() at panic+0x43/frame 0xfffffe00109b49b0
              vm_fault() at vm_fault+0x15c5/frame 0xfffffe00109b4ac0
              vm_fault_trap() at vm_fault_trap+0xb0/frame 0xfffffe00109b4b10
              trap_pfault() at trap_pfault+0x1d9/frame 0xfffffe00109b4b70
              calltrap() at calltrap+0x8/frame 0xfffffe00109b4b70
              --- trap 0xc, rip = 0xffffffff836cd170, rsp = 0xfffffe00109b4c48, rbp = 0xfffffe00109b4db0 ---
              _end() at 0xffffffff836cd170/frame 0xfffffe00109b4db0
              sys_reboot() at sys_reboot+0x29c/frame 0xfffffe00109b4e00
              amd64_syscall() at amd64_syscall+0x109/frame 0xfffffe00109b4f30
              fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00109b4f30
              --- syscall (55, FreeBSD ELF64, reboot), rip = 0x27291a, rsp = 0x820ec2408, rbp = 0x820ec2830 ---
              

              However it looks like it panicked when it tried to make some change after shutdown was initiated:

              <118>pfSense is now shutting down ...
              <118>
              <118>net.inet.carp.allow: 0 -> 0
              <6>pflog0: promiscuous mode disabled
              Trying to mount root from ufs:/dev/ufsid/65b7583531b4716a [rw,noatime]...
              panic: vm_fault_lookup: fault on nofault entry, addr: 0xffffffff836cd000
              cpuid = 2
              time = 1706519642
              KDB: enter: panic
              

              Unclear why it did that but it you clear the crash report and reboot and it doesn't do that every time it's likely a quirk of having just run the initial setup.

              You are still running 2.7.1. You should upgrade to 2.7.2 when you can.

              Steve

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