Pfsense restarting by itself - Fatal trap 12: page fault while in kernel mode

[juniorsaulo]

Hi,

I'm using Pfsense 2.4.3-RELEASE, it's virtualized in VMware 6.0.0 on top of an HP ProLiant DL360 Gen9 server. Pfsense already had a 64-day uptime, but yesterday during the workday it restarted itself. By analyzing the logs, I found the following information:

ul 18 10:06:56 syslogd kernel boot file is /boot/kernel/kernel
Jul 18 10:06:56 kernel Fatal trap 12: page fault while in kernel mode
Jul 18 10:06:56 kernel cpuid = 2; apic id = 04
Jul 18 10:06:56 kernel fault virtual address = 0xc
Jul 18 10:06:56 kernel fault code = supervisor read data, page not present
Jul 18 10:06:56 kernel instruction pointer = 0x20:0xffffffff80d8ed40
Jul 18 10:06:56 kernel stack pointer = 0x28:0xfffffe000026d560
Jul 18 10:06:56 kernel frame pointer = 0x28:0xfffffe000026d560
Jul 18 10:06:56 kernel code segment = base 0x0, limit 0xfffff, type 0x1b
Jul 18 10:06:56 kernel = DPL 0, pres 1, long 1, def32 0, gran 1
Jul 18 10:06:56 kernel processor eflags = interrupt enabled, resume, IOPL = 0
Jul 18 10:06:56 kernel current process = 0 (em0 taskq)

Someone has already gone through this or could give me a way of how to better investigate what has happened, I am worried that this will happen again and again.

Thank you!

[jimp]

vmware workstation or ESX?

If it's ESX, you probably need to upgrade ESX to 6.7 (or at least 6.5) and make sure the hardware compatibility is upgraded to whatever is proper for that version.

pfSense 2.4.x uses FreeBSD 11, which is not technically supported properly until ESX 6.5.

It may work for some, but there are no guarantees there. Just because it boots doesn't mean it will be stable, anything could trigger an issue between the OS and hypervisor.

Changing to vmxnet interfaces would be the next thing to try, and wouldn't require much in the way of changes on the hypervisor, certainly less impact than an upgrade, but still likely to have problems.

[juniorsaulo]

@jimp said in Pfsense restarting by itself - Fatal trap 12: page fault while in kernel mode:

ESX

Thanks for the information, I'll analyze this