From: Vincas Dargis <vindrg@gmail.com>
To: netdev@vger.kernel.org
Subject: About r8169 regression 5.4
Date: Fri, 14 Feb 2020 19:21:30 +0200 [thread overview]
Message-ID: <b46d29d8-faf6-351e-0d9f-a4d4c043a54c@gmail.com> (raw)
Hi,
I've found similar issue I have myself since 5.4 on mailing list archive [0], for this device:
05:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
It works fine as long as I select 5.3 in Grub (it seems no longer maintained in Debian Sid though...)
I see number of commits in net/etherenet/realtek tree, not sure if fix is there, or do we need
another fix for this particular device? I've keep testing latest Debian kernel updates (latest is
5.4.19-1), and no good news yet.
There's Debian bug report [1] which might contain more information.
Some extra info:
$ sudo ethtool -i enp5s0f1
driver: r8169
version:
firmware-version: rtl8411-2_0.0.1 07/08/13
expansion-rom-version:
bus-info: 0000:05:00.1
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
$ sudo mii-tool -v enp5s0f1
enp5s0f1: negotiated 1000baseT-FD flow-control, link ok
product info: vendor 00:07:32, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
[0] https://lkml.org/lkml/2019/11/30/119
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947685
next reply other threads:[~2020-02-14 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:21 Vincas Dargis [this message]
2020-02-14 20:14 ` About r8169 regression 5.4 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
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=b46d29d8-faf6-351e-0d9f-a4d4c043a54c@gmail.com \
--to=vindrg@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).