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

    [v2.3 & v2.4] Kernel crash with Fatal trap 12: page fault while in kernel mode

    Scheduled Pinned Locked Moved General pfSense Questions
    35 Posts 10 Posters 32.9k 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.
    • C
      CDuv
      last edited by

      Yeah! I am not alone!

      Is your network architecture partially similar to mine? Do you have a lot of users?

      If your workaround is to downgrade to 2.2 it is a lead for some debugging and a possible fix…

      I see bug #4689 (Panic/Crash "sbflush_internal: cc 4294967166 || mb 0 || mbcnt 0") is similar but is marked as resolved for 2.3…
      Original bug report on FreeBSD bug tracker is still open and someone reported it ran into the issue it a month ago.

      1 Reply Last reply Reply Quote 0
      • w0wW
        w0w
        last edited by

        I don't see any options you must change in BIOS. All your posted options are OK. Just for testing purpose, enable PowerD and set it to maximum perfomance. Make sure you do not have polling enabled and enable all setting below (see picture).
        If it does not help then install 2.2.x version.

        offload.jpg
        offload.jpg_thumb

        1 Reply Last reply Reply Quote 0
        • C
          CDuv
          last edited by

          I had "Hardware Checksum Offloading" unchecked and both "Hardware TCP Segmentation Offloading" & "Hardware Large Receive Offloading" checked.

          I'll check "Hardware Checksum Offloading" and set PowerD to maximum…

          1 Reply Last reply Reply Quote 0
          • C
            CDuv
            last edited by

            Update:
            I tested OPNsense (v16.7.8 ) under the same load and configuration and it works (3 days now)…
            In the same time, the other server (on pfSense 2.4.0) which is up but not used (no traffic towards him) did not crashed either: indicates crashes are load/traffic related.

            Hope this helps to pinpoint the exact cause of the issue.

            1 Reply Last reply Reply Quote 0
            • w0wW
              w0w
              last edited by

              I think you must create bug report on redmine. The crashes I have had on different hardware also happened under heavy traffic. It could be driver related or NIC hardware revision/firmware.

              1 Reply Last reply Reply Quote 0
              • w0wW
                w0w
                last edited by

                Any news?

                1 Reply Last reply Reply Quote 0
                • H
                  Harvy66
                  last edited by

                  My car won't start, I heard your's doesn't, I bet it's the same reason.

                  I'd recommend starting your own threads so people can step you through stuff to check without causing massive confusion about who is talking about what.

                  1 Reply Last reply Reply Quote 0
                  • P
                    parsalog
                    last edited by

                    I am fighting this same issue, any updates on this issue.  I am running a super micro server as well. it seems a lot of people are seeing the trap 12 when using the intel igb driver specifically?

                    1 Reply Last reply Reply Quote 0
                    • D
                      dcugy
                      last edited by

                      I have the same problem with 2.5.2.

                      problem appears when i migrate frome 2.4 to 2.5

                      intel(R) Celeron(R) CPU 3865U @ 1.80GHz
                      Current: 1700 MHz, Max: 1801 MHz
                      2 CPUs: 1 package(s) x 2 core(s)
                      AES-NI CPU Crypto: Yes (inactive)
                      QAT Crypto: No

                      pfsense release
                      2.5.2-RELEASE (amd64)

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

                        This is almost certainly not the same issue. Many, many things have changed since 2016! 😉

                        Please open a new thread with the actual crash report you're seeing.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S stephenw10 locked this topic on
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.