Network lost after long sleep

Bug #1872408 reported by moreje
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello,
After a long time in sleep mode, my Desktop running Ubuntu 20.04 loses its network ethernet link.
the demsg shows the following lines after sleep exit:

[10402.613687] PM: suspend exit
[10403.035311] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[10403.121362] ata1.00: configured for UDMA/133
[10403.363882] e1000e: enp0s25 NIC Link is Down
[10406.484276] e1000e: enp0s25 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx
[10406.484281] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
[10406.484322] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready

the ethernet is up but at 10 M / full duplex
DHCP of my router does not give any address.

the only way to retrieve a Full 1000 M functionnal link is to reboot the machine.

Can't determine how much time of sleep it needs to reproduce, since an immediate sleep/wake-up does not produce network loss.

Revision history for this message
moreje (j-redoute) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1872408

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
moreje (j-redoute) wrote :

I can't run the apport-collect command since when the bug is active, I have no network link.

You-Sheng Yang (vicamo)
tags: added: hwe-networking-ethernet
Revision history for this message
You-Sheng Yang (vicamo) wrote :

@moreje, I would suggest you to buy a usb-ethernet dongle as an emergency work-around for such cases.

Revision history for this message
Alex Hung (alexhung) wrote :

@moreje,

Did you try re-initialize the NIC driver with following commands?

sudo modprobe -r e1000e && sudo modprobe e1000e

Revision history for this message
moreje (j-redoute) wrote :

Thank you for the tip! I try and come back to reort later!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.