From: Norbert Jurkeit <norbert.jurkeit@web.de>
To: nic_swsd@realtek.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: michael.wiktowy@gmail.com, jcline@redhat.com, marc.c.dionne@gmail.com
Subject: Issue with RTL8111 NIC after upgrade to kernel 4.19
Date: Wed, 21 Nov 2018 11:51:02 +0100 [thread overview]
Message-ID: <d0a53002-bf14-6cd9-ab0f-5d3f9aa395ce@web.de> (raw)
Dear Linux developers,
after upgrade from distro kernel 4.18.18 to 4.19.2 some Fedora users
(including me) encounter issues with RTL8111 based Ethernet interfaces.
The interface is not started correctly after boot with kernel 4.19.2
(i.e. is reported by ifconfig as up, but not running, the LEDs besides
the connector stay off and no data is transferred).
At least for me the issue seems to occur only after reboot from a
previous session with kernel 4.18.18, but not after power-on, which
means the hardware is not fully initialized by the new r8169 driver.
Marc Dionne, another affected Fedora user, thinks that module "realtek"
needs to be loaded, which does not happen automatically. Please see
https://bugzilla.redhat.com/show_bug.cgi?id=1650984 for more details.
As Fedora kernel maintainers usually don't apply many changes to the
upstream kernel, users of other distros will likely be affected as well.
We therefore kindly ask you to investigate the issue and fix it in
future upstream kernels.
Many thanks and best regards,
Norbert Jurkeit
next reply other threads:[~2018-11-21 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 10:51 Norbert Jurkeit [this message]
2018-11-21 19:57 ` Issue with RTL8111 NIC after upgrade to kernel 4.19 Heiner Kallweit
2018-11-21 20:20 ` Andrew Lunn
2018-11-21 20:32 ` Heiner Kallweit
2018-11-21 20:49 ` Heiner Kallweit
2018-11-21 20:52 ` Heiner Kallweit
2018-11-21 21:53 ` Marc Dionne
2018-11-21 22:28 ` Heiner Kallweit
2018-11-21 23:13 ` Marc Dionne
2018-11-22 18:17 ` Heiner Kallweit
2018-11-22 18:57 ` Andrew Lunn
2018-11-22 19:48 ` Heiner Kallweit
2018-11-22 19:29 ` Marc Dionne
2018-11-22 19:53 ` 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=d0a53002-bf14-6cd9-ab0f-5d3f9aa395ce@web.de \
--to=norbert.jurkeit@web.de \
--cc=davem@davemloft.net \
--cc=jcline@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.c.dionne@gmail.com \
--cc=michael.wiktowy@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
/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).