From: Thomas Voegtle <tv@lio96.de>
To: Heiner Kallweit <hkallweit1@gmail.com>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: network problems with r8169
Date: Thu, 18 Jul 2019 20:50:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1907182032370.7080@er-systems.de> (raw)
Hello,
I'm having network problems with the commits on r8169 since v5.2. There
are ping packet loss, sometimes 100%, sometimes 50%. In the end network is
unusable.
v5.2 is fine, I bisected it down to:
a2928d28643e3c064ff41397281d20c445525032 is the first bad commit
commit a2928d28643e3c064ff41397281d20c445525032
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Sun Jun 2 10:53:49 2019 +0200
r8169: use paged versions of phylib MDIO access functions
Use paged versions of phylib MDIO access functions to simplify
the code.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Reverting that commit on top of v5.2-11564-g22051d9c4a57 fixes the problem
for me (had to adjust the renaming to r8169_main.c).
I have a:
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev
0c)
Subsystem: Biostar Microtech Int'l Corp Device [1565:2400]
Kernel driver in use: r8169
on a BIOSTAR H81MG motherboard.
greetings,
Thomas
next reply other threads:[~2019-07-18 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:50 Thomas Voegtle [this message]
2019-07-19 20:05 ` network problems with r8169 Heiner Kallweit
2019-07-19 21:12 ` Thomas Voegtle
2019-07-20 9:11 ` Heiner Kallweit
2019-07-20 14:22 ` Thomas Voegtle
2019-07-20 16:44 ` Heiner Kallweit
2019-07-20 9:13 ` Heiner Kallweit
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=alpine.LSU.2.21.1907182032370.7080@er-systems.de \
--to=tv@lio96.de \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@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