Fatal trap 12: page fault while in kernel mode. PfSense 2.1-release



  • Got the latest version running but get fatal trap 12: page fault while in kernel mode error that kills the embedded system.

    I see a lot about this error in FreeBSD forums. So this may just be inheritet to PfSense.

    Symtoms:
    Box stops working. I was called in and hooked up a serial cable. Black screen in telnet session so I hit enter. Right after that it came with a "Rebooting…." message and did a total reboot whereafter it worked as normal.

    This is a new box I just took into production. An embedded system from one of the recommended vendors. I have two similar boxes. I can test with the other but of cause don't want to if it is a known issue.

    
    Version 	2.1-RELEASE (i386)
    built on Wed Sep 11 18:16:44 EDT 2013
    FreeBSD 8.3-RELEASE-p11
    
    You are on the latest version.
    Platform 	nanobsd (4g)
    NanoBSD Boot Slice 	pfsense0 / ad0s1 (ro)
    CPU Type 	Intel(R) Atom(TM) CPU Z530 @ 1.60GHz
    

    Here is dump from telnet session. The box was not routing traffic and not assigning any IP on LAN. After hitting enter it rebooted and came up OK.

    Here is the last lines from log after the reboot. It contains the "trap 12" message listed in reverse order (newest on top):

    Oct 29 13:50:19 kernel: CPU: Intel(R) Atom(TM) CPU Z530 @ 1.60GHz (1596.00-MHz 686-class CPU)
    Oct 29 13:50:19 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
    Oct 29 13:50:19 kernel: root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
    Oct 29 13:50:19 kernel: FreeBSD 8.3-RELEASE-p11 #0: Wed Sep 11 19:13:36 EDT 2013
    Oct 29 13:50:19 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
    Oct 29 13:50:19 kernel: The Regents of the University of California. All rights reserved.
    Oct 29 13:50:19 kernel: Copyright © 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    Oct 29 13:50:19 kernel: Copyright (c) 1992-2012 The FreeBSD Project.
    Oct 29 13:50:19 kernel: Rebooting...
    Oct 29 13:50:19 kernel: --> or switch off the system now.
    Oct 29 13:50:19 kernel: --> Press a key on the console to reboot,
    Oct 29 13:50:19 kernel: Automatic reboot in 15 seconds - press a key on the console to abort
    Oct 29 13:50:19 kernel: Cannot dump. Device not defined or unavailable.
    Oct 29 13:50:19 kernel: Uptime: 2h10m13s
    Oct 29 13:50:19 kernel: cpuid = 0
    Oct 29 13:50:19 kernel: panic: stack overflow detected; backtrace may be corrupted
    Oct 29 13:50:19 kernel: Fatal trap 12: page fault while in kernel mode
    Oct 29 13:50:19 kernel:
    Oct 29 13:50:19 kernel:
    Oct 29 13:50:19 syslogd: kernel boot file is /boot/kernel/kernel



  • Apparently it is a broad error message. FreeBSD ask to have "trap 12" messages send to them for bugfixing. It seems the error message is just "there is something wrong" but not about what.

    Here are several threads where issue has been fixed changing hardware og build.

    RAM issue:
    http://forums.freenas.org/threads/fatal-trap-12-page-fault-while-in-kernel-mode-cifs-transfer.12598/

    BIOS issue:
    http://forums.freenas.org/threads/fatal-trap-12-page-fault-while-in-kernel-mode.10268/

    NIC issue:
    http://forum.pfsense.org/index.php?topic=40649.0

    PfSense Build related (ftp patch):
    http://forum.pfsense.org/index.php/topic,64144.0.html



  • Found this post that may be a symptom treatment:
    http://forum.pfsense.org/index.php/topic,40769.msg226908.html#msg226908

    If just the box will crash properly and reboot automatically then it will not be so difficult to have the box in production. I will try that fix and see if the box at least can restart by it self.



  • Our pfSense box (HP DL120 G7) has been running great for more than a year. We upgraded from 2.0 to 2.1 a few days after it came out.

    Today it kernel panicked out of the blue. Looks like it was during a receive interrupt from onboard Intel network card. Has anyone seen this issue before. I just wonder if this is an issue in 2.1 cause we had an uptime of more than a year on a 2.0.X build.

    See the attached image for the actual panic.

    ![pfsense panic cropped.png](/public/imported_attachments/1/pfsense panic cropped.png)
    ![pfsense panic cropped.png_thumb](/public/imported_attachments/1/pfsense panic cropped.png_thumb)



  • i have just started experiencing this problem. though it seems to be occuring with add-on intel cards

    see also http://forum.pfsense.org/index.php/topic,70832.0.html


Log in to reply