Arch Linux

amhairghin

Member

Registered: 2015-10-14

Posts: 79

Network issues with kernel 7

The truth is, I can't tell you exactly which kernel version is causing the problem or why it's happening—I only know what the symptoms are and that it's clearly related to Kernel 7, which has been giving us a series of rather interesting “surprises” lately.

The thing is, I'm working away quietly on my computer (an AMD) when suddenly I lose my network connection—nothing responds at all. About a minute after it happens, if I go to the journal, I see this appear:

sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5440 ms
sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: ASPM disabled on Tx timeout
sep 12 12:06:46 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
sep 12 12:06:52 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5777 ms
sep 12 12:07:08 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5681 ms
sep 12 12:07:14 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 14: transmit queue 0 timed out 5399 ms
sep 12 12:07:20 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 11: transmit queue 0 timed out 5693 ms
sep 12 12:07:26 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 1: transmit queue 0 timed out 5492 ms
sep 12 12:07:26 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
sep 12 12:07:58 hell kernel: r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 9: transmit queue 0 timed out 5784 ms
sep 12 12:07:58 hell kernel: r8169 0000:0e:00.0 enp14s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

At that point, the only thing left for me to do is restart. There is (as far as I know) no way to recover the network.

This doesn't happen to me all the time; it's completely random. It might happen shortly after I start up the computer, or I might go days without it crashing. The only thing I know for sure is that this is a problem with Kernel version 7.

Anyway, I'm just leaving this here to let you know that if this happens to anyone else, you're not alone, my friend.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,776

Re: Network issues with kernel 7

From posts here and some proxmox blog this is likely driven by the bus or power management - have you looked at the unfiltered journal for contextual issues?

https://bbs.archlinux.org/viewtopic.php?id=279589&p=2
https://zlendy.com/blog/psa-tuned-in-proxmox-ve

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

amhairghin

Member

Registered: 2015-10-14

Posts: 79

Re: Network issues with kernel 7

Yeah, that was the first thing I checked. The power management settings are the first thing you disable to avoid these problems, but it doesn't help, every now and then, it still catches you off guard.

Well, the card is an RTL8125, so the logical thing to do would probably be to use the r8125-dkms package from the AUR, but the fact is that the kernel's own r8169 driver has always worked well and hasn't caused any problems. I don't know, in the end, I think if it keeps getting on my nerves, I'll just switch to the LTS kernel and be done with it.

robertnino

Member

Registered: Yesterday

Posts: 1

Re: Network issues with kernel 7

Got the same issue.  Mobo is GA-AB350M-DS3H V2 with onboard Realtek LAN (don't know the exact version, kernel says RTL8168g/8111g)

Sep 13 16:03:20 ra kernel: r8169 0000:05:00.0 enp5s0: NETDEV WATCHDOG: CPU: 8: transmit queue 0 timed out 5440 ms
Sep 13 16:03:20 ra kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Sep 13 16:03:26 ra kernel: r8169 0000:05:00.0 enp5s0: NETDEV WATCHDOG: CPU: 9: transmit queue 0 timed out 5230 ms
Sep 13 16:03:26 ra kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Sep 13 16:03:32 ra kernel: r8169 0000:05:00.0 enp5s0: NETDEV WATCHDOG: CPU: 12: transmit queue 0 timed out 6125 ms
Sep 13 16:03:32 ra kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Sep 13 16:04:27 ra kernel: r8169 0000:05:00.0 enp5s0: NETDEV WATCHDOG: CPU: 13: transmit queue 0 timed out 5027 ms
Sep 13 16:04:27 ra kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Sep 13 16:05:31 ra kernel: r8169 0000:05:00.0 enp5s0: NETDEV WATCHDOG: CPU: 6: transmit queue 0 timed out 5375 ms
Sep 13 16:05:31 ra kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

Tried kernel cmd line parameter pcie_aspm=off but the symptoms persisted.
Funny thing is that the issue starts right after boot.

Downgraded to 7.1.5-arch1-2 and I got the network back.

With 7.2.x I get the above issue and no network.

loqs

Member

Registered: 2014-03-06

Posts: 19,060

Re: Network issues with kernel 7

Do all three of the following kernels have the issue:

pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-7.2-1-x86_64.pkg.tar.zst
pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-7.2rc1-1-x86_64.pkg.tar.zst
pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-7.3rc2-1-x86_64.pkg.tar.zst