Crash report
-
Crash report uploaded here for discussion
Seems to be a "Panic String: page fault" error. I can't make sense of it, so uploading it for the gurus to decide if this need to go to redmine as per the help pages.
Device is an SG6100
Please let me know if anything else is required.
-
Backtrace:
db:1:pfs> bt Tracing pid 2 tid 100041 td 0xfffffe0085272560 kdb_enter() at kdb_enter+0x32/frame 0xfffffe00850c5840 vpanic() at vpanic+0x163/frame 0xfffffe00850c5970 panic() at panic+0x43/frame 0xfffffe00850c59d0 trap_fatal() at trap_fatal+0x40c/frame 0xfffffe00850c5a30 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00850c5a90 calltrap() at calltrap+0x8/frame 0xfffffe00850c5a90 --- trap 0xc, rip = 0xffffffff80f4e5d6, rsp = 0xfffffe00850c5b60, rbp = 0xfffffe00850c5b90 --- in6_selecthlim() at in6_selecthlim+0x96/frame 0xfffffe00850c5b90 tcp_default_output() at tcp_default_output+0x1d97/frame 0xfffffe00850c5d70 tcp_timer_rexmt() at tcp_timer_rexmt+0x52f/frame 0xfffffe00850c5dd0 tcp_timer_enter() at tcp_timer_enter+0x101/frame 0xfffffe00850c5e10 softclock_call_cc() at softclock_call_cc+0x134/frame 0xfffffe00850c5ec0 softclock_thread() at softclock_thread+0xe9/frame 0xfffffe00850c5ef0 fork_exit() at fork_exit+0x7f/frame 0xfffffe00850c5f30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00850c5f30 --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Panic:
<6>tailscale0: link state changed to DOWN <6>tun_wg0: link state changed to DOWN <6>pflog0: promiscuous mode disabled <6>ovpns1: link state changed to DOWN Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 04 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80f4e5d6 stack pointer = 0x28:0xfffffe00850c5b60 frame pointer = 0x28:0xfffffe00850c5b90 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 = 2 (clock (0)) rdi: fffff801956ed000 rsi: 000000000000001c rdx: fffff8014cc0d078 rcx: fffff8014cc0d078 r8: 00000000ffffffbd r9: 0000000000000018 rax: 0000000000000000 rbx: 0000000000000000 rbp: fffffe00850c5b90 r10: fffff8002cf964a0 r11: fffffe00bf4d1000 r12: 0000000000010180 r13: fffff801eb26ec98 r14: fffffe00850c5b68 r15: 0000000000000000 trap number = 12 panic: page fault cpuid = 0 time = 1704501624 KDB: enter: panic
Looks like it's this: https://redmine.pfsense.org/issues/14431
Do you have IPv6 enabled on any of those interfaces that went down? -
@stephenw10 Yes, I have IPv6 enabled on all interfaces.
It generated a new bug report after I disconnected the WAN ethernet cable.
-
Mmm, that looks like the same crash type.
WAN is ix3 there? -
Yes, WAN is on ix3
-
A workaround for this just went into 24.03 snapshots and should be in the next build if you're able to try it.
-
@stephenw10 Thanks, I will look forward to when it's released.