Re: [PATCH] wifi: rtw88: extend USB TX report timeout to RTL8822BU

[Bitterblue Smith <rtl8821cerfe2@gmail.com>]

On 06/11/2026 13:01, Barak Pearlmutter wrote:
> I can confirm the "failed to get tx report from firmware" issue on an
> RTL8822BU USB adapter and provide additional context about its impact.
> 
> Device:
>   RTL88x2bu AC1200 USB WiFi adapter
>   USB ID: 0bda:b812
>   Driver: rtw88_8822bu (in-tree)
>   Firmware: version 30.20.0, H2C version 14
>   Kernel: 7.2.15+deb14-amd64 (Debian 13 / linux-image-amd64)
>   Note: this is a Debian-patched kernel; Debian-specific patches may be
>   relevant, though the rtw88 driver is unlikely to be heavily patched.
> 
> Symptoms observed:
> 
> 1. Slow-fire mode (possibly normal operation): "failed to get tx report
>    from firmware" appears roughly every 5 minutes during extended idle
>    periods.  The link remains associated but throughput degrades.
> 
> 2. Rapid-fire mode (fatal): The message appears multiple times per
>    second.  The interface deauthenticates and does not recover without a
>    USB reset of the device.
> 
> The rapid-fire mode is frequently triggered indirectly by a companion
> Realtek Bluetooth adapter (0bda:a725, RTL8761BU) on the same host
> entering its own failure loop after USB autosuspend (see separate report
> to linux-bluetooth).  When the BT device is in a 2-second USB reset
> storm, the WiFi "failed to get tx report" messages begin within seconds
> and escalate to rapid-fire within ~20 minutes.
> 
> Workarounds currently applied:
>   - USB autosuspend disabled for 0bda:b812:
>       ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda",
>         ATTRS{idProduct}=="b812", ATTR{power/autosuspend}="-1"
>   - WiFi PSM disabled on interface up:
>       ACTION=="add", SUBSYSTEM=="net", ATTRS{idVendor}=="0bda",
>         ATTRS{idProduct}=="b812", RUN+="/usr/sbin/iw dev %k set power_save off"
> 
> These reduce but do not eliminate the slow-fire messages.  Extending the
> TX report timeout as proposed in the referenced patch would address the
> root cause.
> 

That's doubtful. It would just hide or delay the messages. I think what
you are experiencing is caused by this chip's USB 3 problem:

https://lore.kernel.org/linux-wireless/b69f6496-dc12-4662-84ac-aa62d0ceac3f@gmail.com/

It will work better in a USB 2 port.

> Relevant log excerpt (slow-fire, link still up):
> 
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   [~5 minutes pass]
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   [repeat]
> 
> Relevant log excerpt (rapid-fire leading to deauth):
> 
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   kernel: rtw88_8822bu 4-5:1.0: failed to get tx report from firmware
>   kernel: wlx1cbfceb2abdb: deauthenticating from cc:2d:21:70:11:fd by local choice (Reason: 3=DEAUTH_LEAVING)
>   kernel: usb 4-5: reset SuperSpeed USB device number 3 using xhci_hcd
>   kernel: rtw88_8822bu 4-5:1.0: Firmware version 30.20.0, H2C version 14
>   [reconnects after USB reset]
> 
> Happy to test a patched kernel or provide further information.
> 

An equivalent patch made it into kernel 7.4, so you can test that if
you want.

> Barak Pearlmutter <barak@cs.nuim.ie>