On 03/25/2018 07:45 PM, Robin Laing wrote:
Network controller is:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 0c)
Kernel modules: r8169
That's the right driver. One thing you could try is after removing the
module, try "modprobe r8169 debug=n" where n is a number up to 16. That
will give you more debugging info in the log. Careful, 16 might really
spam the log, so maybe start at 8 and work your way up.
Start of open lid from suspend
Mar 25 21:33:45 xx NetworkManager: <info> [1522013625.9934]
device (enp4s0): state change: unmanaged -> unavailable (reason
'managed', internal state 'managed')
Mar 25 21:33:45 xx kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is
Mar 25 21:33:46 xx kernel: r8169 0000:04:00.0 enp4s0: link down
Mar 25 21:33:46 xx kernel: IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is
The driver is saying that there is no link detected. Are the lights on?
What does "ethtool enp4s0" tell you?
Mar 26 01:07:55 xx ModemManager: <info> Couldn't
for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0': not
supported by any plugin
This one looks like your network card, but you don't want ModemManager
doing anything with it anyway.
Looking further into the log files, I don't seen any mention of
before March 17 when I tried to make a change to the boot parameters
from something I found on the net which was almost a month after the
I would suggest removing this.
My guess, given that reloading the driver makes it work again, is that
after resume, the driver is not turning some part of the chipset back
on. Maybe the interrupts are getting turned back on.
Mar 26 01:07:55 xx kernel: do_IRQ: 7.33 No irq handler for vector
What does "grep r8169 /proc/interrupts" give you when the interface is
working? Try it a couple of times and see how the numbers change. Then
when it's not working try it again a few times and see if the numbers
are still changing.