Hi, 

 

Today my system loaded the GUI but multiple of tabs would not load the usual data (dashboard, plugins, and apps). Then the system (booted into GUI) froze. I attached the diagnostics after a hard reset. I see there is a series of Kernel messages at the end, though I am not sure what to do with that. The GUI is operating nominally at this point. 

 

Appreciate your help. 

 

 

Quote

Dec 11 20:24:07 Knox kernel: ------------[ cut here ]------------
Dec 11 20:24:07 Knox kernel: WARNING: CPU: 0 PID: 30043 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
Dec 11 20:24:07 Knox kernel: Modules linked in: xt_mark tun tcp_diag udp_diag inet_diag veth macvlan xt_nat xt_tcpudp 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 i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper kvm drm_kms_helper drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel btusb sha512_ssse3 mei_hdcp mei_pxp aesni_intel btrtl crypto_simd i2c_i801 intel_gtt btbcm cryptd gigabyte_wmi wmi_bmof rapl intel_cstate btintel intel_uncore agpgart mei_me i2c_smbus bluetooth joydev input_leds ahci i2c_core led_class r8169 ecdh_generic mei ecc syscopyarea
Dec 11 20:24:07 Knox kernel: libahci realtek sysfillrect sysimgblt thermal fan fb_sys_fops video tpm_crb tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_tad acpi_pad button unix
Dec 11 20:24:07 Knox kernel: CPU: 0 PID: 30043 Comm: kworker/u24:1 Tainted: P           O       6.1.63-Unraid #1
Dec 11 20:24:07 Knox kernel: Hardware name: Gigabyte Technology Co., Ltd. Z690 AORUS ELITE AX DDR4/Z690 AORUS ELITE AX DDR4, BIOS F8 08/08/2022
Dec 11 20:24:07 Knox kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan]
Dec 11 20:24:07 Knox kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
Dec 11 20:24:07 Knox 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
Dec 11 20:24:07 Knox kernel: RSP: 0018:ffffc90000003d98 EFLAGS: 00010202
Dec 11 20:24:07 Knox kernel: RAX: 0000000000000001 RBX: ffff88827038b500 RCX: 2e13383c58d4c10f
Dec 11 20:24:07 Knox kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88827038b500
Dec 11 20:24:07 Knox kernel: RBP: 0000000000000001 R08: 364fefd763bc1edd R09: 780eeea61c40d29b
Dec 11 20:24:07 Knox kernel: R10: 0c0037f45ce1b2ff R11: ffffc90000003d60 R12: ffffffff82a14d00
Dec 11 20:24:07 Knox kernel: R13: 0000000000022dc8 R14: ffff888102769600 R15: 0000000000000000
Dec 11 20:24:07 Knox kernel: FS:  0000000000000000(0000) GS:ffff88889f800000(0000) knlGS:0000000000000000
Dec 11 20:24:07 Knox kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 11 20:24:07 Knox kernel: CR2: 000014f5e5f9a640 CR3: 000000000420a000 CR4: 0000000000750ef0
Dec 11 20:24:07 Knox kernel: PKRU: 55555554
Dec 11 20:24:07 Knox kernel: Call Trace:
Dec 11 20:24:07 Knox kernel: <IRQ>
Dec 11 20:24:07 Knox kernel: ? __warn+0xab/0x122
Dec 11 20:24:07 Knox kernel: ? report_bug+0x109/0x17e
Dec 11 20:24:07 Knox kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
Dec 11 20:24:07 Knox kernel: ? handle_bug+0x41/0x6f
Dec 11 20:24:07 Knox kernel: ? exc_invalid_op+0x13/0x60
Dec 11 20:24:07 Knox kernel: ? asm_exc_invalid_op+0x16/0x20
Dec 11 20:24:07 Knox kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
Dec 11 20:24:07 Knox kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack]
Dec 11 20:24:07 Knox kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat]
Dec 11 20:24:07 Knox kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
Dec 11 20:24:07 Knox kernel: nf_hook_slow+0x3a/0x96
Dec 11 20:24:07 Knox kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Dec 11 20:24:07 Knox kernel: NF_HOOK.constprop.0+0x79/0xd9
Dec 11 20:24:07 Knox kernel: ? ip_protocol_deliver_rcu+0x164/0x164
Dec 11 20:24:07 Knox kernel: __netif_receive_skb_one_core+0x77/0x9c
Dec 11 20:24:07 Knox kernel: process_backlog+0x8c/0x116
Dec 11 20:24:07 Knox kernel: __napi_poll.constprop.0+0x28/0x124
Dec 11 20:24:07 Knox kernel: net_rx_action+0x159/0x24f
Dec 11 20:24:07 Knox kernel: __do_softirq+0x126/0x288
Dec 11 20:24:07 Knox kernel: do_softirq+0x7f/0xab
Dec 11 20:24:07 Knox kernel: </IRQ>
Dec 11 20:24:07 Knox kernel: <TASK>
Dec 11 20:24:07 Knox kernel: __local_bh_enable_ip+0x4c/0x6b
Dec 11 20:24:07 Knox kernel: netif_rx+0x52/0x5a
Dec 11 20:24:07 Knox kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 11 20:24:07 Knox kernel: ? _raw_spin_unlock+0x14/0x29
Dec 11 20:24:07 Knox kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Dec 11 20:24:07 Knox kernel: process_one_work+0x1a8/0x295
Dec 11 20:24:07 Knox kernel: worker_thread+0x18b/0x244
Dec 11 20:24:07 Knox kernel: ? rescuer_thread+0x281/0x281
Dec 11 20:24:07 Knox kernel: kthread+0xe4/0xef
Dec 11 20:24:07 Knox kernel: ? kthread_complete_and_exit+0x1b/0x1b
Dec 11 20:24:07 Knox kernel: ret_from_fork+0x1f/0x30
Dec 11 20:24:07 Knox kernel: </TASK>
Dec 11 20:24:07 Knox kernel: ---[ end trace 0000000000000000 ]---
Dec 11 21:58:23 Knox kernel: mdcmd (38): check resume
Dec 11 21:58:23 Knox kernel: md: recovery thread: check P ...

 

knox-diagnostics-20231211-2206.zip

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.

hmm... I have been using ipvlan

Something was still using macvlan, it can happen if you didn't reboot after the change.

 

Post the output of

docker network ls