Bug #10215
closed
Crash on 2.4.5-RC (Jan 28 12:12:41 EST 2020)
0%
Description
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x20
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80f8c706
stack pointer = 0x28:0xfffffe0462ed0ac0
frame pointer = 0x28:0xfffffe0462ed0ac0
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 = 51545 (unbound-anchor)
trap number = 12
panic: page fault
cpuid = 3
Files
Updated by Jim Pingle almost 5 years ago
- Category set to Operating System
- Status changed from New to Rejected
Not enough information here to do anything with it. The backtrace doesn't suggest anything in particular. You'll need to start a thread on https://forum.pfsense.org and include a lot more detail about your setup so that it can be discussed and diagnosed.
db:0:kdb.enter.default> bt Tracing pid 51545 tid 100505 td 0xfffff80014272620 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe0462ed0770 vpanic() at vpanic+0x19b/frame 0xfffffe0462ed07d0 panic() at panic+0x43/frame 0xfffffe0462ed0830 trap_pfault() at trap_pfault/frame 0xfffffe0462ed0880 trap_pfault() at trap_pfault+0x49/frame 0xfffffe0462ed08e0 trap() at trap+0x29d/frame 0xfffffe0462ed09f0 calltrap() at calltrap+0x8/frame 0xfffffe0462ed09f0 --- trap 0xc, rip = 0xffffffff80f8c706, rsp = 0xfffffe0462ed0ac0, rbp = 0xfffffe0462ed0ac0 --- pfi_kif_match() at pfi_kif_match+0x26/frame 0xfffffe0462ed0ac0 pf_match_translation() at pf_match_translation+0x3d1/frame 0xfffffe0462ed0b50 pf_get_translation() at pf_get_translation+0xf3/frame 0xfffffe0462ed0c30 pf_test_rule() at pf_test_rule+0x21c/frame 0xfffffe0462ed1100 pf_test6() at pf_test6+0x1bf5/frame 0xfffffe0462ed1350 pf_check6_out() at pf_check6_out+0x1d/frame 0xfffffe0462ed1370 pfil_run_hooks() at pfil_run_hooks+0x90/frame 0xfffffe0462ed1400 ip6_output() at ip6_output+0x15c8/frame 0xfffffe0462ed1630 udp6_send() at udp6_send+0x71b/frame 0xfffffe0462ed17d0 sosend_dgram() at sosend_dgram+0x345/frame 0xfffffe0462ed1830 kern_sendit() at kern_sendit+0x1f9/frame 0xfffffe0462ed18e0 sendit() at sendit+0x19e/frame 0xfffffe0462ed1930 sys_sendto() at sys_sendto+0x4d/frame 0xfffffe0462ed1980 amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe0462ed1ab0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0462ed1ab0
The closest thing I saw to an error was a problem on a realtek NIC in the message buffer:
re0: watchdog timeout <5>re0: link state changed to DOWN <5>re0: link state changed to UP <5>re0: link state changed to DOWN <5>re0: link state changed to UP
So it's possible it's a hardware issue (which isn't actionable) or a driver issue (upstream problem, not for us) -- either way, post on the forum for help.
Updated by 