netdev - RTL8125D intermittent disconnects

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACu1E7GJttr8EDjLxYMBkfkKSK2=ZS7hb4bsYAhqO00bt07QtQ@mail.gmail.com>
Date: Sat, 23 Nov 2024 17:35:00 -0500
From: Connor Abbott <cwabbott0@...il.com>
To: netdev@...r.kernel.org
Cc: Heiner Kallweit <hkallweit1@...il.com>, nic_swsd@...ltek.com
Subject: RTL8125D intermittent disconnects

Hello,

I recently bought a motherboard with a builtin RTL8125D Ethernet chip
(XID 688). I updated linux-firmware to get
/lib/firmware/rtl_nic/rtl8125d-1.fw and tried out the patches enabling
it, and while it mostly works the link intermittently disconnects and
reconnects. It seems to be caused by high bandwidth, since doing a
speed test in the browser seems to be a reliable trigger. There's
nothing interesting in dmesg other than "r8169 0000:06:00.0 enp6s0:
Link is Down":

[   36.133656] r8169 0000:06:00.0 enp6s0: Link is Up - 100Mbps/Full -
flow control rx/tx
[   36.476108] r8169 0000:06:00.0 enp6s0: Link is Down
[   48.507244] r8169 0000:06:00.0 enp6s0: Link is Up - 100Mbps/Full -
flow control rx/tx
[   48.821220] r8169 0000:06:00.0 enp6s0: Link is Down
[   60.947170] r8169 0000:06:00.0 enp6s0: Link is Up - 100Mbps/Full -
flow control rx/tx
...

These are the messages at boot:

[    9.512877] r8169 0000:06:00.0 eth0: RTL8125D, cc:28:aa:a7:bd:85,
XID 688, IRQ 100
[    9.512880] r8169 0000:06:00.0 eth0: jumbo features [frames: 9194
bytes, tx checksumming: ko]
[    9.534565] r8169 0000:06:00.0 enp6s0: renamed from eth0
[   10.716346] Realtek Internal NBASE-T PHY r8169-0-600:00: attached
PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC)

I tried this both on a branch based on 6.11 with enablement patches
and some dependent patches backported, and on recent (today)
netdev/main. This doesn't happen with a USB ethernet dongle I have
laying around, so I don't think it's due to the network or something
else in the stack. Is there anything I can do to help debug?

Best regards,

Connor Abbott