From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: Latest net-next kernel 4.19.0+ Date: Tue, 30 Oct 2018 10:50:10 -0700 Message-ID: <473bee73-b40e-2038-35e2-2c03482f7b75@gmail.com> References: <59d5657c-ea0a-7b64-d5ff-5b55eb4fcccf@itcare.pl> <1e954663-ed05-4f33-4384-db880844f9d1@gmail.com> <68f25a28-b79e-d3ae-6eef-50c354ad63ae@gmail.com> <76dfbbda-d7f1-b13a-5921-c12c3b0f8e3e@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: =?UTF-8?Q?Pawe=c5=82_Staszewski?= , dmichail@google.com, Linux Kernel Network Developers To: Cong Wang Return-path: Received: from mail-pf1-f182.google.com ([209.85.210.182]:37499 "EHLO mail-pf1-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727771AbeJaCoj (ORCPT ); Tue, 30 Oct 2018 22:44:39 -0400 Received: by mail-pf1-f182.google.com with SMTP id u13-v6so602878pfm.4 for ; Tue, 30 Oct 2018 10:50:13 -0700 (PDT) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 10/30/2018 10:32 AM, Cong Wang wrote: > Unlike Pawel's case, we don't use vlan at all, maybe this is why we see > it much less frequently than Pawel. > > Also, it is probably not specific to mlx5, as there is another report which > is probably a non-mlx5 driver. Not sure if you provided a stack trace ? Have you tried IPv6 frags maybe ?