January 6, 20242 yr Jan 5 18:56:28 Tower kernel: ------------[ cut here ]------------ Jan 5 18:56:28 Tower kernel: WARNING: CPU: 1 PID: 13603 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jan 5 18:56:28 Tower kernel: Modules linked in: xt_nat xt_tcpudp nvidia_uvm(PO) macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nvidia(PO) mei_pxp mei_hdcp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel btusb sha512_ssse3 btrtl aesni_intel drm_kms_helper crypto_simd btbcm btintel cryptd wmi_bmof intel_wmi_thunderbolt mxm_wmi rapl intel_cstate drm intel_uncore nvme i2c_i801 bluetooth e1000e i2c_smbus nvme_core i2c_core mei_me syscopyarea sysfillrect sysimgblt mei video ahci ecdh_generic input_leds Jan 5 18:56:28 Tower kernel: led_class ecc libahci fb_sys_fops joydev wmi backlight intel_pmc_core button acpi_pad unix Jan 5 18:56:28 Tower kernel: CPU: 1 PID: 13603 Comm: kworker/u16:1 Tainted: P O 6.1.63-Unraid #1 Jan 5 18:56:28 Tower kernel: Hardware name: System manufacturer System Product Name/MAXIMUS VIII HERO ALPHA, BIOS 3801 03/14/2018 Jan 5 18:56:28 Tower kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Jan 5 18:56:28 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jan 5 18:56:28 Tower kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Jan 5 18:56:28 Tower kernel: RSP: 0018:ffffc90000154d98 EFLAGS: 00010202 Jan 5 18:56:28 Tower kernel: RAX: 0000000000000001 RBX: ffff8881cf57eb00 RCX: 80d6b68f374d667c Jan 5 18:56:28 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881cf57eb00 Jan 5 18:56:28 Tower kernel: RBP: 0000000000000001 R08: e6eea51f8de62d21 R09: 0102eb91e5109e49 Jan 5 18:56:28 Tower kernel: R10: 0045d5a4c4398db9 R11: ffffc90000154d60 R12: ffffffff82a14d00 Jan 5 18:56:28 Tower kernel: R13: 000000000002a5d6 R14: ffff88810312b900 R15: 0000000000000000 Jan 5 18:56:28 Tower kernel: FS: 0000000000000000(0000) GS:ffff88884ec40000(0000) knlGS:0000000000000000 Jan 5 18:56:28 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 5 18:56:28 Tower kernel: CR2: 0000000002935000 CR3: 000000000420a003 CR4: 00000000003706e0 Jan 5 18:56:28 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jan 5 18:56:28 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jan 5 18:56:28 Tower kernel: Call Trace: Jan 5 18:56:28 Tower kernel: <IRQ> Jan 5 18:56:28 Tower kernel: ? __warn+0xab/0x122 Jan 5 18:56:28 Tower kernel: ? report_bug+0x109/0x17e Jan 5 18:56:28 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jan 5 18:56:28 Tower kernel: ? handle_bug+0x41/0x6f Jan 5 18:56:28 Tower kernel: ? exc_invalid_op+0x13/0x60 Jan 5 18:56:28 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Jan 5 18:56:28 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jan 5 18:56:28 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jan 5 18:56:28 Tower kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Jan 5 18:56:28 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jan 5 18:56:28 Tower kernel: nf_hook_slow+0x3a/0x96 Jan 5 18:56:28 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jan 5 18:56:28 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Jan 5 18:56:28 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jan 5 18:56:28 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c Jan 5 18:56:28 Tower kernel: process_backlog+0x8c/0x116 Jan 5 18:56:28 Tower kernel: __napi_poll.constprop.0+0x28/0x124 Jan 5 18:56:28 Tower kernel: net_rx_action+0x159/0x24f Jan 5 18:56:28 Tower kernel: __do_softirq+0x126/0x288 Jan 5 18:56:28 Tower kernel: do_softirq+0x7f/0xab Jan 5 18:56:28 Tower kernel: </IRQ> Jan 5 18:56:28 Tower kernel: <TASK> Jan 5 18:56:28 Tower kernel: __local_bh_enable_ip+0x4c/0x6b Jan 5 18:56:28 Tower kernel: netif_rx+0x52/0x5a Jan 5 18:56:28 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jan 5 18:56:28 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Jan 5 18:56:28 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Jan 5 18:56:28 Tower kernel: process_one_work+0x1a8/0x295 Jan 5 18:56:28 Tower kernel: worker_thread+0x18b/0x244 Jan 5 18:56:28 Tower kernel: ? rescuer_thread+0x281/0x281 Jan 5 18:56:28 Tower kernel: kthread+0xe4/0xef Jan 5 18:56:28 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Jan 5 18:56:28 Tower kernel: ret_from_fork+0x1f/0x30 Jan 5 18:56:28 Tower kernel: </TASK> Jan 5 18:56:28 Tower kernel: ---[ end trace 0000000000000000 ]---
January 6, 20242 yr Community Expert Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.
January 6, 20242 yr Author Thank you very much @JorgeB , I noticed the system was unresponsive yesterday as well. It's interesting these things just started happening recently. I just made the switch.
January 7, 20242 yr Author Hey @JorgeB , I had to go back to macvlan. Reasoning is that I want some of my containers to run on br0 having their own IP. My Router's Wireguard needs a unique Mac Address to put those IP/Mac Address to use VPN (like Plex) MacVlan creates unique Mac Addresses for those br0 instances. When I put it on IPVLAN, all containers on br0 shared the same Mac Address with the host and I didn't want that.
January 7, 20242 yr Community Expert Solution https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces
January 8, 20242 yr Author Thanks @trurl , I went ahead and changed everything per that document... using custom eth0: now
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.