You are not logged in.
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.
Offline
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
Offline