Random errors since upgrading to 6.10

[mattekure]

Since upgrading to 6.10, I've noticed frequent random errors in the log.  I have no idea what might be causing these, the system ran fine for over a year under 6.9.2.  Last night it crashed to the point of requiring a hard reboot.  I could not ssh in.   I have attached diagnostics.

 

 

May 23 12:53:21 Tower kernel: ------------[ cut here ]------------
May 23 12:53:21 Tower kernel: WARNING: CPU: 19 PID: 0 at net/netfilter/nf_conntrack_core.c:1192 __nf_conntrack_confirm+0xb8/0x254 [nf_conntrack]
May 23 12:53:21 Tower kernel: Modules linked in: input_leds led_class xt_connmark xt_mark xt_comment iptable_raw nvidia_uvm(PO) veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle macvlan xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod nvidia_modeset(PO) nvidia(PO) drm backlight nct6775 hwmon_vid efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables edac_mce_amd crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd wmi_bmof mxm_wmi mpt3sas igb rapl i2c_piix4 i2c_algo_bit ahci raid_class k10temp i2c_core scsi_transport_sas libahci wmi button acpi_cpufreq [last unloaded: ccp]
May 23 12:53:21 Tower kernel: CPU: 19 PID: 0 Comm: swapper/19 Tainted: P           O      5.15.40-Unraid #1
May 23 12:53:21 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P4.40 06/23/2021
May 23 12:53:21 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xb8/0x254 [nf_conntrack]
May 23 12:53:21 Tower kernel: Code: 89 c6 48 89 44 24 18 e8 53 e4 ff ff 44 89 f2 44 89 ef 89 c6 89 c5 e8 2c e8 ff ff 84 c0 75 9f 49 8b 87 80 00 00 00 a8 08 74 19 <0f> 0b 89 ee 44 89 ef 45 31 e4 e8 dc df ff ff e8 ae e4 ff ff e9 71
May 23 12:53:21 Tower kernel: RSP: 0018:ffffc9000058c878 EFLAGS: 00010202
May 23 12:53:21 Tower kernel: RAX: 0000000000000188 RBX: ffffffff828e3500 RCX: 4c6f57b7dba5feee
May 23 12:53:21 Tower kernel: RDX: 0000000000000000 RSI: 00000000000001b4 RDI: ffffffffa0442910
May 23 12:53:21 Tower kernel: RBP: 00000000000295b4 R08: 13a07e8279bd786b R09: da3c3c485d577177
May 23 12:53:21 Tower kernel: R10: b8bbed1e1e242eab R11: d92e2be3294076ec R12: 0000000000028cc7
May 23 12:53:21 Tower kernel: R13: 0000000000028cc7 R14: 0000000000000000 R15: ffff88846356b900
May 23 12:53:21 Tower kernel: FS:  0000000000000000(0000) GS:ffff888ffecc0000(0000) knlGS:0000000000000000
May 23 12:53:21 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 23 12:53:21 Tower kernel: CR2: 000014fefd43ad14 CR3: 0000000635e00000 CR4: 0000000000350ee0
May 23 12:53:21 Tower kernel: Call Trace:
May 23 12:53:21 Tower kernel: <IRQ>
May 23 12:53:21 Tower kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack]
May 23 12:53:21 Tower kernel: nf_hook_slow+0x3e/0x93
May 23 12:53:21 Tower kernel: ? ip_protocol_deliver_rcu+0x135/0x135

 

tower-diagnostics-20220523-1332.zip

[JorgeB]

Try changing the docker custom network type to ipvlan, advanced view must be enable on the docker settings page.

[mattekure]

ok.  I've done that and restarted the docker.  I'll monitor it and see if it pops up again.

[Breki]

I've had the same issues on my Unraid installation. I've now also changed the Docker custom network type to `ipvlan` and will monitor the situation as well.

[Waddoo]

Mar 22 19:39:10 Alexandria kernel: WARNING: CPU: 5 PID: 1298 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack]
Mar 22 19:39:10 Alexandria kernel: Modules linked in: nvidia_uvm(PO) xt_mark macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs nfsd lockd grace sunrpc md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) drm backlight agpgart iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables mlx4_en mlx4_core r8169 realtek edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas wmi_bmof glue_helper i2c_piix4 wmi k10temp raid_class scsi_transport_sas i2c_core
Mar 22 19:39:10 Alexandria kernel: ccp rapl ahci libahci button acpi_cpufreq [last unloaded: mlx4_core]
Mar 22 19:39:10 Alexandria kernel: CPU: 5 PID: 1298 Comm: kworker/5:1 Tainted: P S         O      5.10.28-Unraid #1
Mar 22 19:39:10 Alexandria kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.60 06/11/2020
Mar 22 19:39:10 Alexandria kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Mar 22 19:39:10 Alexandria kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack]

 

Is this the similar error to what this thread was getting? How has the stability been after switching to ipvlan?

I am still running Unraid OS 6.9.2