PF Restart every time
-
Guys, someone see this error?
Because every time PF restarts and came back with this logstextdump.tar.0 info.0 -
Backtrace:
db:0:kdb.enter.default> bt Tracing pid 11 tid 100005 td 0xfffff80004325000 kdb_enter() at kdb_enter+0x37/frame 0xfffffe003f174490 vpanic() at vpanic+0x197/frame 0xfffffe003f1744e0 panic() at panic+0x43/frame 0xfffffe003f174540 trap_fatal() at trap_fatal+0x391/frame 0xfffffe003f1745a0 trap() at trap+0x67/frame 0xfffffe003f1746b0 calltrap() at calltrap+0x8/frame 0xfffffe003f1746b0 --- trap 0x9, rip = 0xffffffff80da98f4, rsp = 0xfffffe003f174780, rbp = 0xfffffe003f1747e0 --- callout_process() at callout_process+0x184/frame 0xfffffe003f1747e0 handleevents() at handleevents+0x188/frame 0xfffffe003f174820 timercb() at timercb+0x25f/frame 0xfffffe003f174870 lapic_handle_timer() at lapic_handle_timer+0x9b/frame 0xfffffe003f1748a0 Xtimerint() at Xtimerint+0xb1/frame 0xfffffe003f1748a0 --- interrupt, rip = 0xffffffff81531986, rsp = 0xfffffe003f174970, rbp = 0xfffffe003f174970 --- acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfffffe003f174970 acpi_cpu_idle() at acpi_cpu_idle+0x2e0/frame 0xfffffe003f1749b0 cpu_idle_acpi() at cpu_idle_acpi+0x3e/frame 0xfffffe003f1749d0 cpu_idle() at cpu_idle+0x9f/frame 0xfffffe003f1749f0 sched_idletd() at sched_idletd+0x326/frame 0xfffffe003f174ab0 fork_exit() at fork_exit+0x7e/frame 0xfffffe003f174af0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe003f174af0 --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Panic:
kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 2; apic id = 04 instruction pointer = 0x20:0xffffffff80da98f4 stack pointer = 0x28:0xfffffe003f174780 frame pointer = 0x28:0xfffffe003f1747e0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 11 (idle: cpu2) trap number = 9 panic: general protection fault cpuid = 2 time = 1680623985 KDB: enter: panic
Nothing significant in the message buffer
It looks like something in the idle process so maybe some unsupported power saving function?
Has it always done this?
Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.