Experiencing similar behavior mentioned in this post: https://forum.opnsense.org/index.php?topic=39236.
System information:
- OPNsense 24.1.9_4-amd64
- FreeBSD 13.2-RELEASE-p11
- OpenSSL 3.0.14
Running on Protectli Vault FW4B – 4 Port Intel® J3160
Attached is the information from the firmware reporter page, please let me know what else I should provide
Can you connect a PC to the serial console and watch if there are kernel messages preceding the reboot?
the attachment is the buffer leading up to it Patrick. Seems a kernel panic lead from packet routing.
Looking at the last crash report I see this
panic: Unknown caching mode 14
cpuid = 1
time = 1719289561
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00a15f98f0
vpanic() at vpanic+0x151/frame 0xfffffe00a15f9940
panic() at panic+0x43/frame 0xfffffe00a15f99a0
pmap_enter_quick_locked() at pmap_enter_quick_locked+0x39a/frame 0xfffffe00a15f9a00
pmap_enter_object() at pmap_enter_object+0x1f8/frame 0xfffffe00a15f9a80
vm_map_pmap_enter() at vm_map_pmap_enter+0x2b6/frame 0xfffffe00a15f9af0
vm_map_insert() at vm_map_insert+0x4f9/frame 0xfffffe00a15f9b80
vm_map_fixed() at vm_map_fixed+0x182/frame 0xfffffe00a15f9be0
vm_mmap_object() at vm_mmap_object+0x1b8/frame 0xfffffe00a15f9c50
vn_mmap() at vn_mmap+0x141/frame 0xfffffe00a15f9ce0
kern_mmap_req() at kern_mmap_req+0x596/frame 0xfffffe00a15f9dc0
sys_mmap() at sys_mmap+0x46/frame 0xfffffe00a15f9e00
amd64_syscall() at amd64_syscall+0x10c/frame 0xfffffe00a15f9f30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00a15f9f30
--- syscall (477, FreeBSD ELF64, mmap), rip = 0x4c67daff061a, rsp = 0x382114c5c678, rbp = 0x382114c5c7e0 ---
KDB: enter: panic
panic.txt0600003014636443331 7140 ustarrootwheelUnknown caching mode 14
version.txt0600007514636443331 7544 ustarrootwheelFreeBSD 13.2-RELEASE-p11 stable/24.1-n255023-99a14409566 SMP
the previous messages are also interesting.
Do you have the cpu firmware up to date? There's a thread somewhere here about those newer intel cpus having stability problems -I think- , solved or mitigated with those updates.
You could do a memtest just to be sure and could also install a vanilla freebsd installation.
Point being, crashes are usually hardware related.
Following up in case anyone has the same issue... this was in fact due to my firmware. After updating the issue resolved.
Which firmware was it and how did you fix it?
I was previously on an old version of coreboot, flashed the device using Protectli's Flashli tool to the most recent AMI version: https://kb.protectli.com/kb/how-to-use-flashli/