Help with a call trace in 6.8.0

[EgillSkallagrimsson]

I've been getting this in my logs about every few hours. Any ideas how to fix it?

WARNING: CPU: 14 PID: 89337 at net/netfilter/nf_conntrack_core.c:945 __nf_conntrack_confirm+0xa0/0x69e
Dec 23 18:11:15 Server kernel: Modules linked in: dm_mod dax veth xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net macvlan tun vhost tap ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod igb i2c_algo_bit sr_mod cdrom sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper mpt3sas i2c_i801 intel_cstate i2c_core intel_uncore intel_rapl_perf ahci raid_class libahci scsi_transport_sas pcc_cpufreq wmi ipmi_si button [last unloaded: i2c_algo_bit]
Dec 23 18:11:15 Server kernel: CPU: 14 PID: 89337 Comm: kworker/14:0 Not tainted 4.19.88-Unraid #1
Dec 23 18:11:15 Server kernel: Hardware name: ZTSYSTEM CYPRESS11      /S2600CP   , BIOS SE5C600.86B.02.06.0006.032420170950 03/24/2017
Dec 23 18:11:15 Server kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Dec 23 18:11:15 Server kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x69e
Dec 23 18:11:15 Server kernel: Code: 04 e8 56 fb ff ff 44 89 f2 44 89 ff 89 c6 41 89 c4 e8 7f f9 ff ff 48 8b 4c 24 08 84 c0 75 af 48 8b 85 80 00 00 00 a8 08 74 26 <0f> 0b 44 89 e6 44 89 ff 45 31 f6 e8 94 f1 ff ff be 00 02 00 00 48
Dec 23 18:11:15 Server kernel: RSP: 0018:ffff88882e983d90 EFLAGS: 00010202
Dec 23 18:11:15 Server kernel: RAX: 0000000000000188 RBX: ffff88882bb8a700 RCX: ffff88807403ec18
Dec 23 18:11:15 Server kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffffff81e08dc0
Dec 23 18:11:15 Server kernel: RBP: ffff88807403ebc0 R08: 000000003743f580 R09: ffff888755937c60
Dec 23 18:11:15 Server kernel: R10: 0000000000000000 R11: ffff88878de5a800 R12: 000000000000a137
Dec 23 18:11:15 Server kernel: R13: ffffffff81e91100 R14: 0000000000000000 R15: 00000000000015f0
Dec 23 18:11:15 Server kernel: FS:  0000000000000000(0000) GS:ffff88882e980000(0000) knlGS:0000000000000000
Dec 23 18:11:15 Server kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 23 18:11:15 Server kernel: CR2: 000015440b9e7000 CR3: 0000000001e0a006 CR4: 00000000000626e0
Dec 23 18:11:15 Server kernel: Call Trace:
Dec 23 18:11:15 Server kernel: <IRQ>
Dec 23 18:11:15 Server kernel: ipv4_confirm+0xaf/0xb9
Dec 23 18:11:15 Server kernel: nf_hook_slow+0x3a/0x90
Dec 23 18:11:15 Server kernel: ip_local_deliver+0xad/0xdc
Dec 23 18:11:15 Server kernel: ? ip_sublist_rcv_finish+0x54/0x54
Dec 23 18:11:15 Server kernel: ip_rcv+0xa0/0xbe
Dec 23 18:11:15 Server kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1
Dec 23 18:11:15 Server kernel: __netif_receive_skb_one_core+0x53/0x6f
Dec 23 18:11:15 Server kernel: process_backlog+0x77/0x10e
Dec 23 18:11:15 Server kernel: net_rx_action+0x107/0x26c
Dec 23 18:11:15 Server kernel: __do_softirq+0xc9/0x1d7
Dec 23 18:11:15 Server kernel: do_softirq_own_stack+0x2a/0x40
Dec 23 18:11:15 Server kernel: </IRQ>
Dec 23 18:11:15 Server kernel: do_softirq+0x4d/0x5a
Dec 23 18:11:15 Server kernel: netif_rx_ni+0x1c/0x22
Dec 23 18:11:15 Server kernel: macvlan_broadcast+0x111/0x156 [macvlan]
Dec 23 18:11:15 Server kernel: ? __switch_to_asm+0x41/0x70
Dec 23 18:11:15 Server kernel: macvlan_process_broadcast+0xea/0x128 [macvlan]
Dec 23 18:11:15 Server kernel: process_one_work+0x16e/0x24f
Dec 23 18:11:15 Server kernel: worker_thread+0x1e2/0x2b8
Dec 23 18:11:15 Server kernel: ? rescuer_thread+0x29e/0x29e
Dec 23 18:11:15 Server kernel: kthread+0x10c/0x114
Dec 23 18:11:15 Server kernel: ? kthread_park+0x89/0x89
Dec 23 18:11:15 Server kernel: ret_from_fork+0x35/0x40
Dec 23 18:11:15 Server kernel: ---[ end trace 8c53befd60a8c7ab ]---

 

[JorgeB]

Macvlan call traces are usually caused by dockers with custom IP addresses.

[EgillSkallagrimsson]

Well, it ended up being my Windows 10 VM that I had moved over to the second nic on my motherboard do to the TUN error in the 6.8 beta releases making my logs an unreadable mess. Switched it back to using one nic and the call traces quit showing up in the logs.