regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bernhard Hampel-Waffenthal <bernhard.hampelw@posteo.at>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org,
	regressions@lists.linux.dev, Jakub Kicinski <kuba@kernel.org>
Subject: [REGRESSION] r8169: RTL8168h "transmit queue 0 timed out" after ASPM L1 enablement
Date: Wed,  8 Jun 2022 00:44:15 +0000	[thread overview]
Message-ID: <9ebb43ee-52a1-c77d-d609-ca447a32f3e6@posteo.at> (raw)

#regzbot introduced: 4b5f82f6aaef3fa95cce52deb8510f55ddda6a71

Hi,

since the last major kernel version upgrade to 5.18 on Arch Linux I'm 
unable to get a usable ethernet connection on my desktop PC.

I can see a timeout in the logs

 > kernel: NETDEV WATCHDOG: enp37s0 (r8169): transmit queue 0 timed out

and regular very likely related errors after

 > kernel: r8169 0000:25:00.0 enp37s0: rtl_rxtx_empty_cond == 0 (loop: 
42, delay: 100).


The link does manage to go up at nominal full 1Gbps speed, but there is 
no usable connection to speak of and pings are very bursty and take 
multiple seconds.

I was able to pinpoint that the problems were introduced in commit 
4b5f82f6aaef3fa95cce52deb8510f55ddda6a71 with the enablement of ASPM 
L1/L1.1 for ">= RTL_GIGA_MAC_VER_45", which my chip falls under. Adding 
pcie_aspm=off the kernel command line or changing that check to ">= 
RTL_GIGA_MAC_VER_60" for testing purposes and recompiling the kernel 
fixes my problems.


I'm using a MSI B450I GAMING PLUS AC motherboard with a RTL8168h chip as 
per dmesg:

 > r8169 0000:25:00.0 eth0: RTL8168h/8111h, 30:9c:23:de:97:a9, XID 541, 
IRQ 101

lspci says:

 > 25:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] 
(rev 15)
         Subsystem: Micro-Star International Co., Ltd. [MSI] Device 
[1462:7a40]
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx+
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
         Latency: 0, Cache Line Size: 64 bytes
         Interrupt: pin A routed to IRQ 30
         IOMMU group: 14
         Region 0: I/O ports at f000 [size=256]
         Region 2: Memory at fcb04000 (64-bit, non-prefetchable) [size=4K]
         Region 4: Memory at fcb00000 (64-bit, non-prefetchable) [size=16K]
         Capabilities: <access denied>
         Kernel driver in use: r8169
         Kernel modules: r8169


If you need more info I'll do my best to provide what I can, hope that 
helps already.

Regards,
Bernhard

             reply	other threads:[~2022-06-08  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  0:44 Bernhard Hampel-Waffenthal [this message]
2022-06-08  7:30 ` [REGRESSION] r8169: RTL8168h "transmit queue 0 timed out" after ASPM L1 enablement Heiner Kallweit
2022-06-20  6:40   ` Thorsten Leemhuis
2022-07-04 10:56     ` [REGRESSION] r8169: RTL8168h "transmit queue 0 timed out" after ASPM L1 enablement #forregzbot Thorsten Leemhuis
2022-06-08 13:19 ` [REGRESSION] r8169: RTL8168h "transmit queue 0 timed out" after ASPM L1 enablement Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ebb43ee-52a1-c77d-d609-ca447a32f3e6@posteo.at \
    --to=bernhard.hampelw@posteo.at \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).