Bug 1661680

Summary: Realtek Driver Bug
Product: [Fedora] Fedora Reporter: fleabeard <joshuaconley>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 29CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-24 12:03:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description fleabeard 2018-12-22 02:17:02 UTC 
Description of problem:
After installing Fedora 29 and rebooting, my Realtek Ethernet doesn't work and is bridged by virbr0 with no working internet/networking connections.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Install Fedora 29
2. Reboot Computer
3. Wired Ethernet doesn't work. Status of Wired Connection in Network Manager is (unplugged)

Actual results:
Wired Ethernet stops working and is bridged by virbr0. No internet access is available in either. No VM's are used in this bug.

Expected results:
Working wired ethernet.

Additional info:
Using a Realtek onboard NIC
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

The fix is to reload the driver via 'sudo rmmod r8169' & 'modprobe r8169' then everything works as it should.
Comment 1 fleabeard 2018-12-22 02:20:01 UTC 
Forgot to mention kernel version:
Linux localhost.localdomain 4.19.9-300.fc29.x86_64 #1 SMP Thu Dec 13 17:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Comment 2 Hans de Goede 2018-12-24 12:03:29 UTC 
This is a duplicate of bug 1650984, people have been debugging this issue in that bug and hopefully a fix will be available soon (but it is a hard to pin down issue). Please add any further comments you may have to bug 1650984.

*** This bug has been marked as a duplicate of bug 1650984 ***