pfsense 2.8 CE Crash Report
-
Earlier this evening, when I was trying to shutdown the firewall, it kept ignoring the halt and rebooting.
Logging in and was presented with a crash report. Unit had been running fine.
-
Backtrace:
db:1:pfs> bt Tracing pid 0 tid 250000 td 0xfffff8012e371000 kdb_enter() at kdb_enter+0x33/frame 0xfffffe008e1ce880 panic() at panic+0x43/frame 0xfffffe008e1ce8e0 trap_fatal() at trap_fatal+0x40b/frame 0xfffffe008e1ce940 trap_pfault() at trap_pfault+0x46/frame 0xfffffe008e1ce990 calltrap() at calltrap+0x8/frame 0xfffffe008e1ce990 --- trap 0xc, rip = 0xffffffff8128fca4, rsp = 0xfffffe008e1cea60, rbp = 0xfffffe008e1cea60 --- strcmp() at strcmp+0x14/frame 0xfffffe008e1cea60 ifc_find_cloner() at ifc_find_cloner+0x5b/frame 0xfffffe008e1cea90 ifc_dump_ifp_nl() at ifc_dump_ifp_nl+0x19/frame 0xfffffe008e1ceac0 dump_iface() at dump_iface+0x525/frame 0xfffffe008e1ceb60 dump_cb() at dump_cb+0x1c/frame 0xfffffe008e1ceb80 if_foreach_sleep() at if_foreach_sleep+0x227/frame 0xfffffe008e1cec00 rtnl_handle_getlink() at rtnl_handle_getlink+0x24d/frame 0xfffffe008e1cecd0 rtnl_handle_message() at rtnl_handle_message+0x195/frame 0xfffffe008e1ced30 nl_taskqueue_handler() at nl_taskqueue_handler+0x44e/frame 0xfffffe008e1cee40 taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe008e1ceec0 taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe008e1ceef0 fork_exit() at fork_exit+0x7b/frame 0xfffffe008e1cef30 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe008e1cef30 --- trap 0xc, rip = 0x8337966ea, rsp = 0x835ddaca8, rbp = 0x835ddacc0 ---
Panic:
Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 02 fault virtual address = 0xffffffff83e46170 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8128fca4 stack pointer = 0x0:0xfffffe008e1cea60 frame pointer = 0x0:0xfffffe008e1cea60 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 = 0 (netlink_socket (PID) rdi: fffff800051af400 rsi: ffffffff83e46170 rdx: 0000000000000000 rcx: 0000000000000000 r8: 0000000000000000 r9: 8080808080808080 rax: 0000000000000076 rbx: fffff8012e371000 rbp: fffffe008e1cea60 r10: 0000000000000000 r11: ffffb1afa9a0b8a8 r12: 0000000000000050 r13: 0000000000000050 r14: fffff800051af400 r15: ffffffff83e46170 trap number = 12 panic: page fault cpuid = 1 time = 1754673840 KDB: enter: panic
That's not a crash that's familiar to me.
How were you trying to shut it down, from the gui?
I don't see the shutdown logged.
I do see this IP conflict but it's almost certainly unrelated:
<3>arp: 6e:cd:d6:51:d0:9b is using my IP address 10.7.205.106 on igb4! <3>arp: 6e:cd:d6:51:d0:9b is using my IP address 10.17.97.230 on igb4!
-
Yes via the halt option on the GUI menu.
-
Hmm, so is that shown in the main system log? It may just not be in the console log.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.