dmynerd78 Posted June 22, 2022 Share Posted June 22, 2022 (edited) I've been getting ever more frequent kernel panics sporadically and I can't seem to resolve it. Here's some things I've done: Installed ECC RAM & disabled any overclocking (Done around April/May; have not run memtest yet) Remove all docker containers (and docker.img) and up new containers (Done on the weekend of June 3, 2022) Ensure all docker containers and plugins are up to date Run the Fix Common Problems plugin and check for issues Any help or pointers would be greatly appreciated 🙂 Each tower diagnostic was taken immediately after rebooting from the kernel panic. There's also a syslog text file which has logging since May 6th (sadly I don't have all the diagnostics for all the kernel panics listed in the syslog, but I've uploaded the last 3) tower-diagnostics-20220622-1128.zip syslog.txt Edited August 12, 2022 by dmynerd78 cleanup Quote Link to comment
Solution JorgeB Posted June 23, 2022 Solution Share Posted June 23, 2022 Jun 14 10:00:47 172.18.0.1 kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jun 14 10:00:47 172.18.0.1 kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more 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/ 1 Quote Link to comment
dmynerd78 Posted June 23, 2022 Author Share Posted June 23, 2022 17 minutes ago, JorgeB said: Jun 14 10:00:47 172.18.0.1 kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jun 14 10:00:47 172.18.0.1 kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more 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/ I've set the network to be ipvlan so fingers crossed that fixes it. Thanks for the help! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.