Fatal trap 12: page fault while in kernel mode



  • Hey folks - I've been using pfsense for a few months, running on this QOTOM box. It acts as my home NAT gateway and OpenVPN machine. Fairly standard setup using 11.1-RELEASE-p4..

    The other day the whole system went down - I had to manually reboot the box, and "Fatal trap 12: page fault while in kernel mode" was the message in the crash log. I wasn't doing anything fancy at the time… just normal internet activities over NAT.

    Yikes! I'm super glad this happened while I was at home, and not on the road with no physical access to the box.

    Here's my questions:

    • Is there a way for the machine to have auto-rebooted itself instead of just hanging? That would be much preferred!

    • Has anyone else run into a crash like this? Is it a known issue? I've attached a crash log.

    Thanks!
    pfsense_crash.txt



  • Take a look on your dashboard, and check the "MBUF" usage.  Your crash was in the Intel igb network card driver.  If the MBUF usage is high relative to the number available during the network activity that caused the crash, that might be your culprit.  The settings for igb cards might help.

    https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards


  • Netgate

    Hmm, it already allocated the mbuf by that point

    rn_match() at rn_match+0x1ad/frame 0xfffffe022991d650
    fib4_lookup_nh_basic() at fib4_lookup_nh_basic+0x84/frame 0xfffffe022991d6b0
    ip_findroute() at ip_findroute+0x31/frame 0xfffffe022991d6e0
    ip_tryforward() at ip_tryforward+0x1f7/frame 0xfffffe022991d750
    ip_input() at ip_input+0x3c5/frame 0xfffffe022991d7b0
    netisr_dispatch_src() at netisr_dispatch_src+0xa0/frame 0xfffffe022991d80
    ….

    https://github.com/freebsd/freebsd/blob/master/sys/net/radix.c#L279



  • I've come across this on my box as well (same hardware).
    It has happened about seven times in 2 months now, I've submitted the crash-reports, the times I've been able to, a couple of times it has just rebooted without any report, it just says a crash has happened when I login after the reboot.


Log in to reply