Random freeze and forced reboot

[exico]

I've been dealing with this for 2 weeks...

I have a very strange random freeze that only a reset or forced shutdown can clear.

 

I had problem with setting  up the syslog but now it works.

 

What i did so far:

- Remove HBA (LSI 9211) working for 5 years or so

- Remove NIC (HP branded Broadcom 10G ethernet)

- Remove video card (1050 ti)

- Swap PSU

- Memtest the RAM

- Swap the Motherboard with a Gigabyte X79 UP4 with a 4930K and some ddr3 ram

 

At the moment I have just my motherboard with a NVME adapter and 8 Sata drives and im using the integrated 1G nic (e1000) and sata ports

The motherboard is a Supermicro X9SRL-F with a E5-2697 v2 CPU and 64 GB of RAM

 

I attached diagnostics and the last syslog. The last freeze occured at "Nov 13 12:29:29"

 

Checking the syslog I was a "tainted kernel" (you can see one at line 8284 "Nov 13 12:28:29 UNRAIDSRV kernel: CPU: 16 PID: 11248 Comm: kworker/16:1 Tainted: P        W  O       6.1.49-Unraid #1"

After some digging i got this:

root@UNRAIDSRV:~# cat /proc/sys/kernel/tainted
4609
root@UNRAIDSRV:~# ./kernel-chktaint
Kernel is "tainted" for the following reasons:
 * proprietary module was loaded (#0)
 * kernel issued warning (#9)
 * externally-built ('out-of-tree') module was loaded  (#12)
For a more detailed explanation of the various taint flags see
 Documentation/admin-guide/tainted-kernels.rst in the Linux kernel sources
 or https://kernel.org/doc/html/latest/admin-guide/tainted-kernels.html
Raw taint value as int/string: 4609/'P        W  O      '
root@UNRAIDSRV:~#

 

 

Im not a big linux person so I can go so far.

 

Do you have any suggestion on what i can try before i go mad?

syslog-127.0.0.1.zip unraidsrv-diagnostics-20231113-1317.zip

[JorgeB]

Nov 13 04:20:23 UNRAIDSRV kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Nov 13 04:20:23 UNRAIDSRV kernel: ? _raw_spin_unlock+0x14/0x29
Nov 13 04:20:23 UNRAIDSRV kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

[exico]

Will do and report back.

 

If it is that its strange. Didnt change it or added containers in a while and happened out of the blue.

[JorgeB]

It's not uncommon to start after an Unraid release update.

[exico]

Well I did update the system roughly 1 week after 6.12.4 came out. Thats why its strange.

 

Anyway I can report that no more crashes occured. At least for now.