[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026012758-dedicate-desecrate-358a@gregkh>
Date: Tue, 27 Jan 2026 14:04:09 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ivan <kernvirt@...il.com>
Cc: linux-usb@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [BUG] r8152: Tx timeout and xHCI setup device timeout. RTL8153
31.00
On Tue, Jan 27, 2026 at 03:36:44PM +0300, Ivan wrote:
> Hello
> I am reporting a persistent hardware hang issue with the r8152 driver
> on an Ryzen 5 7520u (Mendocino) using a usb type c hub.
>
> The Ethernet connection can drop at any time. After the connection
> fails, the Ethernet adapter itself disappears from the system, but the
> other USB devices in the hub continue to work.
> USB_QUIRK_NO_LPM (0x400) is enabled by default, but it doesn't help.
>
> Environment:
> CPU: Ryzen 5 7520u (Mendocino)
> Kernel: 6.18.6 (arch linux), 6.12 lts (gentoo)
> Ethernet chip: rtl8153 0bda:8153, bcdDevice 31.00
>
> I have attached the relevant journalctl logs and the lsusb -vd for this device
There's no timing in the log, so it's a bit hard to determine this, but
it looks like the device is locking up and there's nothing we can do
about it from the kernel side:
asus kernel: r8152 4-1.1:1.0 enp3s0f4u1u1: carrier on
asus kernel: r8152-cfgselector 4-1.1: Failed to read 4 bytes at 0xe820/0x0133 (-110)
asus kernel: xhci_hcd 0000:03:00.4: Timeout while waiting for setup device command
asus kernel: r8152 4-1.1:1.0 enp3s0f4u1u1: NETDEV WATCHDOG: CPU: 4: transmit queue 0 timed out 6129 ms
asus kernel: r8152 4-1.1:1.0 enp3s0f4u1u1: Tx timeout
asus kernel: xhci_hcd 0000:03:00.4: Timeout while waiting for setup device command
asus kernel: r8152-cfgselector 4-1.1: device not accepting address 4, error -62
asus kernel: r8152 4-1.1:1.0 enp3s0f4u1u1: Get ether addr fail
asus kernel: r8152-cfgselector 4-1.1: USB disconnect, device number 4
So perhaps the chip itself is the problem?
sorry it's a bit hard to determine what is really happening here but it
seems like a flaky device. Is it overheating?
thanks,
greg k-h
Powered by blists - more mailing lists