cholzer Posted August 25, 2023 Share Posted August 25, 2023 For about 4 weeks now I get this about every 2 to 3 days in the log. The system itself continues to work though, nothing obvious "breaks, stops or freezes". Aug 24 23:19:07 NAS kernel: ------------[ cut here ]------------ Aug 24 23:19:07 NAS kernel: WARNING: CPU: 2 PID: 19856 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Aug 24 23:19:07 NAS kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat xt_nat xt_tcpudp iptable_mangle vhost_net tun vhost vhost_iotlb tap veth macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc ixgbe xfrm_algo mdio e1000e i915 iosf_mbi drm_buddy i2c_algo_bit x86_pkg_temp_thermal ttm intel_powerclamp coretemp drm_display_helper kvm_intel drm_kms_helper drm kvm i2c_i801 crct10dif_pclmul input_leds crc32_pclmul wmi_bmof mxm_wmi crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore i2c_smbus joydev led_class intel_gtt nvme agpgart i2c_core nvme_core ahci syscopyarea libahci sysfillrect sysimgblt fb_sys_fops tpm_crb tpm_tis tpm_tis_core video thermal fan wmi Aug 24 23:19:07 NAS kernel: backlight tpm acpi_pad button unix [last unloaded: xfrm_algo] Aug 24 23:19:07 NAS kernel: CPU: 2 PID: 19856 Comm: kworker/2:2 Not tainted 5.19.17-Unraid #2 Aug 24 23:19:07 NAS kernel: Hardware name: System manufacturer System Product Name/ROG STRIX Z370-E GAMING, BIOS 3005 09/30/2021 Aug 24 23:19:07 NAS kernel: Workqueue: events macvlan_process_broadcast [macvlan] Aug 24 23:19:07 NAS kernel: RIP: 0010:__nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] Aug 24 23:19:07 NAS kernel: Code: c6 48 89 44 24 10 e8 dd e2 ff ff 8b 7c 24 04 89 da 89 c6 89 04 24 e8 56 e6 ff ff 84 c0 75 a2 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 16 de ff ff e8 2c e3 ff ff e9 7e 01 Aug 24 23:19:07 NAS kernel: RSP: 0018:ffffc90000170cf0 EFLAGS: 00010202 Aug 24 23:19:07 NAS kernel: RAX: 0000000000000188 RBX: 0000000000000000 RCX: abd8a9687e187a16 Aug 24 23:19:07 NAS kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa0273140 Aug 24 23:19:07 NAS kernel: RBP: ffff8881092ebf00 R08: 3a435c8f350d0ebe R09: 4ca5bad75056aacb Aug 24 23:19:07 NAS kernel: R10: 5565a652dd6ba82b R11: 629a3762be45c08e R12: ffffffff82909480 Aug 24 23:19:07 NAS kernel: R13: 0000000000014290 R14: ffff8882803b2400 R15: 0000000000000000 Aug 24 23:19:07 NAS kernel: FS: 0000000000000000(0000) GS:ffff888426c80000(0000) knlGS:0000000000000000 Aug 24 23:19:07 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 24 23:19:07 NAS kernel: CR2: 0000150ccfa6e740 CR3: 000000000220a005 CR4: 00000000003706e0 Aug 24 23:19:07 NAS kernel: Call Trace: Aug 24 23:19:07 NAS kernel: <IRQ> Aug 24 23:19:07 NAS kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Aug 24 23:19:07 NAS kernel: nf_hook_slow+0x3a/0x96 Aug 24 23:19:07 NAS kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Aug 24 23:19:07 NAS kernel: NF_HOOK.constprop.0+0x79/0xd9 Aug 24 23:19:07 NAS kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Aug 24 23:19:07 NAS kernel: ip_sabotage_in+0x47/0x58 [br_netfilter] Aug 24 23:19:07 NAS kernel: nf_hook_slow+0x3a/0x96 Aug 24 23:19:07 NAS kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 Aug 24 23:19:07 NAS kernel: NF_HOOK.constprop.0+0x79/0xd9 Aug 24 23:19:07 NAS kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 Aug 24 23:19:07 NAS kernel: __netif_receive_skb_one_core+0x77/0x9c Aug 24 23:19:07 NAS kernel: process_backlog+0x8c/0x116 Aug 24 23:19:07 NAS kernel: __napi_poll.constprop.0+0x28/0x124 Aug 24 23:19:07 NAS kernel: net_rx_action+0x159/0x24f Aug 24 23:19:07 NAS kernel: __do_softirq+0x126/0x288 Aug 24 23:19:07 NAS kernel: do_softirq+0x7f/0xab Aug 24 23:19:07 NAS kernel: </IRQ> Aug 24 23:19:07 NAS kernel: <TASK> Aug 24 23:19:07 NAS kernel: __local_bh_enable_ip+0x4c/0x6b Aug 24 23:19:07 NAS kernel: netif_rx+0x52/0x5a Aug 24 23:19:07 NAS kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Aug 24 23:19:07 NAS kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Aug 24 23:19:07 NAS kernel: process_one_work+0x1a8/0x295 Aug 24 23:19:07 NAS kernel: worker_thread+0x18b/0x244 Aug 24 23:19:07 NAS kernel: ? rescuer_thread+0x281/0x281 Aug 24 23:19:07 NAS kernel: kthread+0xe4/0xef Aug 24 23:19:07 NAS kernel: ? kthread_complete_and_exit+0x1b/0x1b Aug 24 23:19:07 NAS kernel: ret_from_fork+0x1f/0x30 Aug 24 23:19:07 NAS kernel: </TASK> Aug 24 23:19:07 NAS kernel: ---[ end trace 0000000000000000 ]--- 2 days ago I transplanted all harddisks into a new system (different mainboard, CPU and RAM). But as you can see above I got the same problem yesterday night. Anyone an idea what could cause this or what this error actually means? It looks kinda severe? System is still on Version: 6.11.5 - I usually always wait for a few months before upgrading to a new major release for stability. Quote Link to comment
JorgeB Posted August 25, 2023 Share Posted August 25, 2023 Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)). Quote Link to comment
cholzer Posted August 25, 2023 Author Share Posted August 25, 2023 2 minutes ago, JorgeB said: Switching to ipvlan should fix it I have containers that need to have a static IP on my main LAN. If I get this right, switching to ipvlan would no allow this, right? The ipvlan type is best when connection to the physical network is not needed Also what is broken with macvlan that I have to switch? Or what causes this issue in the first place? Quote Link to comment
JorgeB Posted August 25, 2023 Share Posted August 25, 2023 4 minutes ago, cholzer said: I have containers that need to have a static IP on my main LAN. Ipvlan also supports that, but if you prefer to keep macvlan update to this release, read the release notes before. 1 Quote Link to comment
cholzer Posted August 25, 2023 Author Share Posted August 25, 2023 56 minutes ago, JorgeB said: Ipvlan also supports that, but if you prefer to keep macvlan update to this release, read the release notes before. Thx! I will wait for this release to reach stable status and then maybe a week or two before I upgrade. 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.