July 1, 20215 yr Hey everyone. Back again for this issue thats been driving me crazy. Seem to have random freezing and thought it was ram and ran memtest for a few days. Bought new ram and tested it as well, still no errors. Was having some read errors (the ones that point to cables) and swapped those out and those stopped as well! Thats when I started watching it and leaving the log open. I noticed a bunch of macvlan errors and read into that, there seems to be something with br0 that when you put a static IP caused an issue? So I created a vlan and that issue seemed to have gone away, until today. I hit plex and realized that it may have been a common denominator when these freezes happened. Sure enough I see another macvlan call trace come up. I'm at a loss now. I miss my stableness can anyone help? Jul 1 11:22:13 barkbox kernel: ------------[ cut here ]------------ Jul 1 11:22:13 barkbox kernel: WARNING: CPU: 2 PID: 32425 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Jul 1 11:22:13 barkbox kernel: Modules linked in: nvidia_uvm(PO) xt_nat xt_tcpudp veth md4 sha512_ssse3 sha512_generic cmac cifs libarc4 macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd lockd grace sunrpc md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper drm backlight agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) jc42 ip6table_filter ip6_tables iptable_filter ip_tables x_tables mlx4_en mlx4_core igb i2c_algo_bit e1000e intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas glue_helper i2c_i801 raid_class input_leds intel_cstate i2c_smbus scsi_transport_sas i7core_edac i2c_core led_class ata_piix intel_uncore ipmi_si button acpi_cpufreq [last unloaded: mlx4_core] Jul 1 11:22:13 barkbox kernel: CPU: 2 PID: 32425 Comm: kworker/2:0 Tainted: P O 5.10.28-Unraid #1 Jul 1 11:22:13 barkbox kernel: Hardware name: Cirrascale VB1325/GA-7TESM , BIOS F8l 07/18/2011 Jul 1 11:22:13 barkbox kernel: Workqueue: events macvlan_process_broadcast [macvlan] Jul 1 11:22:13 barkbox kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Jul 1 11:22:13 barkbox kernel: Code: e8 dc f8 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 36 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 6d f3 ff ff e8 35 f5 ff ff e9 22 01 Jul 1 11:22:13 barkbox kernel: RSP: 0018:ffffc900032b8d38 EFLAGS: 00010202 Jul 1 11:22:13 barkbox kernel: RAX: 0000000000000188 RBX: 0000000000000039 RCX: 000000009c9ef3dd Jul 1 11:22:13 barkbox kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffa02f1e24 Jul 1 11:22:13 barkbox kernel: RBP: ffff8881cbbb4280 R08: 000000009bb7e272 R09: ffff888242015140 Jul 1 11:22:13 barkbox kernel: R10: 0000000000000000 R11: ffff88826e5f0400 R12: 0000000000006709 Jul 1 11:22:13 barkbox kernel: R13: ffffffff8210b440 R14: 0000000000000039 R15: 0000000000000000 Jul 1 11:22:13 barkbox kernel: FS: 0000000000000000(0000) GS:ffff888237a80000(0000) knlGS:0000000000000000 Jul 1 11:22:13 barkbox kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 1 11:22:13 barkbox kernel: CR2: 000000c000721000 CR3: 000000000200a006 CR4: 00000000000206e0 Jul 1 11:22:13 barkbox kernel: Call Trace: Jul 1 11:22:13 barkbox kernel: <IRQ> Jul 1 11:22:13 barkbox kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Jul 1 11:22:13 barkbox kernel: nf_hook_slow+0x39/0x8e Jul 1 11:22:13 barkbox kernel: nf_hook.constprop.0+0xb1/0xd8 Jul 1 11:22:13 barkbox kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe Jul 1 11:22:13 barkbox kernel: ip_local_deliver+0x49/0x75 Jul 1 11:22:13 barkbox kernel: ip_sabotage_in+0x43/0x4d [br_netfilter] Jul 1 11:22:13 barkbox kernel: nf_hook_slow+0x39/0x8e Jul 1 11:22:13 barkbox kernel: nf_hook.constprop.0+0xb1/0xd8 Jul 1 11:22:13 barkbox kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 Jul 1 11:22:13 barkbox kernel: ip_rcv+0x41/0x61 Jul 1 11:22:13 barkbox kernel: __netif_receive_skb_one_core+0x74/0x95 Jul 1 11:22:13 barkbox kernel: process_backlog+0xa3/0x13b Jul 1 11:22:13 barkbox kernel: net_rx_action+0xf4/0x29d Jul 1 11:22:13 barkbox kernel: __do_softirq+0xc4/0x1c2 Jul 1 11:22:13 barkbox kernel: asm_call_irq_on_stack+0x12/0x20 Jul 1 11:22:13 barkbox kernel: </IRQ> Jul 1 11:22:13 barkbox kernel: do_softirq_own_stack+0x2c/0x39 Jul 1 11:22:13 barkbox kernel: do_softirq+0x3a/0x44 Jul 1 11:22:13 barkbox kernel: netif_rx_ni+0x1c/0x22 Jul 1 11:22:13 barkbox kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jul 1 11:22:13 barkbox kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Jul 1 11:22:13 barkbox kernel: process_one_work+0x13c/0x1d5 Jul 1 11:22:13 barkbox kernel: worker_thread+0x18b/0x22f Jul 1 11:22:13 barkbox kernel: ? process_scheduled_works+0x27/0x27 Jul 1 11:22:13 barkbox kernel: kthread+0xe5/0xea Jul 1 11:22:13 barkbox kernel: ? __kthread_bind_mask+0x57/0x57 Jul 1 11:22:13 barkbox kernel: ret_from_fork+0x22/0x30 Jul 1 11:22:13 barkbox kernel: ---[ end trace 09633e9089da0fe1 ]--- barkbox-diagnostics-20210701-1306.zip
July 1, 20215 yr Community Expert Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
July 1, 20215 yr Author 11 minutes ago, JorgeB said: Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ I took care of that and changed it to br0.5 on a separate subnet and vlan. maybe that still didnt fix it?
July 1, 20215 yr Community Expert 10 minutes ago, SeveNx7 said: maybe that still didnt fix it? Not if you're still having macvlan/br_netfilter call traces.
Archived
This topic is now archived and is closed to further replies.