[v2.3 & v2.4] Kernel crash with Fatal trap 12: page fault while in kernel mode
-
bad cable? faulty plug on the other end with out of spec voltages?
-
@w0w:
Are there some BIOS/UEFI options regarding OS installation compatibility?
Did you try to install 2.4 on ZFS with GPT-UEFI (it should work on latest builds)? I am not sure may be its related to some power savings or anything else you can find in BIOS or UEFI settings related to power savings.
It would be good to disable all CPU power saving modes except common C1 mode for testing purposes.pfSense 2.4 was installed on MBR: I'll try GPT…
I have no access to BIOS on this appliance which is pre-prepared for pfSense (bought to a local appliance reseller): serial console does not allow me to enter BIOS (I see the "Press: Got it working.to enter…" but pressing the [Del] key does nothing).
The BIOS says the following about CPU:- EIST (GV3) : Disable
- P-stat Coordination : Package (cannot be modified)
- TM1 : Enable
- TM2 Mode : Adaptative Throttling (cannot be modified)
- CPU C State : Disable
- Enhanced Halt State : Disable (cannot be modified)
- ACP C2 : Diable (cannot be modified)
- Monitor/Mwait : Enable (cannot be modified)
- L1 Prefetcher : Enable
- L2 Prefetcher : Enable
- Max CPUID Value Limit : Disable
- Execute Disable Bit : Enable
- AES-NI : Enable
- Turbo : Enable (cannot be modified)
- Active Processor Core : All
But, on the pfSense config, PowerD is disabled and AC Power, Battery Power and Unknown Power settings are all set to "Hiadaptive" (did not touched theses after 2.4.0-BETA installation).
It is advised to disable power saving modes in the BIOS/UEFI?
-
Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 06 fault virtual address = 0x5e00000000 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80d80b00 stack pointer = 0x28:0xfffffe00a1644b60 frame pointer = 0x28:0xfffffe00a1644b80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 75463 (pfctl)
Got the same error once a day with the same motherboard in 2.3.x. Bios settings weren't changed since the first install of 2.x. I don't think it is a hardware issue but I also have no clue how to solve the issue but installing 2.2 again.
-
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. -
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.
-
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…
-
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.
-
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.
-
Any news?
-
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.
-
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?
-
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: Nopfsense release
2.5.2-RELEASE (amd64) -
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
-
S stephenw10 locked this topic on