I have been busy and unable to look at this until today.
On 26/03/18 01:05, Samuel Sieb wrote:
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.
Going to 16 didn't make any difference from 10.
Apr 13 14:03:41 tdllap kernel: r8169 0000:04:00.0: can't disable ASPM;
OS doesn't have ASPM control
Apr 13 14:03:41 tdllap kernel: r8169 0000:04:00.0 eth0: RTL8168g/8111g
at 0x00000000ef2b4190, 40:16:7e:10:e0:9a, XID 0c000880 IRQ 34
Apr 13 14:03:41 tdllap kernel: r8169 0000:04:00.0 eth0: jumbo features
[frames: 9200 bytes, tx checksumming: ko]
Apr 13 14:03:41 tdllap kernel: r8169 0000:04:00.0 enp4s0: renamed from eth0
Apr 13 14:03:41 tdllap kernel: r8169 0000:04:00.0 enp4s0: link down
Apr 13 14:03:44 tdllap kernel: r8169 0000:04:00.0 enp4s0: link up
The driver is saying that there is no link detected. Are the lights on?
What does "ethtool enp4s0" tell you?
Link lights on switch come up when lid closed and opened without
reloading the network driver.
ethtool shows Link detected: no which is interesting.
Looking further into the log files, I don't seen any mention of r1869
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.
This is from /proc/interupts and doesn't change between suspends or
disappear. It is there from boot until I remove the module.
34: 0 0 0 0 125 0
0 175 IR-PCI-MSI 2097152-edge enp4s0
It used to work until February but I don't know what update affected it
as I wasn't told until a few kernel updates that there was an issue.
What I found that is when I load the module, lsmod give me this.
r8169 94208 0
mii 16384 1 r8169
I am going to look more at the mii-tool and see if that has anything to
do with it.
I did find another thread about kernel modules being broken in February
and specifically mentioning r8169 module not reloading on suspend.
users mailing list -- email@example.com
To unsubscribe send an email to users-le...@lists.fedoraproject.org