July 1, 20242 yr Hi all, I have a problem with my NAS. Lately, the system has been either nonresponsive or overloaded with CPU. When this happens, I am unable to access my shares or the web interface. When I check my logs, I find what appears to be part of a core dump. Also attached is a copy of the diag zip file. Where do I start to resolve this issue? Jul 1 16:37:24 unraid01 kernel: ------------[ cut here ]------------ Jul 1 16:37:24 unraid01 kernel: WARNING: CPU: 2 PID: 759 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 1 16:37:24 unraid01 kernel: Modules linked in: xt_nat xt_tcpudp 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) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls igc i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel intel_rapl_msr kvm crct10dif_pclmul drm_buddy crc32_pclmul i2c_algo_bit crc32c_intel ghash_clmulni_intel processor_thermal_device_pci_legacy sha512_ssse3 ttm mei_pxp drm_display_helper sha256_ssse3 sha1_ssse3 processor_thermal_device processor_thermal_rfim processor_thermal_mbox aesni_intel processor_thermal_rapl drm_kms_helper crypto_simd intel_rapl_common i2c_i801 cryptd mei_hdcp wmi_bmof drm nvme intel_gtt intel_cstate i2c_smbus agpgart nvme_core int340x_thermal_zone i2c_core Jul 1 16:37:24 unraid01 kernel: intel_soc_dts_iosf mei_me syscopyarea ahci sysfillrect sysimgblt mei libahci iosf_mbi fb_sys_fops thermal fan video tpm_crb wmi tpm_tis tpm_tis_core backlight tpm intel_pmc_core acpi_tad acpi_pad button unix [last unloaded: md_mod] Jul 1 16:37:24 unraid01 kernel: CPU: 2 PID: 759 Comm: kworker/u8:30 Tainted: P O 6.1.79-Unraid #1 Jul 1 16:37:24 unraid01 kernel: Hardware name: Default string Default string/Default string, BIOS GFJSL-V1.1-R208 04/20/2023 Jul 1 16:37:24 unraid01 kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Jul 1 16:37:24 unraid01 kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 1 16:37:24 unraid01 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 Jul 1 16:37:24 unraid01 kernel: RSP: 0018:ffffc900001a0d98 EFLAGS: 00010202 Jul 1 16:37:24 unraid01 kernel: RAX: 0000000000000001 RBX: ffff888123619500 RCX: 30604be7341a7af0 Jul 1 16:37:24 unraid01 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888123619500 Jul 1 16:37:24 unraid01 kernel: RBP: 0000000000000001 R08: 8ce91d82bb405af3 R09: 8cf5b29f09d4b62a Jul 1 16:37:24 unraid01 kernel: R10: 8c8c1f13979a6d38 R11: ffffc900001a0d60 R12: ffffffff82a16f40 Jul 1 16:37:24 unraid01 kernel: R13: 000000000000bf06 R14: ffff888005989e00 R15: 0000000000000000 Jul 1 16:37:24 unraid01 kernel: FS: 0000000000000000(0000) GS:ffff88817c100000(0000) knlGS:0000000000000000 Jul 1 16:37:24 unraid01 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 1 16:37:24 unraid01 kernel: CR2: 000014d11802d690 CR3: 0000000034084000 CR4: 0000000000350ee0 Jul 1 16:37:24 unraid01 kernel: Call Trace: Jul 1 16:37:24 unraid01 kernel: <IRQ> Jul 1 16:37:24 unraid01 kernel: ? __warn+0xab/0x122 Jul 1 16:37:24 unraid01 kernel: ? report_bug+0x109/0x17e Jul 1 16:37:24 unraid01 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 1 16:37:24 unraid01 kernel: ? handle_bug+0x41/0x6f Jul 1 16:37:24 unraid01 kernel: ? exc_invalid_op+0x13/0x60 Jul 1 16:37:24 unraid01 kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 1 16:37:24 unraid01 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 1 16:37:24 unraid01 kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jul 1 16:37:24 unraid01 kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Jul 1 16:37:24 unraid01 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jul 1 16:37:24 unraid01 kernel: nf_hook_slow+0x3a/0x96 Jul 1 16:37:24 unraid01 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 1 16:37:24 unraid01 kernel: NF_HOOK.constprop.0+0x79/0xd9 Jul 1 16:37:24 unraid01 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 1 16:37:24 unraid01 kernel: __netif_receive_skb_one_core+0x77/0x9c Jul 1 16:37:24 unraid01 kernel: process_backlog+0x8c/0x116 Jul 1 16:37:24 unraid01 kernel: __napi_poll.constprop.0+0x28/0x124 Jul 1 16:37:24 unraid01 kernel: net_rx_action+0x159/0x24f Jul 1 16:37:24 unraid01 kernel: __do_softirq+0x126/0x288 Jul 1 16:37:24 unraid01 kernel: do_softirq+0x7f/0xab Jul 1 16:37:24 unraid01 kernel: </IRQ> Jul 1 16:37:24 unraid01 kernel: <TASK> Jul 1 16:37:24 unraid01 kernel: __local_bh_enable_ip+0x4c/0x6b Jul 1 16:37:24 unraid01 kernel: netif_rx+0x52/0x5a Jul 1 16:37:24 unraid01 kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 1 16:37:24 unraid01 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Jul 1 16:37:24 unraid01 kernel: process_one_work+0x1a8/0x295 Jul 1 16:37:24 unraid01 kernel: worker_thread+0x18b/0x244 Jul 1 16:37:24 unraid01 kernel: ? rescuer_thread+0x281/0x281 Jul 1 16:37:24 unraid01 kernel: kthread+0xe4/0xef Jul 1 16:37:24 unraid01 kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 1 16:37:24 unraid01 kernel: ret_from_fork+0x1f/0x30 Jul 1 16:37:24 unraid01 kernel: </TASK> Jul 1 16:37:24 unraid01 kernel: ---[ end trace 0000000000000000 ]--- unraid01-diagnostics-20240701-1712.zip
July 1, 20242 yr Community Expert Solution 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.
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.