Randomly no network connection after resume

Kernels & Hardware, configuring network, installing services

Randomly no network connection after resume

Postby piotrusch » 2018-11-04 12:29

Hi everybody,

for some time (a year or more) now I've been having the issue, that after suspend the PC randomly doesn't have ethernet connection. Randomly in this case means sometimes it happens after every suspend, sometimes after every second and sometimes it just runs flawlessly. The only thing which helps in such cases is a reboot or another suspend.

The system is an Intel NUC5i3ryh with a wired Intel Corporation Ethernet Connection (3) I218-V (rev 03) adapter. Network is configured by systemd-networkd with a static address and the used module is e1000e. It's connected to the router. The system is Debian 9 with some packages from 10. Here are the two different logs, first with not working connection:

Code: Select all
Nov 03 21:07:08 mypc kernel: e1000e: EEE TX LPI TIMER: 00000011
Nov 03 21:07:08 mypc kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI
Nov 03 21:07:08 mypc kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI
Nov 03 21:07:08 mypc kernel: e1000e: enp0s25 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx
Nov 03 21:07:08 mypc kernel: e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO


and second a working one:

Code: Select all
Nov 04 13:08:11 mypc kernel: e1000e: EEE TX LPI TIMER: 00000011
Nov 04 13:08:11 mypc kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI
Nov 04 13:08:11 mypc kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI
Nov 04 13:08:11 mypc kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx


It's been a long way so far with lots of trials but nothing has helped yet:

    Kept the BIOS updated
    Changed the router
    Changed the cable
    Tried different power saving options in the BIOS (PCI related etc.)
    Loaded the network card module (e1000e) with specific option (such as "options e1000e SmartPowerDownEnable=0")
    Changed the linux distro (ubuntu 16.04 to 18.04; recently to Debian)
    Reloaded network adapter and whole network stack on resume

I also tried to shut down the network before suspend and fired it up on resume which, as far as I remember, helped but isn't applicable since WOL doesn't work in this scenario which is needed here.

Unfortunately I ran out of ideas of what to try and where to investigate. Hopefully one of you can point me to the right spot to head on.

Regards, Piotrusch
piotrusch
 
Posts: 1
Joined: 2018-11-04 11:57

Re: Randomly no network connection after resume

Postby Head_on_a_Stick » 2018-11-04 13:10

piotrusch wrote:Network is configured by systemd-networkd with a static address and the used module is e1000e.

Can we please see the .network file, thanks!

piotrusch wrote:The system is Debian 9 with some packages from 10.

^ This means that you have broken your Debian box :(

See https://wiki.debian.org/DontBreakDebian

Probably best to re-install from scratch and try again.

Also, there is no Debian 10 (yet).

piotrusch wrote:Here are the two different logs

Does `journalctl -u systemd-networkd` have anything more to say?

piotrusch wrote:Reloaded network adapter and whole network stack on resume

^ How exactly did you do this?

In respect of WOL, have you tried https://wiki.archlinux.org/index.php/Wake-on-LAN#systemd.link?

FWIW, I use systemd-networkd in Debian buster and the connections resume just fine for me (both wireless & wired).
I suffer from depression and may lash out occasionally, try not to take it personally.
User avatar
Head_on_a_Stick
 
Posts: 8172
Joined: 2014-06-01 17:46
Location: /dev/chair


Return to System configuration

Who is online

Users browsing this forum: No registered users and 6 guests

fashionable