Random Crashes just started and don't know why

Beginning about 20 May 2025, I have been experiencing what appears to be random crashes. What I do know, is that I have not changed any configuration or hardware up until that point. I originally thought it might be a docker container causing it, because i was having some issues with my Frigate NVR container. I first realized it was crashing/restarting, because with the containers up, it alerts me when some of them restart. No Truenas related emails or anything. This is verified by checking the uptime in Truenas

This behavior began happening while running Electric Eel Successfully for a while, and so I tried to see if upgrading to Fangtooth 25.04.1 would fix anything. It did not.

To further troubleshoot, and try to ensure it wasn’t a container causing some weird crash, last night, i stopped all my containers and after some time the issue still occurred.

I have ran Memtest86 and all 4 passes completed with no RAM or ECC errors.
I looked through the logs, and nothing jumped out at me from those, but I am also a noob when it comes to looking at the var/log/messages.

Wondering if anyone has any ideas where to go from here, or maybe can look at the logs and see what they think? Below are some approx times that i KNOW the crash/reboot occurred.
-02:38
-23:20

My Setup:
ASROCK RACK W680D4U-2L2T/G5
Intel(R) Core™ i5-14500
128GB 4x Kingston DDR5 4800 ECC UDIMM
LSI/Broadcom 9305 16i HBA
8x Seagate Exos 20TB
6x 2TB Samsung SSDs
2X Seagate Skyhawk AI 12TB

Thank you to anyone who has some thoughts

Full logs attached.
truenas612025_0237.txt (2.1 MB)

Here is an example, but not every crash/reboot looks the same.

May 29 22:13:23 truenas kernel: veth350079d: entered promiscuous mode
May 29 22:13:23 truenas kernel: br-5bc9fd42e2d4: port 2(vethf74ceff) entered blocking state
May 29 22:13:23 truenas kernel: br-5bc9fd42e2d4: port 2(vethf74ceff) entered disabled state
May 29 22:13:23 truenas kernel: vethf74ceff: entered allmulticast mode
May 29 22:13:23 truenas kernel: vethf74ceff: entered promiscuous mode
May 29 22:13:23 truenas kernel: eth0: renamed from veth304e063
May 29 22:13:23 truenas kernel: br-2c0fa881dc58: port 3(veth350079d) entered blocking state
May 29 22:13:23 truenas kernel: br-2c0fa881dc58: port 3(veth350079d) entered forwarding state
May 29 22:13:23 truenas kernel: eth1: renamed from veth1378091
May 29 22:13:23 truenas kernel: br-5bc9fd42e2d4: port 2(vethf74ceff) entered blocking state
May 29 22:13:23 truenas kernel: br-5bc9fd42e2d4: port 2(vethf74ceff) entered forwarding state
May 29 22:13:33 truenas kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd
May 29 22:13:33 truenas kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM.
May 29 22:16:09 truenas kernel: av:h264:df0[441885]: segfault at 7fb5779d4bc8 ip 00007fb535c6e67e sp 00007fb5347fe080 error 6 in iHD_drv_video.so[99467e,7fb53542d000+951000] likely on CPU 10 (core 20, socket 0)
May 29 22:16:09 truenas kernel: Code: 01 00 00 80 3d aa 1e ef 01 00 74 30 48 83 fe 1f 0f 87 8e 01 00 00 48 8d 04 76 48 c1 e0 04 49 83 7c 07 60 00 74 16 48 8d 55 b0 <4c> 89 bd e8 6a 1d 43 ff 89 c6 c4 c0 0f 85 91 01 00 00 0b 8b 45 c8
May 29 23:13:18 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 29 23:13:19 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 29 23:13:20 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 00:13:18 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 00:13:19 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 00:13:20 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 01:13:18 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 01:13:19 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 01:13:20 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 01:55:45 truenas kernel: mux0:segment[441783]: segfault at c34a1c3 ip 0000561bc2b58d54 sp 00007fad637fd7a0 error 4 in ffmpeg[985d54,561bc2592000+5e74000] likely on CPU 8 (core 16, socket 0)
May 30 01:55:45 truenas kernel: Code: 4b 10 49 39 c9 0f 84 c1 0d 00 00 48 89 d0 48 0f ba f0 3f 48 85 c0 74 4b 44 89 c8 66 6c 2e 0f 1f 8e 00 00 00 ca 00 48 8b 45 10 <f6> 41 6e 02 75 12 83 8b 4d 10 0b 09 83 e9 36 83 f9 01 3b 87 54 05
May 30 02:13:18 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 02:13:19 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 02:13:20 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 02:13:21 truenas kernel: br60: received packet on vlan60 with own address as source address (addr:1e:2a:55:e3:b9:38, vlan:0)
May 30 02:43:43 truenas syslog-ng[6764]: syslog-ng starting up; version='3.38.1'
May 30 02:42:58 truenas kernel: Linux version 6.12.15-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Mon May 26 13:44:31 UTC 2025
May 30 02:42:58 truenas kernel: Command line: BOOT_IMAGE=/ROOT/25.04.1@/boot/vmlinuz-6.12.15-production+truenas root=ZFS=boot-pool/ROOT/25.04.1 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N
May 30 02:42:58 truenas kernel: x86/tme: not enabled by BIOS
May 30 02:42:58 truenas kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
May 30 02:42:58 truenas kernel: BIOS-provided physical RAM map:
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000067767fff] usable
May 30 02:42:58 truenas kernel: BIOS-e820: [mem 0x0000000067768000-0x0000000067768fff] reserved

Here is another example

type or pasteMay 31 23:26:25 truenas kernel: vethfd58272: renamed from eth0
May 31 23:26:25 truenas kernel: br-7db48bb42ad8: port 4(veth981633a) entered disabled state
May 31 23:26:25 truenas kernel: veth981633a (unregistering): left allmulticast mode
May 31 23:26:25 truenas kernel: veth981633a (unregistering): left promiscuous mode
May 31 23:26:25 truenas kernel: br-7db48bb42ad8: port 4(veth981633a) entered disabled state
May 31 23:26:26 truenas kernel: br-9d9de3914766: port 1(veth7fdf840) entered disabled state
May 31 23:26:26 truenas kernel: veth32dbb72: renamed from eth1
May 31 23:26:26 truenas kernel: br-9d9de3914766: port 1(veth7fdf840) entered disabled state
May 31 23:26:26 truenas kernel: veth7fdf840 (unregistering): left allmulticast mode
May 31 23:26:26 truenas kernel: veth7fdf840 (unregistering): left promiscuous mode
May 31 23:26:26 truenas kernel: br-9d9de3914766: port 1(veth7fdf840) entered disabled state
May 31 23:26:26 truenas kernel: br-7db48bb42ad8: port 1(veth93b8927) entered disabled state
May 31 23:26:26 truenas kernel: veth97b53d9: renamed from eth0
May 31 23:26:26 truenas kernel: br-7db48bb42ad8: port 1(veth93b8927) entered disabled state
May 31 23:26:26 truenas kernel: veth93b8927 (unregistering): left allmulticast mode
May 31 23:26:26 truenas kernel: veth93b8927 (unregistering): left promiscuous mode
May 31 23:26:26 truenas kernel: br-7db48bb42ad8: port 1(veth93b8927) entered disabled state
May 31 23:27:09 truenas kernel: loop0: detected capacity change from 0 to 3241176
May 31 23:27:09 truenas kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
May 31 23:40:23 truenas kernel: show_signal_msg: 7 callbacks suppressed
May 31 23:40:23 truenas kernel: PLUGIN[proc net[9503]: segfault at 59c309f4ceb0 ip 000055c2eb8fec4a sp 00007f19cbb37670 error 4 in netdata[c0c4a,55c2eb852000+270000] likely on CPU 4 (core 8, socket 0)
May 31 23:40:23 truenas kernel: Code: 0f 14 f6 41 89 d0 31 c9 41 55 49 89 fd ba 01 00 00 00 66 0f 28 ca 41 54 49 89 f4 55 53 48 83 ec 38 48 8b 47 58 0f 29 74 24 20 <48> 8b 78 10 48 8b 40 58 f2 0f 11 44 24 08 ff 50 08 48 b8 db 34 b6
May 31 23:40:26 truenas netdata[31224]: CONFIG: cannot load cloud config '/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
Jun  1 00:30:43 truenas kernel: loop0: detected capacity change from 0 to 3241176
Jun  1 02:38:25 truenas syslog-ng[6769]: syslog-ng starting up; version='3.38.1'
Jun  1 02:37:27 truenas kernel: Linux version 6.12.15-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Mon May 26 13:44:31 UTC 2025
Jun  1 02:37:27 truenas kernel: Command line: BOOT_IMAGE=/ROOT/25.04.1@/boot/vmlinuz-6.12.15-production+truenas root=ZFS=boot-pool/ROOT/25.04.1 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N
Jun  1 02:37:27 truenas kernel: x86/tme: not enabled by BIOS
Jun  1 02:37:27 truenas kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Jun  1 02:37:27 truenas kernel: BIOS-provided physical RAM map:
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000067767fff] usable
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000067768000-0x0000000067768fff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000067769000-0x00000000687c9fff] usable
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x00000000687ca000-0x00000000687cafff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x00000000687cb000-0x0000000071ba8fff] usable
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000071ba9000-0x0000000074ca8fff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000074ca9000-0x0000000074d9afff] ACPI data
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000074d9b000-0x0000000074ec6fff] ACPI NVS
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000074ec7000-0x0000000075f02fff] reserved
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000075f03000-0x0000000075ffefff] type 20
Jun  1 02:37:27 truenas kernel: BIOS-e820: [mem 0x0000000075fff000-0x0000000075ffffff] usable code here

Just posting back here in case this helps anyone in the future. Im still not sure whay happened or why it started happening suddenly but i seemed to have fixed it by blowing away and rebuilding all my network interfaces.

The only thing that lead me down thay path is that right before truenas died, it always had a bunch of

br60: received packet on vlan60 with own address as source

Errors. Since redoing the network interfaces my issue went away.