Hello everyone,

 

I've been trying to figure out the root cause to some recent system instability that seemed to have began about 3-4 weeks ago. Almost daily, I'm having to reboot my system due to high CPU usage or complete crash. After rebooting, system runs fine for about 24 hours and then crashing again. Not sure if this is hardware related or something else. I have an AMD system and did disable c-states. Prior to recently, everything worked fine with no issues. I have attached the diagnostics from today as I was able to capture the diagnostic from this mornings reboot up until crash. Any help would be appreciated.

plexbeast-diagnostics-20210907-1613.zip

Sep  7 13:25:51 plexbeast kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Sep  7 13:25:51 plexbeast kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 might fix it, or see below for info.

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

See also here:

https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Just pulled down the 6.10 rc1 upgrade and switched over to ipvlan. This should be easy to test because if it stays running for longer than 24 hours, that may have solved the issue for me. Fingers crossed.

Just an update, the upgrade didn't solve the problem. However, further digging into the issue yielded an issue being caused by Duplicati (Docker Container). Looks like the choice by Duplicati of using a database was the ultimate culprit. Switched from Duplicati to another backup solution (Duplicacy in this case) and system has been stable ever since.