my nuc5i3ryh runs as a HTPC with kodi and vdr. It automatically goes to sleep (S3) when there's no activity. It either wakes up by timer, IR remote, WOL or simply the power button. The IP is static on the wired interface and wifi is disabled.
For a long time now I have an annoying issue: randomly the network is not working after resume. Sometimes it's every time, sometimes just every second time and sometimes it just works smoothly for days. Here's what I tried so far without improvement:
- Keep the BIOS updated
- Change the router
- Change the cable
- Try 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; now it runs Debian Stretch)
- Reload network adapter and whole network stack on resume
This is how the system logs, when the interfaces fires up correctly:
Sep 14 19:40:31 nuc5i3ryh kernel: e1000e: EEE TX LPI TIMER: 00000011
Sep 14 19:40:31 nuc5i3ryh kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI
Sep 14 19:40:31 nuc5i3ryh kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI
Sep 14 19:40:34 nuc5i3ryh kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
And without network:
Sep 15 11:55:22 nuc5i3ryh kernel: e1000e: EEE TX LPI TIMER: 00000011
Sep 15 11:55:22 nuc5i3ryh kernel: e1000e 0000:00:19.0: System wakeup enabled by ACPI
Sep 15 11:55:22 nuc5i3ryh kernel: e1000e 0000:00:19.0: System wakeup disabled by ACPI
Sep 15 11:55:25 nuc5i3ryh kernel: e1000e: enp0s25 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx
Sep 15 11:55:25 nuc5i3ryh kernel: e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
To me it very much looks like a hardware issue but I'm not willing to spend money on a new nuc while this one is running well (except for the standby).
Does the issue look familiar to you? Is there anything else I can try?
First of all, Intel does not validate the operation of Linux on the NUC products and thus can only provide limited support for Linux issues. It is recommended that you check for more-recent updates to the ethernet driver and that you (also) query the folks in the Linux forums for help.
To me (speaking in generalities), this sounds like, on occasion, the state of the hardware is not being restored properly. Since I have seen no reports of similar issues with Windows, I doubt it is a hardware issue and I doubt it is a BIOS issue -- but you should ensure you have the very latest version installed.
Sorry I don't have a better answer. You can wait until Monday for the Intel Customer Support agents to come online (though I doubt they will have a better answer) and perhaps someone with experience correcting this specific issue will respond.