Network adapter doesn't work after returning from suspend

[Gordon Dracup]

Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter does not resume after suspend. Wifi not available.

References to a fix for r8169 driver found. Tried the following fixes:
1. sudo service network-manager restart. This did not work.
2. Script in /lib/systemd/system-sleep/r8169-refresh as described in https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend This did not work.
3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 fixes in version 4.21, but this is not available on the ubuntu mainline kernels https://kernel.ubuntu.com/~kernel-ppa/mainline/

Possibly related to bug #1752772
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-04-08 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: linux (not installed)
Tags: bionic
Uname: Linux 4.20.17-042017-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1824038

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.

[Gordon Dracup (gordon-dracup)]

apport information

[Gordon Dracup (gordon-dracup)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Please reproduce the issue and attach full dmesg.

[Gordon Dracup (gordon-dracup)]

dmesg output as requested

[Kai-Heng Feng (kaihengfeng)]

There are several fixes in upstream r8169 driver, please test mainline kernel:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/

[Gordon Dracup (gordon-dracup)]

1. Removed the r8169-refresh script
2. Rested with 5.1-rc4

Problem still occurs. See updated dmesg log.

[Gordon Dracup (gordon-dracup)]

Sorry, typo. 2. Re-tested with 5.1-rc4. Problem still occurs.

[Kai-Heng Feng (kaihengfeng)]

Ok, please raise the issue to the maintainer and mailing list:
<email address hidden>
<email address hidden>
<email address hidden>

[Gordon Dracup (gordon-dracup)]

Can you tell me how I would do that. I added the first name to the subscription list, but I can't do it with the second two.

[Kai-Heng Feng (kaihengfeng)]

Since Heiner Kallweit has an Launchpad account, let's wait for his reply.

[Heiner Kallweit (kalle1)]

This sounds more like a platform issue (especially as WiFi seems to be affected too). Few months ago we had something similiar and it turned out to be a problem with Intel PCI bridge code.
The only way I see for now is to find a working version and then bisect.

[Kai-Heng Feng (kaihengfeng)]

Looks like it has a Haswell CPU, so older kernels should be able to work on this system.

[Gordon Dracup (gordon-dracup)]

An update on this.

I installed kernel 5.0, but the same issue occured. I did notice that my wi-fi can be re-activated using the keyboard wireless switch (Fn-Wifi). I have 2 wi-fi networks available, the normal one and the 5G one. I had been using the 5G one, but switched to use the normal one. My wi-fi came back up, and resumes ok after being in standby.

I re-booted using the kernel 5.1.rc4, and it works ok as above. I don't remember trying the physical wi-fi function key before, so it is possible it would have worked in the Ubuntu current mainline kernel 4.18, which I will test next.

Could the issue be 5G wifi specific?

[Gordon Dracup (gordon-dracup)]

Confirmed. The same behaviour in the original kernel 4.18.0-17.