Comment 34 for bug 1760073

Revision history for this message
Florian W. (florian-will) wrote :

Since updating to bionic, I notice the same symptoms (network not working after suspend).

I'm adding this comment to note that this makes my network come up again, I'll try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in https://ubuntuforums.org/showthread.php?t=2386503 )

My journalctl looks a very little bit different, but I guess it's simply because we don't use exactly the same mainboards, so the IRQs differ:

Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6262] manager: sleep: wake requested (sleeping: yes enabled: yes)
Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6263] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Apr 28 11:00:17 flo-desktop kernel: r8169 0000:02:00.0 eth0: link down
Apr 28 11:00:17 flo-desktop kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6566] manager: NetworkManager state is now DISCONNECTED
Apr 28 11:00:20 flo-desktop ModemManager[693]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:0a.0/0000:02:00.0': not supported by any plugin
Apr 28 11:00:20 flo-desktop kernel: do_IRQ: 3.36 No irq handler for vector