On 30.10.2018 12:04, Andre Tomt wrote:
On 30.10.2018 11:58, Andre Tomt wrote:
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.
Sorry, s/some of the/none of the
I think it is fairly safe to say 4.19 + mlx4 + these 4 commits is OK. At
least for my workload. Servers are now 51-61 hours in, no splats. I also
added ntp pool traffic to one of them to make things a little more exciting.
Not sure what is needed for 4.18, I dont have the mental bandwidth to
test that right now. Also no idea about the similar looking mlx5 splats
reported elsewhere.
