Hi Jim. Here’s a kernel regression report that is likely impacting you here…
Thanks, Deano - I’ll check that out.
Is the module loaded?
lsmod | grep -i r816
If no r8169
grep -i 'blacklist r8169' /etc/modprobe.d/*
Yes, the module is loaded. Best to read the thread from the start for a complete picture.
Yeah, it’s definitely the r8169 regression. I just reconfigured to use r8168, and after a couple of reboots and forcing the card to use the 8168 module (and disabling my wifi interface), it’s working again.
Thanks for the assist, everyone. Appreciated.
Good stuff!
Do we have a Realtek revision issue?
- For Jim, the revision of the RTL8111/8168/8411 controller is ‘0c’ – r8168 is OK …
- On this system, the revision of the RTL8111/8168/8411 controller is ‘15’ – r8169 is OK …
r8169 is the driver builtin the kernel.
r8168 is the original driver from the realtek side.
As I already mentioned back in post #20
Could you perhaps explain how you managed to do this? I am struck by the same issue today (on tumbleweed, since snapshot of 21-11). At least, I think I am, see:
~] dmesg|tail
1950.981474] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1956.101341] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1961.989715] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1967.109372] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1972.997226] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1988.101234] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1993.989184] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
1999.109179] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
2004.997116] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
2014.980936] r8169 0000:04:00.0 enp4s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
~]
I tried to install this package, but somehow it fails:
Software installation Installation was only partially successful.
The following packages could not be installed
- r8168
I think YaST only managed to add the repositories.
Problem is fixed! Not sure how though. Went back to a older snapshot (17-11), which didn’t solve the problem (neither did booting with a different kernel, by the way) - so I thought I’d run the update again. And then it just worked?