From: Andre Tomt <andre@tomt.net>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Eric Dumazet <edumazet@google.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev <netdev@vger.kernel.org>,
rossi.f@inwind.it, Dimitris Michailidis <dmichail@google.com>
Subject: Re: Fw: [Bug 201423] New: eth0: hw csum failure
Date: Tue, 30 Oct 2018 11:58:38 +0100 [thread overview]
Message-ID: <869fbb53-a0a5-95f9-2c77-c3ae3f6d181f@tomt.net> (raw)
In-Reply-To: <91545596-f932-8834-f613-feda3edc9b84@tomt.net>
On 27.10.2018 23:41, Andre Tomt 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.
>
> Just hit it on the simpler server; no VRF, no tunnels, no nat/conntrack.
> Only a basic stateless nftables ruleset and a vlan netdev (unlikely to
> be the one triggering this I guess; it has only v4 traffic).
I'm currently testing 4.19 with the recomended commit added, plus these
to sort out some GRO issues (on a hunch, unsure if related):
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=a8305bff685252e80b7c60f4f5e7dd2e63e38218
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=992cba7e276d438ac8b0a8c17b147b37c8c286f7
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=ece23711dd956cd5053c9cb03e9fe0668f9c8894
and I *think* it is behaving better now? it's not conclusive as it could
take a while to trip in this environment but some of the test servers
have not shown anything bad in almost 24h.
next prev parent reply other threads:[~2018-10-30 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 15:15 Fw: [Bug 201423] New: eth0: hw csum failure Stephen Hemminger
2018-10-15 15:41 ` Eric Dumazet
2018-10-15 16:12 ` Dave Stevenson
2018-10-15 16:21 ` Stephen Hemminger
2018-10-15 22:28 ` Fw: " Fabio Rossi
2018-10-16 6:30 ` Andre Tomt
2018-10-16 13:00 ` Eric Dumazet
2018-10-19 21:58 ` Eric Dumazet
2018-10-19 22:25 ` Eric Dumazet
2018-10-21 13:34 ` Andre Tomt
2018-10-24 19:41 ` Andre Tomt
2018-10-25 17:38 ` Eric Dumazet
2018-10-26 11:45 ` Andre Tomt
2018-10-26 12:38 ` Andre Tomt
2018-10-26 12:59 ` Eric Dumazet
2018-10-26 13:17 ` Andre Tomt
2018-10-27 21:41 ` Andre Tomt
2018-10-30 10:58 ` Andre Tomt [this message]
2018-10-30 11:04 ` Andre Tomt
2018-10-31 4:08 ` Andre Tomt
2018-11-04 5:43 ` Andre Tomt
2018-10-31 0:25 ` Fabio Rossi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=869fbb53-a0a5-95f9-2c77-c3ae3f6d181f@tomt.net \
--to=andre@tomt.net \
--cc=dmichail@google.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rossi.f@inwind.it \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.