System: Linux Mint 19.1 Kernel: 4.15.0-58 Network interface 1: Intel 82579V, connected locally to another machine with a null-modem cable, 1Gb/s Network interface 2: Intel 82574L on motherboard, connected via FritzBox 7490 to outside world via VDSL This interface (interface 1) functioned perfectly from the installation of Mint 19.1 with several 4.15 kernels up to yesterday, when the system was updated from 4.15.0-55 to 4.15.0-58 (among other updates). With this kernel the interface alternates between up and down states within seconds. inxi -i: Device-1: Intel 82579V Gigabit Network driver: e1000e IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 10:bf:48:7d:5f:d2 IP v4: 172.16.0.11/24 type: noprefixroute scope: global lspci: 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04) Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 35 Region 0: Memory at f7c00000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f7c39000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at f080 [size=32] Capabilities: <access denied> Kernel driver in use: e1000e Kernel modules: e1000e Both kernel 4.15.0-55 and 4.15.0-58 use the same version of e1000e: version 3.2.6-k Reverting to kernel 4.15.0-55 restores the correct working of the interface.
I have the same problem. After update to 4.15.0-58 on XUbuntu 18.04 my Thinkpad P50 can no longer establish a connection. The interface continuously alternates between up and down. If I revert to an older kernel, the network connection works again. kern.log contains multiple "sent link down event" and "sent link up event" events in a short timeframe: [snip] Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: up Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: attached Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent link down event. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent link up event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: detached Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent link down event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent link up event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: up Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: attached Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent link down event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent link up event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: detached Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent link down event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent link up event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: up Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: attached Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent link down event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent link up event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: detached Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent link down event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent link up event. Aug 20 10:06:20 martijn-ThinkPad-P50 kernel: [ 2447.583182] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [snip] The up-down cycle continues indefinitely
My laptop has a different controller but uses the same driver e1000e inxi -i: Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e lspci: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
Looks like this was already fixed in the mainline kernel. For Ubuntu the fix will be included with Kernel 4.15.0-60.67 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841148