Hi,

i have see that i have these Call Trace Errors since the last days. It is Spamming all 20 Seconds in the LOG. Someone knows what is this or i can do?

 

 

My Hardware:

Intel S2600CP2

E5-2620 V2

2 x 16GB DDR3 ECC RAM

Mellanox-ConnectX-3 SFP+

 

 

Mar 26 10:42:43 Sven-NAS kernel: eth0: hw csum failure
Mar 26 10:42:43 Sven-NAS kernel: CPU: 2 PID: 0 Comm: swapper/2 Tainted: P           O      4.19.24-Unraid #1
Mar 26 10:42:43 Sven-NAS kernel: Hardware name: Intel Corporation S2600CP/S2600CP, BIOS SE5C600.86B.02.06.0007.082420181029 08/24/2018
Mar 26 10:42:43 Sven-NAS kernel: Call Trace:
Mar 26 10:42:43 Sven-NAS kernel: <IRQ>
Mar 26 10:42:43 Sven-NAS kernel: dump_stack+0x5d/0x79
Mar 26 10:42:43 Sven-NAS kernel: __skb_checksum_complete+0x5d/0xa7
Mar 26 10:42:43 Sven-NAS kernel: igmp_rcv+0x138/0x685
Mar 26 10:42:43 Sven-NAS kernel: ip_local_deliver_finish+0x101/0x1aa
Mar 26 10:42:43 Sven-NAS kernel: ip_local_deliver+0xb9/0xd5
Mar 26 10:42:43 Sven-NAS kernel: ? ip_sublist_rcv_finish+0x53/0x53
Mar 26 10:42:43 Sven-NAS kernel: ip_rcv+0x9e/0xbc
Mar 26 10:42:43 Sven-NAS kernel: ? ip_rcv_finish_core.isra.0+0x2e6/0x2e6
Mar 26 10:42:43 Sven-NAS kernel: __netif_receive_skb_one_core+0x4d/0x69
Mar 26 10:42:43 Sven-NAS kernel: netif_receive_skb_internal+0x9f/0xba
Mar 26 10:42:43 Sven-NAS kernel: napi_gro_frags+0x153/0x18b
Mar 26 10:42:43 Sven-NAS kernel: mlx4_en_process_rx_cq+0x7e7/0x950 [mlx4_en]
Mar 26 10:42:43 Sven-NAS kernel: ? mlx4_cq_completion+0x1e/0x63 [mlx4_core]
Mar 26 10:42:43 Sven-NAS kernel: ? mlx4_en_rx_irq+0x23/0x3e [mlx4_en]
Mar 26 10:42:43 Sven-NAS kernel: ? mlx4_eq_int+0xb2a/0xb55 [mlx4_core]
Mar 26 10:42:43 Sven-NAS kernel: mlx4_en_poll_rx_cq+0x66/0xc6 [mlx4_en]
Mar 26 10:42:43 Sven-NAS kernel: net_rx_action+0x10b/0x274
Mar 26 10:42:43 Sven-NAS kernel: __do_softirq+0xce/0x1e2
Mar 26 10:42:43 Sven-NAS kernel: irq_exit+0x5e/0x9d
Mar 26 10:42:43 Sven-NAS kernel: do_IRQ+0xa9/0xc7
Mar 26 10:42:43 Sven-NAS kernel: common_interrupt+0xf/0xf
Mar 26 10:42:43 Sven-NAS kernel: </IRQ>
Mar 26 10:42:43 Sven-NAS kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141
Mar 26 10:42:43 Sven-NAS kernel: Code: ff 45 84 ff 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 a4 4e be ff fb 66 0f 1f 44 00 00 <48> 2b 1c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cb
Mar 26 10:42:43 Sven-NAS kernel: RSP: 0018:ffffc9000328bea0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc
Mar 26 10:42:43 Sven-NAS kernel: RAX: ffff88881daa0b00 RBX: 000038b4794f3c4a RCX: 000000000000001f
Mar 26 10:42:43 Sven-NAS kernel: RDX: 000038b4794f3c4a RSI: 000000003d196a7c RDI: 0000000000000000
Mar 26 10:42:43 Sven-NAS kernel: RBP: ffff88881daab300 R08: 0000000000000002 R09: 00000000000203c0
Mar 26 10:42:43 Sven-NAS kernel: R10: 00000000005ed6e8 R11: 00026820c620f166 R12: 0000000000000004
Mar 26 10:42:43 Sven-NAS kernel: R13: 0000000000000004 R14: ffffffff81e58e58 R15: 0000000000000000
Mar 26 10:42:43 Sven-NAS kernel: do_idle+0x192/0x20e
Mar 26 10:42:43 Sven-NAS kernel: cpu_startup_entry+0x6a/0x6c
Mar 26 10:42:43 Sven-NAS kernel: start_secondary+0x197/0x1b2
Mar 26 10:42:43 Sven-NAS kernel: secondary_startup_64+0xa4/0xb0

Edited March 26, 20197 yr by DrAg0n141

Push

Best to post up a Diagnostics file opposed to just cut and paste of a section of your log. 

Tools, diagnostics, download, attach zip file here.

Now the diagnostic files.

sven-nas-diagnostics-20190328-0734.zip

An Idea? I have reset Bios to default and still have this Problem.

The errors appear to be related to the Mellanox NIC, you could try setting one of the onboard NICs as et0 and Mellanox as eth1 or eth2, if not possible I would reset the network config and start over with as simple  config as possible.

How can i reset the network config?

delete /boot/network.cfg and /boot/network-rules.cfg and reboot.

Dont have an network-rules.cfg is this ok?

yes

Ok have delete the network.cfg and reboot, the errors stay.

Try with another NIC as eth0

I have tested it with another NIC the errors stop, and have replaced the Gbic and put the Mellanox in another PCIE slot. I think the Mellanox is defective.

2 minutes ago, DrAg0n141 said:

I think the Mellanox is defective.

It's possible, I have some ConnectX-2 and X-3 and they all work fine with Unraid

After reinstall unRAID completely the errors are gone. i think one of the plugins produce the many errors.