Call Trace - Assistance Required

Party? No Party? Server is up and working even though this was discovered:

Aug 24 20:45:50 Brahms1 kernel: ------------[ cut here ]------------
Aug 24 20:45:50 Brahms1 kernel: WARNING: CPU: 1 PID: 12 at net/core/skbuff.c:4177 skb_try_coalesce+0x22c/0x338()
Aug 24 20:45:50 Brahms1 kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ipmi_devintf bonding mlx4_en vxlan udp_tunnel coretemp mpt3sas kvm_intel kvm mlx4_core raid_class scsi_transport_sas igb ata_piix ptp pps_core i2c_algo_bit i2c_core ipmi_si acpi_cpufreq
Aug 24 20:45:50 Brahms1 kernel: CPU: 1 PID: 12 Comm: ksoftirqd/1 Not tainted 4.4.30-unRAID #2
Aug 24 20:45:50 Brahms1 kernel: Hardware name: HP ProLiant DL580 G7, BIOS P65 05/23/2011
Aug 24 20:45:50 Brahms1 kernel: 0000000000000000 ffff8814223079e8 ffffffff8136f79f 0000000000000000
Aug 24 20:45:50 Brahms1 kernel: 0000000000001051 ffff881422307a20 ffffffff8104a4ab ffffffff8152f85e
Aug 24 20:45:50 Brahms1 kernel: ffff88141f72a700 ffff88016922f500 00000000000004c0 ffff881422307a8c
Aug 24 20:45:50 Brahms1 kernel: Call Trace:
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8152f85e>] ? skb_try_coalesce+0x22c/0x338
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8104a568>] warn_slowpath_null+0x15/0x17
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8152f85e>] skb_try_coalesce+0x22c/0x338
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81597820>] tcp_try_coalesce+0x38/0x97
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81597cd0>] tcp_queue_rcv+0x5c/0x101
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8159bccc>] tcp_rcv_established+0x4d4/0x5e5
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff815a2ded>] tcp_v4_do_rcv+0x98/0x1c8
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff815a52b9>] tcp_v4_rcv+0x733/0xad1
Aug 24 20:45:50 Brahms1 kernel: [<ffffffffa1700213>] ? ipv4_confirm+0x7a/0xd0 [nf_conntrack_ipv4]
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81586da8>] ip_local_deliver_finish+0xf4/0x1c3
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff815872c3>] ip_local_deliver+0xae/0xb7
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81586cb4>] ? inet_del_offload+0x40/0x40
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81587110>] ip_rcv_finish+0x299/0x2a2
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8158759d>] ip_rcv+0x2d1/0x32f
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81586e77>] ? ip_local_deliver_finish+0x1c3/0x1c3
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8153c6cf>] __netif_receive_skb_core+0x5a5/0x644
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8106cb8b>] ? update_curr+0x7d/0xc6
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8106d584>] ? dequeue_entity+0x69b/0x775
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8153cc2f>] __netif_receive_skb+0x13/0x55
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8153d98e>] process_backlog+0xac/0x143
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8153d794>] net_rx_action+0xd8/0x226
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8104d6d3>] __do_softirq+0xc3/0x1b6
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8104d7e1>] run_ksoftirqd+0x1b/0x3c
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81061e6c>] smpboot_thread_fn+0x16c/0x1ac
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81061d00>] ? sort_range+0x1d/0x1d
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8105fb24>] kthread+0xcd/0xd5
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8105fa57>] ? kthread_worker_fn+0x137/0x137
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff81629f7f>] ret_from_fork+0x3f/0x70
Aug 24 20:45:50 Brahms1 kernel: [<ffffffff8105fa57>] ? kthread_worker_fn+0x137/0x137
Aug 24 20:45:50 Brahms1 kernel: ---[ end trace 76fc64584775246d ]---

If I remember correctly, I was playing around with duplicity yesterday doing a test backup to another local server about the time this appears.

Much appreciated.

--edit--

appears I've had similar before on different server hardware. But the common denominator I think is the mellanox card. could that be the problem?

brahms1-diagnostics-20170825-1117.zip

Edited August 25, 20178 yr by 1812