From: Vincas Dargis <vindrg@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Salvatore Bonaccorso <carnil@debian.org>
Cc: netdev@vger.kernel.org
Subject: Re: About r8169 regression 5.4
Date: Thu, 27 Feb 2020 20:25:17 +0200 [thread overview]
Message-ID: <cb8114b1-0cd7-3a56-a567-5745aad43793@gmail.com> (raw)
In-Reply-To: <90776f02-5c98-235b-663f-962ad68e1c93@gmail.com>
2020-02-24 21:49, Heiner Kallweit rašė:
> Realtek responded that they can't reproduce the issue. They suggested to not enable tx offloading
> per default as a workaround. So for now you have to disable tx offloading via ethtool.
Thanks for your time Heiner! I'll just keep it like this.
Maybe I reproduce it via some sort of strange setup - multiple different P2P applications, maybe Shorewall firewall confugration set some interesting networking options too..? Anyway, if this hang up
is not universal, I guess it's not worth to disable it by default from kernel side?
next prev parent reply other threads:[~2020-02-27 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:21 About r8169 regression 5.4 Vincas Dargis
2020-02-14 20:14 ` Heiner Kallweit
2020-02-15 9:22 ` Vincas Dargis
2020-02-15 16:12 ` Salvatore Bonaccorso
2020-02-15 21:10 ` Vincas Dargis
2020-02-15 22:07 ` Vincas Dargis
2020-02-15 22:35 ` Heiner Kallweit
2020-02-15 23:27 ` Heiner Kallweit
2020-02-17 18:08 ` Vincas Dargis
2020-02-17 19:59 ` Heiner Kallweit
2020-02-18 18:36 ` Vincas Dargis
2020-02-19 21:54 ` Heiner Kallweit
2020-02-20 17:36 ` Vincas Dargis
2020-02-20 18:32 ` Heiner Kallweit
2020-02-21 20:21 ` Vincas Dargis
2020-02-21 21:01 ` Heiner Kallweit
2020-02-23 13:24 ` Vincas Dargis
2020-02-23 13:27 ` Heiner Kallweit
2020-02-24 19:49 ` Heiner Kallweit
2020-02-27 18:25 ` Vincas Dargis [this message]
2020-04-12 11:56 ` Lauri Jakku
2020-04-12 12:02 ` Lauri Jakku
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=cb8114b1-0cd7-3a56-a567-5745aad43793@gmail.com \
--to=vindrg@gmail.com \
--cc=carnil@debian.org \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).