Kernel Panics on version 6.11.1

[mlody11]

I've been dealing with the Unraid kernel going into panic for many weeks now and I don't what to do at this point.  Here is what I've done so far.

1) replaced power supply

2) replaced motherboard

3) replaced memory

4) replaced CPU (but with same type)

5) switch from SATA multiplier to SAS controller (all drives are on the SAS controller except for the NVME drives)

 

Still getting kernel panics.  Please help.  Diagnostics attached.

 

doing memtest again but the memory was replaced... so I'd be amazed.

 

tower-diagnostics-20221105-1336.zip

Edited November 5, 2022 by mlody11

[Alex43]

What is your motherboard and CPU?  If it is AMD/Ryzen, I had a panic as well.  There are details in the FAQ about some power settings in the BIOS that you may have that seem to have stabilized it for me (although I'm only a few days in, to be fair)

[mlody11]

The CPU is, what is fairly old now, i7 6700K.  None of it is overclocked.  Its running with 4 sticks of 8GB RAM.  The memtest has done 2 passes at this point, 0 errors.  Really stumped on what is happening.

[JorgeB]

Enable the syslog server and post that after a crash.

[mlody11]

Sure, I keep them on a Splunk server so here is the csv export for it.  Attached is the overnight memtest result too.

crash_logs.csv

 

I should add... I did some research and I am running custom static IPs and docker access to the host. So, about 10 minutes ago I switch to ipvlan instead of macvlan for docker.

Edited November 6, 2022 by mlody11

[JorgeB]

33 minutes ago, mlody11 said:

So, about 10 minutes ago I switch to ipvlan instead of macvlan for docker.

Yes, that should help since the logged call traced appeared to be related to macvlan.

[mlody11]

May be a bit early still because I have gone 2 weeks between errors but I think they've been occurring more frequently lately so I think the ipvlan vs macvlan might have solved it.