Bug 1787187

Summary: E1000e Networking issue with Kernel-5.4.5-300.fc31.x86_64
Product: [Fedora] Fedora Reporter: Ryan <stealthcipher>
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: 31CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-01 05:10:32 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 Ryan 2020-01-01 05:07:04 UTC
1. Please describe the problem:
Unable to establish network connection after upgrade to kernel 5.4.5-300 (x86_64) from updates-testing

2. What is the Version-Release number of the kernel:
5.4.5-300.fc31.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
This was working fine in 5.3.16

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Install kernel 5.4.5-300 on my pc

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
unsure...not tried

6. Are you running any modules that not shipped with directly Fedora's kernel?:
no

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Jan 01 10:44:34 kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
Jan 01 10:44:34 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c8:60:00:e0:c2:44
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
Jan 01 10:44:34 kernel: e1000e 0000:00:19.0 eno1: renamed from eth0
Jan 01 10:44:40 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:45:30 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:45:30 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Jan 01 10:45:36 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:45:43 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:45:50 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:45:56 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:46:03 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:46:10 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 01 10:46:17 kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

Comment 1 Ryan 2020-01-01 05:10:32 UTC

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