Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1057790: linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode

20 views
Skip to first unread message

Timo van Roermund

unread,
Dec 8, 2023, 10:30:04 AM12/8/23
to
Package: linux-image-6.5.0-5-amd64
Version: linux-image-6.5.0-5-amd64
Severity: important

Dear Maintainer,

My RTL8125 NIC stoped working after upgrading the kernel (linux-image-amd64) from version 6.5.10+1 to 6.5.13+1.

More specifically, the previous kernel that this meta package depends on (package linux-image-6.5.0-4-amd64) worked fine; but the new dependency (linux-image-6.5.0-5-amd64) causes my NIC to stop working.

I found this upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=218187

And I can confirm that I'm also using a jumbo MTU (9000 bytes).

The issue has been fixed in kernel 6.6.5:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/realtek?h=v6.6.5&id=a9ef897677f957401842e45f2006167cdf757ee4

But I'm not sure if kernel 6.5.x will still receive a fix, as it's EOL.

I added below two snippets from the syslog, illustrating the issue.

Cheers, Timo

---

NIC working correctly with kernel version 6.5.10 (Debian linux-image-6.5.0-4-amd64):
====================================================================================

kernel: [ 0.000000] Linux version 6.5.0-4-amd64 (debian...@lists.debian.org) (gcc-13 (Debian 13.2.0-6) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1 (2023-11-03)
(...)
kernel: [ 0.664766] r8169 0000:01:00.0: enabling device (0000 -> 0003)
kernel: [ 0.664885] r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
kernel: [ 0.684835] r8169 0000:01:00.0 eth0: RTL8125A, 00:8e:25:70:01:42, XID 609, IRQ 126
kernel: [ 0.684838] r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
kernel: [ 0.687592] r8169 0000:01:00.0 lan1: renamed from eth0
kernel: [ 7.581712] r8169 0000:01:00.0: firmware: direct-loading firmware rtl_nic/rtl8125a-3.fw
kernel: [ 7.607571] RTL8226 2.5Gbps PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
kernel: [ 7.767905] r8169 0000:01:00.0 lan1: Link is Down
kernel: [ 10.175613] r8169 0000:01:00.0 lan1: Link is Up - 2.5Gbps/Full - flow control off

NIC stops working with kernel version 6.5.13 (Debian linux-image-6.5.0-5-amd64):
================================================================================

kernel: [ 0.000000] Linux version 6.5.0-5-amd64 (debian...@lists.debian.org) (gcc-13 (Debian 13.2.0-7) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 (2023-11-29)
(...)
kernel: [ 0.683111] r8169 0000:01:00.0: enabling device (0000 -> 0003)
kernel: [ 0.683212] r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
kernel: [ 0.701390] r8169 0000:01:00.0 eth0: RTL8125A, 00:8e:25:70:01:42, XID 609, IRQ 125
kernel: [ 0.701392] r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
kernel: [ 0.704404] r8169 0000:01:00.0 lan1: renamed from eth0
kernel: [ 7.473392] r8169 0000:01:00.0: firmware: direct-loading firmware rtl_nic/rtl8125a-3.fw
kernel: [ 7.499525] RTL8226 2.5Gbps PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
kernel: [ 242.686979] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 242.687002] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 363.528597] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 363.528620] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 484.363011] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 484.363034] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 605.190516] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 605.190538] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 726.019534] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 726.019556] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 846.848552] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 846.848576] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 967.677539] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 967.677562] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 1088.506682] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 1088.506705] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 1209.335864] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 1209.335887] r8169_phylink_handler+0x5b/0x240 [r8169]
kernel: [ 1330.165165] rtl_reset_work+0x1bd/0x3b0 [r8169]
kernel: [ 1330.165188] r8169_phylink_handler+0x5b/0x240 [r8169]

Diederik de Haas

unread,
Dec 8, 2023, 12:00:04 PM12/8/23
to
Control: reassign -1 src:linux 6.5.13-1
Control: fixed-upstream

On Friday, 8 December 2023 16:10:50 CET Timo van Roermund wrote:
> Package: linux-image-6.5.0-5-amd64
> Version: linux-image-6.5.0-5-amd64
> Severity: important
>
> My RTL8125 NIC stoped working after upgrading the kernel (linux-image-amd64)
> from version 6.5.10+1 to 6.5.13+1.
>
> The issue has been fixed in kernel 6.6.5:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/driv
> ers/net/ethernet/realtek?h=v6.6.5&id=a9ef897677f957401842e45f2006167cdf757ee
> 4
>
> But I'm not sure if kernel 6.5.x will still receive a fix, as it's EOL.

Upstream won't. There might be a Debian backport, but I don't expect it.
An update to 6.6.5 is already present in Debian kernel's git repo and that or
a later 6.6 version should be released to Experimental or Unstable at some
point, but AFAIK it's not known yet when and where.
signature.asc

Salvatore Bonaccorso

unread,
Dec 8, 2023, 12:00:04 PM12/8/23
to
Hi,

On Fri, Dec 08, 2023 at 04:10:50PM +0100, Timo van Roermund wrote:
> Package: linux-image-6.5.0-5-amd64
> Version: linux-image-6.5.0-5-amd64
> Severity: important
>
> Dear Maintainer,
>
> My RTL8125 NIC stoped working after upgrading the kernel (linux-image-amd64) from version 6.5.10+1 to 6.5.13+1.
>
> More specifically, the previous kernel that this meta package depends on (package linux-image-6.5.0-4-amd64) worked fine; but the new dependency (linux-image-6.5.0-5-amd64) causes my NIC to stop working.
>
> I found this upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=218187
>
> And I can confirm that I'm also using a jumbo MTU (9000 bytes).
>
> The issue has been fixed in kernel 6.6.5:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/realtek?h=v6.6.5&id=a9ef897677f957401842e45f2006167cdf757ee4

Should that be 59d395ed606d ("r8169: fix deadlock on RTL8125 in jumbo
mtu mode")?

Regards,
Salvatore

Debian Bug Tracking System

unread,
Dec 8, 2023, 12:00:04 PM12/8/23
to
Processing control commands:

> reassign -1 src:linux 6.5.13-1
Bug #1057790 [src:linux] linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode
Ignoring request to reassign bug #1057790 to the same package
Bug #1057790 [src:linux] linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode
No longer marked as found in versions linux/6.1.64-1.
> fixed-upstream
Unknown command or malformed arguments to command.


--
1057790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Timo van Roermund

unread,
Dec 8, 2023, 1:20:03 PM12/8/23
to

Salvatore Bonaccorso

unread,
Dec 8, 2023, 2:40:05 PM12/8/23
to
Hi Timo,

On Fri, Dec 08, 2023 at 07:02:45PM +0100, Timo van Roermund wrote:
> Yes, you're right, my mistake. It should be that one:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/realtek?h=v6.6.5&id=fbe43b7f02a2b578d547cec93dbca81e94c0dbb5

Thanks for confirming!

Diederik has added a bug closer for the next upload in experimental in
our packaging repo.

Regards,
Salvatore

Debian Bug Tracking System

unread,
Dec 9, 2023, 1:10:04 PM12/9/23
to
Your message dated Sat, 09 Dec 2023 17:56:32 +0000
with message-id <E1rC1Z2-...@fasolo.debian.org>
and subject line Bug#1057790: fixed in linux 6.1.66-1
has caused the Debian Bug report #1057790,
regarding linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)

Debian Bug Tracking System

unread,
Dec 20, 2023, 8:10:05 AM12/20/23
to
Your message dated Wed, 20 Dec 2023 13:00:10 +0000
with message-id <E1rFwBG-...@fasolo.debian.org>
and subject line Bug#1057790: fixed in linux 6.6.7-1~exp1
0 new messages