Call Traces - eventual crashing


Urbanpixels

Recommended Posts

Good morning. 

 

I have an installation which has been running for around 2 months. Ever since creating it i've had call traces in some form or other. Usually Macvlan but now I'm not sure what is causing it.

 

I had separate dockers on static IP's using VLAN's and still had these issues even though the big Macvlan thread says to use VLAN's

 

Now I've moved everything to Bridge without static IP's (Other than my Pihole Docker, which is still VLAN) and im still getting call traces. Im starting to wonder if its from something else but i don't understand enough to decipher the call trace. 

 

Can anybody help? I've attached diagnostics too.

 

Sep 29 19:42:13 Radiant-Unraid kernel: WARNING: CPU: 2 PID: 0 at net/netfilter/nf_conntrack_core.c:945 __nf_conntrack_confirm+0xa0/0x69e Sep 29 19:42:13 Radiant-Unraid kernel: Modules linked in: macvlan tun xt_nat veth nvidia_uvm(O) ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) edac_mce_amd crc32_pclmul pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd drm_kms_helper drm kvm_amd kvm syscopyarea sysfillrect sysimgblt fb_sys_fops mpt3sas rsnvme(PO) agpgart i2c_piix4 ccp i2c_core raid_class atlantic scsi_transport_sas nvme ahci mxm_wmi wmi_bmof crct10dif_pclmul nvme_core libahci pcc_cpufreq crc32c_intel wmi button acpi_cpufreq Sep 29 19:42:13 Radiant-Unraid kernel: CPU: 2 PID: 0 Comm: swapper/2 Tainted: P O 4.19.107-Unraid #1 Sep 29 19:42:13 Radiant-Unraid kernel: Hardware name: System manufacturer System Product Name/ROG CROSSHAIR VII HERO, BIOS 3103 06/17/2020 Sep 29 19:42:13 Radiant-Unraid kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x69e Sep 29 19:42:13 Radiant-Unraid 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 95 f1 ff ff be 00 02 00 00 48 Sep 29 19:42:13 Radiant-Unraid kernel: RSP: 0018:ffff8887fe6838e8 EFLAGS: 00010202 Sep 29 19:42:13 Radiant-Unraid kernel: RAX: 0000000000000188 RBX: ffff8887f80aeb00 RCX: ffff88833490ce18 Sep 29 19:42:13 Radiant-Unraid kernel: RDX: 0000000000000001 RSI: 0000000000000133 RDI: ffffffff81e093a4 Sep 29 19:42:13 Radiant-Unraid kernel: RBP: ffff88833490cdc0 R08: 000000008cfd706e R09: ffffffff81c8aa80 Sep 29 19:42:13 Radiant-Unraid kernel: R10: 0000000000000158 R11: ffffffff81e91080 R12: 0000000000003d33 Sep 29 19:42:13 Radiant-Unraid kernel: R13: ffffffff81e91080 R14: 0000000000000000 R15: 000000000000f769 Sep 29 19:42:13 Radiant-Unraid kernel: FS: 0000000000000000(0000) GS:ffff8887fe680000(0000) knlGS:0000000000000000 Sep 29 19:42:13 Radiant-Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 29 19:42:13 Radiant-Unraid kernel: CR2: 0000559a1bdefca8 CR3: 00000007a3ef0000 CR4: 0000000000340ee0 Sep 29 19:42:13 Radiant-Unraid kernel: Call Trace: Sep 29 19:42:13 Radiant-Unraid kernel: <IRQ> Sep 29 19:42:13 Radiant-Unraid kernel: ipv4_confirm+0xaf/0xb9 Sep 29 19:42:13 Radiant-Unraid kernel: nf_hook_slow+0x3a/0x90 Sep 29 19:42:13 Radiant-Unraid kernel: ip_local_deliver+0xad/0xdc Sep 29 19:42:13 Radiant-Unraid kernel: ? ip_sublist_rcv_finish+0x54/0x54 Sep 29 19:42:13 Radiant-Unraid kernel: ip_sabotage_in+0x38/0x3e Sep 29 19:42:13 Radiant-Unraid kernel: nf_hook_slow+0x3a/0x90 Sep 29 19:42:13 Radiant-Unraid kernel: ip_rcv+0x8e/0xbe Sep 29 19:42:13 Radiant-Unraid kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1 Sep 29 19:42:13 Radiant-Unraid kernel: __netif_receive_skb_one_core+0x53/0x6f Sep 29 19:42:13 Radiant-Unraid kernel: netif_receive_skb_internal+0x79/0x94 Sep 29 19:42:13 Radiant-Unraid kernel: br_pass_frame_up+0x128/0x14a Sep 29 19:42:13 Radiant-Unraid kernel: ? br_flood+0xa4/0x148 Sep 29 19:42:13 Radiant-Unraid kernel: ? br_fdb_update+0x56/0x13d Sep 29 19:42:13 Radiant-Unraid kernel: br_handle_frame_finish+0x342/0x383 Sep 29 19:42:13 Radiant-Unraid kernel: ? br_pass_frame_up+0x14a/0x14a Sep 29 19:42:13 Radiant-Unraid kernel: br_nf_hook_thresh+0xa3/0xc3 Sep 29 19:42:13 Radiant-Unraid kernel: ? br_pass_frame_up+0x14a/0x14a Sep 29 19:42:13 Radiant-Unraid kernel: br_nf_pre_routing_finish+0x24a/0x271 Sep 29 19:42:13 Radiant-Unraid kernel: ? br_pass_frame_up+0x14a/0x14a Sep 29 19:42:13 Radiant-Unraid kernel: ? br_handle_local_finish+0xe/0xe Sep 29 19:42:13 Radiant-Unraid kernel: ? nf_nat_ipv4_in+0x1e/0x62 [nf_nat_ipv4] Sep 29 19:42:13 Radiant-Unraid kernel: ? br_handle_local_finish+0xe/0xe Sep 29 19:42:13 Radiant-Unraid kernel: br_nf_pre_routing+0x31c/0x343 Sep 29 19:42:13 Radiant-Unraid kernel: ? br_nf_forward_ip+0x362/0x362 Sep 29 19:42:13 Radiant-Unraid kernel: nf_hook_slow+0x3a/0x90 Sep 29 19:42:13 Radiant-Unraid kernel: br_handle_frame+0x27e/0x2bd Sep 29 19:42:13 Radiant-Unraid kernel: ? br_pass_frame_up+0x14a/0x14a Sep 29 19:42:13 Radiant-Unraid kernel: __netif_receive_skb_core+0x4a7/0x7b1 Sep 29 19:42:13 Radiant-Unraid kernel: ? inet_gro_receive+0x246/0x254 Sep 29 19:42:13 Radiant-Unraid kernel: __netif_receive_skb_one_core+0x35/0x6f Sep 29 19:42:13 Radiant-Unraid kernel: netif_receive_skb_internal+0x79/0x94 Sep 29 19:42:13 Radiant-Unraid kernel: napi_gro_receive+0x44/0x7b Sep 29 19:42:13 Radiant-Unraid kernel: aq_ring_rx_clean+0x32d/0x35b [atlantic] Sep 29 19:42:13 Radiant-Unraid kernel: ? hw_atl_b0_hw_ring_rx_receive+0x12b/0x1f7 [atlantic] Sep 29 19:42:13 Radiant-Unraid kernel: aq_vec_poll+0xf2/0x180 [atlantic] Sep 29 19:42:13 Radiant-Unraid kernel: net_rx_action+0x107/0x26c Sep 29 19:42:13 Radiant-Unraid kernel: __do_softirq+0xc9/0x1d7 Sep 29 19:42:13 Radiant-Unraid kernel: irq_exit+0x5e/0x9d Sep 29 19:42:13 Radiant-Unraid kernel: do_IRQ+0xb2/0xd0 Sep 29 19:42:13 Radiant-Unraid kernel: common_interrupt+0xf/0xf Sep 29 19:42:13 Radiant-Unraid kernel: </IRQ> Sep 29 19:42:13 Radiant-Unraid kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141 Sep 29 19:42:13 Radiant-Unraid kernel: Code: ff 45 84 f6 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 7a 8d bb ff fb 66 0f 1f 44 00 00 <48> 2b 2c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cd Sep 29 19:42:13 Radiant-Unraid kernel: RSP: 0018:ffffc90003253e98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffd6 Sep 29 19:42:13 Radiant-Unraid kernel: RAX: ffff8887fe69fac0 RBX: ffff8887f6f66c00 RCX: 000000000000001f Sep 29 19:42:13 Radiant-Unraid kernel: RDX: 0000000000000000 RSI: 00000000238e3ad4 RDI: 0000000000000000 Sep 29 19:42:13 Radiant-Unraid kernel: RBP: 00003eb130160966 R08: 00003eb130160966 R09: 0000000000002ecb Sep 29 19:42:13 Radiant-Unraid kernel: R10: 000000002510a978 R11: 071c71c71c71c71c R12: 0000000000000002 Sep 29 19:42:13 Radiant-Unraid kernel: R13: ffffffff81e5e1e0 R14: 0000000000000000 R15: ffffffff81e5e2b8 Sep 29 19:42:13 Radiant-Unraid kernel: ? cpuidle_enter_state+0xbf/0x141 Sep 29 19:42:13 Radiant-Unraid kernel: do_idle+0x17e/0x1fc Sep 29 19:42:13 Radiant-Unraid kernel: cpu_startup_entry+0x6a/0x6c Sep 29 19:42:13 Radiant-Unraid kernel: start_secondary+0x197/0x1b2 Sep 29 19:42:13 Radiant-Unraid kernel: secondary_startup_64+0xa4/0xb0 Sep 29 19:42:13 Radiant-Unraid kernel: ---[ end trace e96b4b447794652c ]---

 

 

radiant-unraid-diagnostics-20200930-1052.zip

Edited by Urbanpixels
Link to comment
6 hours ago, Urbanpixels said:

I had separate dockers on static IP's using VLAN's and still had these issues

Your unraid system is on vlan 130; are your docker containters using a different vlan?  I believe ALL of your containers that have a static IP must be on a different vlan than that of your unraid system.  My understanding for this is because most routers will not route broadcast packets between networks - with the broadcast packets being the cause of the macvlan call traces.

Link to comment

My unraid install was on vlan 150 most of my dockers were on vlan 130

 

I've now made everything onto vlan 130 with br0 and vlan unused. Everything is bridge and I've offloaded piHole to another device.

 

It seems quite silly that we can't apply different IP addresses to different dockers. Sort of negates the whole point? Never had this issue with Freenas.

Edited by Urbanpixels
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.