There's a regression in 5.3 for some cards supported by the e1000e driver: https://bugzilla.kernel.org/show_bug.cgi?id=205047 I have a number of boxes affected by this that stop working with the 5.3 kernels. From the bug, it's not clear to me if this was fixed in 5.4, but it might not have been.
Hello. I make some experiments with this - this bug appear after upgrade kernel in Fedora-31 from 5.3.16-300.fc31.x86_64 to 5.4.x Connection continously start/reset with this messages: янв 26 15:54:08 Host1 kded5[3837]: plasma-nm: Unhandled active connection state change: 1 янв 26 15:54:08 Host1 kded5[3837]: plasma-nm: Unhandled active connection state change: 1 янв 26 15:54:14 Host1 NetworkManager[949]: <info> [1580043254.5138] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') янв 26 15:54:14 Host1 NetworkManager[949]: <info> [1580043254.5282] dhcp4 (enp0s31f6): canceled DHCP transaction янв 26 15:54:14 Host1 NetworkManager[949]: <info> [1580043254.5283] dhcp4 (enp0s31f6): state changed unknown -> done янв 26 15:54:14 Host1 NetworkManager[949]: <info> [1580043254.5315] manager: NetworkManager state is now DISCONNECTED янв 26 15:54:15 Host1 kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0662] device (enp0s31f6): carrier: link connected янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0665] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0671] policy: auto-activating connection 'Onboard_LAN' (708b2b50-68f3-4413-9167-b85dc5741983) янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0677] device (enp0s31f6): Activation: starting connection 'Onboard_LAN' (708b2b50-68f3-4413-9167-b85dc5741983) янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0678] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.0682] manager: NetworkManager state is now CONNECTING янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.1550] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.1575] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') янв 26 15:54:15 Host1 NetworkManager[949]: <info> [1580043255.1585] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) янв 26 15:54:15 Host1 kded5[3837]: plasma-nm: Unhandled active connection state change: 1 Switching from DHCP to static-config don't affect - connection continue resetting; Switching "auto-negotiation" option to "off" can help, also force setting link-speed to 1Gbps/HalfDuplex can help to make connection; But this connection can not survive/reopen after reboot; Sleeping in RAM-standby mode and waking up made connection drop to 10mbps and i detect "TxError" errors on switch port (DGS-1100-10ME): TX OutOctets 193115544851 OutUcastPkts 501851548 OutNUcastPkts 676615 OutErrors 51788 LateCollisions 51788 ExcessiveCollisions 0 In normal state Errors / Collisions not detected on switch interface even under load about 700-800 Mbps. This bug not all motherboards/NIC appear ! - My Asus STRIX H270F GAMING with bios version 1205 from release date: 05/11/2018 and NIC "Intel Corporation Ethernet Connection (2) I219-V" affected - only in 5.4.14-200 i can start network after setting "Half-Duplex" in connection properties; - Another PC with MB "ASUS P8P67 EVO" bios version: 3602 release date: 11/01/2012 and NIC "Intel Corporation 82579V Gigabit Network Connection (rev 05)" network work correctly without tweaks with same e1000e driver. Kernel 5.3.16 work ideal with both MB/NIC.
The bug is present in all 5.4 kernels, a fix was never backported. The fix is in 5.5, which should appear in Fedora in a month or so, if past performance is an indicator.
Hmm, i make update to 5.4.17 and this solve my problem - link stay established in auto-negotiation-mode, no disconnections; This related to deep hardware features ? In 5.5 kernel version this bug will be fully eliminated ?
According to the upstream kernel logs the fix for this is in 5.4.18 as well. Not sure why 5.4.17 would work, but glad that it does.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.