jdsour Posted July 7, 2022 Share Posted July 7, 2022 (edited) Hi all, I'm quite new to unraid so not a whole lot of knowledge, I've been getting a Kernal panic every couple of weeks and I'm stumped as to what is causing it. Below is a screenshot of the last time it happend, hopefully someone will be able to help. Cheers Edited July 7, 2022 by jdsour Quote Link to comment
JorgeB Posted July 7, 2022 Share Posted July 7, 2022 Enable the syslog server and post that and the complete diagnostics after the next crash. Quote Link to comment
jdsour Posted July 7, 2022 Author Share Posted July 7, 2022 (edited) I have the syslog running if you'd like to take a look. I rebooted around 10.30 syslog-192.168.0.100.log tower-diagnostics-20220707-1229.zip Edited July 7, 2022 by jdsour Quote Link to comment
JorgeB Posted July 7, 2022 Share Posted July 7, 2022 Dec 11 08:40:14 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Dec 11 08:40:14 Tower 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 and 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/ Quote Link to comment
jdsour Posted July 7, 2022 Author Share Posted July 7, 2022 Ok great, I'll give it a go, thanks for your help JorgeB much appreciated. 1 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.