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

    Fatal trap 12: page fault while in kernel mode when connecting PPPoE

    Scheduled Pinned Locked Moved Plus 23.09 Development Snapshots (Retired)
    27 Posts 4 Posters 3.8k 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.
    • w0wW
      w0w @cmcdonald
      last edited by

      @cmcdonald
      Yes, looks like the problem is limited to “Synchronize states” option.

      K cmcdonaldC 2 Replies Last reply Reply Quote 0
      • K
        kprovost @w0w
        last edited by

        @w0w I've had a look at that dump, and while I think I've identified what's going wrong I do not understand how we can end up in that situation.

        It'd be interesting to get a full core dump (as opposed to these text dumps). Are you up for reproducing the problem and sharing a core dump (along with the exact version you triggered the crash on, of course)?

        Short version: add a device for a swap partition, ideally at least as large as system RAM. A USB stick should work. (Note you'll lose all data on the stick!)
        If the USB (or other) swap device is da0 do:

        gpart destroy -F da0
        gpart create -s gpt da0
        gpart add -t freebsd-swap da0
        

        Add /dev/da0p1 none swap sw 0 0 to /etc/fstab.
        Edit /etc/pfSense-ddb.conf and change the script kdb.enter.default to script kdb.enter.default=bt ; show registers ; dump ; reset.

        Reboot.

        Future panics should dump a kernel core to the swap partition, which will get saved to /var/crash on the next boot. Those files (along with an exact version number of the system this happened on) should let us dig a bit deeper.

        1 Reply Last reply Reply Quote 1
        • cmcdonaldC
          cmcdonald Netgate Developer @w0w
          last edited by

          @w0w What if you restrict pfsync updates from primary to secondary only, a vice-versa...instead of bi-directional syncing?

          Need help fast? https://www.netgate.com/support

          w0wW 1 Reply Last reply Reply Quote 1
          • w0wW
            w0w @cmcdonald
            last edited by

            @cmcdonald That's what I did last time 😊
            It looks like it stopped to crash, but maybe it needs further testing, not sure.
            @kprovost
            I posted some links with core dumps created privately 🙄

            cmcdonaldC 1 Reply Last reply Reply Quote 0
            • cmcdonaldC
              cmcdonald Netgate Developer @w0w
              last edited by

              @w0w disabling which sync path (primary to secondary or secondary to primary) ?

              Need help fast? https://www.netgate.com/support

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

                @cmcdonald
                Secondary to primary.

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

                  https://redmine.pfsense.org/issues/14804

                  Just for reference, problem solved.

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