On Fri, Oct 26, 2018 at 5:38 AM Andre Tomt <an...@tomt.net> wrote: > > On 26.10.2018 13:45, Andre Tomt wrote: > > On 25.10.2018 19:38, Eric Dumazet wrote: > >> > >> > >> On 10/24/2018 12:41 PM, Andre Tomt wrote: > >>> > >>> It eventually showed up again with mlx4, on 4.18.16 + fix and also on > >>> 4.19. I still do not have a useful packet capture. > >>> > >>> It is running a torrent client serving up various linux distributions. > >>> > >> > >> Have you also applied this fix ? > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=db4f1be3ca9b0ef7330763d07bf4ace83ad6f913 > >> > >> > > > > No. I've applied it now to 4.19 and will report back if anything shows up. > > And it tripped again with that commit; however on another box with a > much more complicated setup (VRFs, sch_cake, ifb, conntrack/nat, 6in4 > tunnel, VF device on mlx4) > > > [ 8197.348260] wanib: hw csum failure > > [ 8197.348288] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.19.0-1 #1 > > [ 8197.348289] Hardware name: Supermicro SYS-5018D-FN8T/X10SDV-TP8F, BIOS > > 1.3 03/19/2018 > > [ 8197.348290] Call Trace: > > [ 8197.348296] <IRQ> > > [ 8197.348304] dump_stack+0x5c/0x80 > > [ 8197.348308] __skb_checksum_complete+0xac/0xc0 > > [ 8197.348318] icmp_error+0x1c8/0x1f0 [nf_conntrack] > > [ 8197.348325] ? ip_output+0x61/0xc0 > > [ 8197.348328] ? skb_copy_bits+0x13d/0x220 > > [ 8197.348334] nf_conntrack_in+0xd8/0x390 [nf_conntrack] > > [ 8197.348339] ? ___pskb_trim+0x192/0x330 > > [ 8197.348343] nf_hook_slow+0x43/0xc0 > > [ 8197.348346] ip_rcv+0x90/0xb0 > > [ 8197.348349] ? ip_rcv_finish_core.isra.0+0x310/0x310 > > [ 8197.348354] __netif_receive_skb_one_core+0x42/0x50 > > [ 8197.348357] netif_receive_skb_internal+0x24/0xb0 > > [ 8197.348361] ifb_ri_tasklet+0x167/0x260 [ifb] > > [ 8197.348365] tasklet_action_common.isra.3+0x49/0xb0 > > [ 8197.348369] __do_softirq+0xe7/0x2d3 > > [ 8197.348372] irq_exit+0x96/0xd0 > > [ 8197.348375] do_IRQ+0x85/0xd0 > > [ 8197.348378] common_interrupt+0xf/0xf > > [ 8197.348379] </IRQ> > > [ 8197.348382] RIP: 0010:cpuidle_enter_state+0xb9/0x320 > > [ 8197.348384] Code: e8 1c 16 bc ff 80 7c 24 0b 00 74 17 9c 58 0f 1f 44 00 > > 00 f6 c4 02 0f 85 3b 02 00 00 31 ff e8 3e fb c0 ff fb 66 0f 1f 44 00 00 > > <48> b8 ff ff ff ff f3 01 00 00 48 2b 1c 24 ba ff ff ff 7f 48 39 c3 > > [ 8197.348386] RSP: 0018:ffff9f0441953ea8 EFLAGS: 00000246 ORIG_RAX: > > ffffffffffffffd5 > > [ 8197.348388] RAX: ffff9759efae0fc0 RBX: 000007749807d911 RCX: > > 000000000000001f > > [ 8197.348390] RDX: 000007749807d911 RSI: 000000003a2e8670 RDI: > > 0000000000000000 > > [ 8197.348393] RBP: ffff9759efae98a8 R08: 0000000000000002 R09: > > 0000000000020840 > > [ 8197.348396] R10: 00626b4810384abc R11: ffff9759efae01e8 R12: > > 0000000000000001 > > [ 8197.348398] R13: ffffffff8d0ac638 R14: 0000000000000001 R15: > > 0000000000000000 > > [ 8197.348402] ? cpuidle_enter_state+0x94/0x320 > > [ 8197.348407] do_idle+0x1e4/0x220 > > [ 8197.348411] cpu_startup_entry+0x5f/0x70 > > [ 8197.348415] start_secondary+0x185/0x1a0 > > [ 8197.348417] secondary_startup_64+0xa4/0xb0
Very different trace , yet another bug to track . If you can, try to remove some components from this setup.
