From: Michal Pecio <michal.pecio@gmail.com>
To: Samuil <samuilsgames@protonmail.com>
Cc: "pkshih@realtek.com" <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: RTW88 USB Wi-Fi Adapter (8822BU) Disconnects and Fails with USB Write Errors - Status -71 & -110
Date: Fri, 17 Oct 2025 20:00:48 +0200 [thread overview]
Message-ID: <20251017200048.6e748dae.michal.pecio@gmail.com> (raw)
In-Reply-To: <7qi-6tBb1frj_rYuHZflT1akP5I6yA2yxTA7Gg8IQBlDIwSqiWx76AFmcirkfHv5VmqQ7CZ4SesZSswoDKzOt3kbgh3MI-4CqEq-RrxHnns=@protonmail.com>
On Fri, 17 Oct 2025 17:25:03 +0000, Samuil wrote:
> > Does it happen every time on every boot?
> The disconnect happens on every boot although rarely the device is
> able to reconnect again. Usually, however, the adapter just stops
> working until I reboot again.
Well, I had no luck reproducing this on v6.18-rc1.
I left it running overnight with ping traffic ~700KB/s each way.
> > May we know what 'lspci -nn' says about this 0000:02:00.0 controller?
> 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller [1022:43d5] (rev 01)
Similar to my B350 chipset.
In some stress tests it showed a HW bug which currently isn't being
worked around by xhci_hcd and I think this bug may be responsible for
at least some of the noise you get, namely this sequence with constant
"event dma" but increasing "TD at":
Event dma 0x0000000105a9e110 for ep 0 status 4 not part of TD at 000000011fd2bd30 - 000000011fd2bd50
Event dma 0x0000000105a9e110 for ep 0 status 4 not part of TD at 000000011fd2bd90 - 000000011fd2bdb0
It's a broken state which rtw88 can't do anything about. The dynamic
debug I asked for may shed some light on how you got into this state.
Whether fixing this would enable rtw88 to continue is unclear, because
everything likely starts with a "Transaction Error" on endpoint 0. That
could either be a one-off error (harmless if xHCI recoveres from it and
rtw88 retries whatever it wanted to do), or the USB device crashes due
to some traffic pattern unique to your network or whatever.
> Are you using a USB 2 port for the adapter to be working properly
> without configuration?
Nope, I made sure to run it SuperSpeed on my buggy AMD chipset.
This is probably unique to your network traffic or hardware (poor
USB link quality? maybe try other ports.)
Still, I would be curious to see this dynamic debug if possible.
Are you able to compile and run a patched kernel?
Regards,
Michal
next prev parent reply other threads:[~2025-10-17 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <zjR8G0R1ZUFe9h8_ibO-LWc9OOJyMThA9jp9ftYbETLG3IN0cHPvhCAaC9ypGKPbapsbzTH5VqnDhFcX93GkwnG1BEyETplFQmRiGGshBz8=@protonmail.com>
2025-10-16 22:59 ` RTW88 USB Wi-Fi Adapter (8822BU) Disconnects and Fails with USB Write Errors - Status -71 & -110 Michal Pecio
2025-10-17 17:25 ` Samuil
2025-10-17 18:00 ` Michal Pecio [this message]
[not found] ` <9d4086b0e8134084a8bb7800db56db2b@realtek.com>
2025-10-17 17:06 ` Samuil
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=20251017200048.6e748dae.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=samuilsgames@protonmail.com \
/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).