How to handle Crash-Report
-
I got this morning after ISP-reconnect (chron-job) my first crash report.
pfsense-VM crashed and rebooted
I saved crash report on HDD. Too whom is shall send it? -
You can post the backtrace and panic here for review, there is nothing private there.
Or upload the full report here and I'll check it: https://nc.netgate.com/nextcloud/s/fRCXaAN9DECGeXX
Steve
-
@stephenw10
Thank you for your help.
Have files attached here
info(1).0 textdump.tar(2).0
I do every morning at 04:58 (local time) this cronjob /var/etc/pppoe_restart_pppoe0 since my ISP forces every 24 hours a reconnect. From Status -> System Logs-> System -> General i could see the forced reboot starts during that and was finished 04:59 and maybe 40 or 50 seconds -
Panic:
Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80f51729 stack pointer = 0x28:0xfffffe009eca17f0 frame pointer = 0x28:0xfffffe009eca1a00 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 = 98910 (dpinger) rdi: fffffe009eca1798 rsi: fffffe009eca1800 rdx: 000000000e0080fe rcx: 7e3dd1feff58124a r8: 00000000ffffffa0 r9: 0000000000000018 rax: 0000000000000000 rbx: fffff8011331f800 rbp: fffffe009eca1a00 r10: fffff801a320b980 r11: fffff80017b13000 r12: 0000000000000000 r13: fffff8012ffb8484 r14: 0000000000000000 r15: 0000000000000000 <6>ng0: changing name to 'pppoe0' trap number = 12 panic: page fault cpuid = 3 time = 1733716685 KDB: enter: panicBacktrace:
db:0:kdb.enter.default> bt Tracing pid 98910 tid 228832 td 0xfffffe007c22a560 kdb_enter() at kdb_enter+0x32/frame 0xfffffe009eca14d0 vpanic() at vpanic+0x163/frame 0xfffffe009eca1600 panic() at panic+0x43/frame 0xfffffe009eca1660 trap_fatal() at trap_fatal+0x40c/frame 0xfffffe009eca16c0 trap_pfault() at trap_pfault+0x4f/frame 0xfffffe009eca1720 calltrap() at calltrap+0x8/frame 0xfffffe009eca1720 --- trap 0xc, rip = 0xffffffff80f51729, rsp = 0xfffffe009eca17f0, rbp = 0xfffffe009eca1a00 --- ip6_output() at ip6_output+0xbd9/frame 0xfffffe009eca1a00 rip6_send() at rip6_send+0x5dc/frame 0xfffffe009eca1bb0 sosend_generic() at sosend_generic+0x61a/frame 0xfffffe009eca1c70 sousrsend() at sousrsend+0x5f/frame 0xfffffe009eca1cd0 kern_sendit() at kern_sendit+0x134/frame 0xfffffe009eca1d60 sendit() at sendit+0xb7/frame 0xfffffe009eca1db0 sys_sendto() at sys_sendto+0x4d/frame 0xfffffe009eca1e00 amd64_syscall() at amd64_syscall+0x109/frame 0xfffffe009eca1f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe009eca1f30 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x3a7f6c6958aa, rsp = 0x3a7f6f1d7f28, rbp = 0x3a7f6f1d7f70 ---That's not immediately familiar. But it seems likely related to other issues where an interface is brought down and the kernel is still trying to send traffic to it.
This: https://redmine.pfsense.org/issues/14431
What exactly are you running in that script?
-
@stephenw10 said in How to handle Crash-Report:
What exactly are you running in that script?
The entry in
is just the result of the Interfaces -> WAN (pppoe0) -> Custom reset entry. I did not edit the script. I just filled the Hour (0-23), blank for * (every) and the Minute (0-59), blank for * (every) entries there.Specific date (mm/dd/yyyy) is blank.
As result pf sense created in Services -> Cron -> Settings the script /var/etc/pppoe_restart_pppoe0. But i did not edit it any further. So it's just the factory default. -
@stephenw10 said in How to handle Crash-Report:
What exactly are you running in that script?
less /var/etc/pppoe_restart_pppoe0
#!/bin/sh
/usr/local/sbin/pfSctl -c 'interface reload wan'
/usr/bin/logger -t pppoe0 "PPPoE periodic reset executed on wan" -
Ah I see.
Is this the first time you've seen it?
-
@stephenw10 said in How to handle Crash-Report:
Is this the first time you've seen it?
Yes, it was first time.
I do use pfsense since mid June 2024. So not for very long
