Fatal trap 12: page fault on pfSense 2.7.2
-
Hi Guys,
I really can't remember a crashreport until now in ver. 2.7.2. I've got the full CR. too. Page Fault.... could it be upcoming RAM Problem/s (hardware)????
Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xf8 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80a93d32 stack pointer = 0x28:0xfffffe008e525cb0 frame pointer = 0x28:0xfffffe008e525cf0 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 = 16 (usbus0) rdi: fffff80009294000 rsi: fffff80005825741 rdx: fffffe008e525d88 rcx: fffff80005825740 r8: 0000000000000000 r9: 0000000000000000 rax: 0000000000000000 rbx: fffff80009294000 rbp: fffffe008e525cf0 r10: 0000000000000000 r11: 0000000000000003 r12: fffff80009279148 r13: fffff800092940e0 r14: fffff800092942e8 r15: 0000000000000013 trap number = 12 panic: page fault cpuid = 0 time = 1776986971 KDB: enter: panicThanks in advance,
Leroyx -
Read Crash Report - Fatal trap 12: page fault while in kernel mode (lsof) first to get a general idea of the issue.
From what you've shown, I see a page fault (that's Intel's trap 12).
In the kernel space (the upper 0xfffffff..... part of memory).
The 'name' of the part of the kernel where it happened is 'usbus0' (driver) so the issue arrived when dealing with USB traffic (?).The post I mentioned above shows more details, like the called function stack.
That said, "trap 12" can't be finger pointed easily.General observations are ;
Maybe you are using to modern hardware with software that is to old ?
Or the other way around ?
I mean 2.7.2 was good, but pretty ancient by now. -
Hi Gertjan,
The HW is a Vault FW2B, nowadays it's pretty old too :-[
But it works prefectly. I dont use the USB Ports.Leroyx
-
This post is deleted! -
What does the backtrace in the crash report show?
Privacy Policy · Cookie Policy