* wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
@ 2026-03-23 10:58 Jeffrey Wälti
2026-03-24 2:02 ` Ping-Ke Shih
0 siblings, 1 reply; 8+ messages in thread
From: Jeffrey Wälti @ 2026-03-23 10:58 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org; +Cc: pkshih@realtek.com
Hi,
I am experiencing a reproducible HWSI bus lockup on the RTL8922AE
(rtw89_8922ae) triggered by the connected AP changing its advertised
bandwidth in a beacon. During the lockup, the radio is unresponsive and the only fix I could find is reconnecting to the network.
The issue occurs on every boot within seconds of association, and also during normal operation whenever the AP re-advertises its
channel width.
I have tested with both the in-tree driver on kernel 6.19 and the
latest out-of-tree driver from morrownr/rtw89 (git HEAD). Both
reproduce the issue identically.
User-visible impact
-------------------
During the HWSI busy window, all network traffic basically stops. Existing TCP connections stall and time-sensitive applications (VoIP, video calls) break. The Wi-Fi/BT coexistence is also disrupted, causing paired Bluetooth devices to disconnect.
The issue reproduces on every association and also during
runtime when the AP periodically re-advertises its bandwidth (sometimes every few minutes), making connectivity unreliable.
Boot-to-bug dmesg (trimmed to relevant entries)
------------------------------------------------
[ 17.659262] rtw89_8922ae 0000:03:00.0: loaded firmware rtw89/rtw8922a_fw-4.bin
[ 17.659440] rtw89_8922ae 0000:03:00.0: enabling device (0000 -> 0003)
[ 17.666964] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf), cmd version 1, type 1
[ 17.666968] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf), cmd version 1, type 3
[ 17.685115] rtw89_8922ae 0000:03:00.0: chip rfe_type is 1
[ 17.685886] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input24
[ 17.685913] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input25
[ 17.687499] rtw89_8922ae 0000:03:00.0: Firmware version 0.1.0.0 (7b393818), cmd version 0, type 64
[ 17.687504] rtw89_8922ae 0000:03:00.0: Firmware element BB version: 00 49 00 00
[ 17.687511] rtw89_8922ae 0000:03:00.0: Firmware element radio A version: 00 33 00 00
[ 17.687516] rtw89_8922ae 0000:03:00.0: Firmware element NCTL version: 00 0f 00 00
[ 17.687536] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46 00 00
[ 17.687537] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46 00 00
[ 17.687538] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46 00 00
[ 17.687546] rtw89_8922ae 0000:03:00.0: Firmware element PWR_TRK version: 00 33 00 00
[ 17.687550] rtw89_8922ae 0000:03:00.0: Firmware element REGD version: 00 49 00 08
[ 17.691873] rtw89_8922ae 0000:03:00.0: rfkill hardware state changed to enable
[ 18.108033] systemd-journald[808]: Received client request to flush runtime journal.
[ 18.367229] input: keyd virtual keyboard as /devices/virtual/input/input26
[ 18.383013] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.383017] Bluetooth: BNEP filters: protocol multicast
[ 18.383021] Bluetooth: BNEP socket layer initialized
[ 18.410929] input: keyd virtual pointer as /devices/virtual/input/input27
[ 18.464298] Bluetooth: hci0: RTL: fw version 0x41c0c905
[ 18.647322] Bluetooth: hci0: AOSP extensions version v1.00
[ 18.647546] Bluetooth: MGMT ver 1.23
[ 18.655814] NET: Registered PF_ALG protocol family
[ 21.985205] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[ 21.985210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[ 22.001200] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[ 22.001210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[ 22.002893] wlan0: authenticated
[ 22.003792] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
[ 22.005327] wlan0: RX AssocResp from 7c:10:c9:b5:b4:4c (capab=0x1011 status=0 aid=17)
[ 22.111182] wlan0: associated
[ 22.111255] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[ 22.111263] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 7c:10:c9:b5:b4:4c
[ 32.623170] hid-sensor-hub 0020:1022:0001.0004: hidraw3: SENSOR HUB HID v0.00 Device [hid-amdsfh 1022:0001] on pcie_mp2_amd
[ 33.076564] wlan0: AP 7c:10:c9:b5:b4:4c changed bandwidth in beacon, new used config is 5220.000 MHz, width 5 (5250.000/0 MHz)
[ 33.090085] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.102460] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.114775] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.127371] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.141826] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.153783] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.165901] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.178402] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.191675] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.205185] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.217544] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.229788] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.242802] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.257200] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.269858] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.282153] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.295625] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.307822] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.320258] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.332693] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.345004] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.360051] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.373084] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.385703] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.397827] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.411372] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.426744] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.438969] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.451407] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.464456] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.477296] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.489589] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.502064] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[ 33.514235] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[ 33.514249] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[ 34.491697] rfkill: input handler disabled
[ 34.778186] Bluetooth: RFCOMM TTY layer initialized
[ 34.778198] Bluetooth: RFCOMM socket layer initialized
[ 34.778201] Bluetooth: RFCOMM ver 1.11
[ 39.723603] rfkill: input handler enabled
[ 40.871391] rfkill: input handler disabled
[ 41.010414] nvme nvme0: using unchecked data buffer
[ 43.272141] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Environment
-----------
Linux version 6.19.9-1-cachyos (linux-cachyos@cachyos) (clang version 22.1.1, LLD 22.1.1) #1 SMP PREEMPT_DYNAMIC Thu, 19 Mar 2026 20:13:27 +0000
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8922AE 802.11be PCIe Wireless Network Adapter [10ec:8922] (rev 01)
Subsystem: Lenovo Device [17aa:4922]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 112
IOMMU group: 15
Region 0: I/O ports at 2000 [size=256]
Region 2: Memory at 80b00000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: rtw89_8922ae
Kernel modules: rtw89_8922ae
rtw89_8922ae 12288 0
rtw89_8922a 77824 1 rtw89_8922ae
rtw89_pci 131072 1 rtw89_8922ae
rtw89_core 1236992 2 rtw89_8922a,rtw89_pci
mac80211 1806336 2 rtw89_core,rtw89_pci
cfg80211 1523712 3 rtw89_core,rtw89_8922a,mac80211
rfkill 45056 9 rtw89_core,bluetooth,ideapad_laptop,cfg80211
Hardware: Lenovo Yoga 7 2-in-1 14AKP10 (machine type 83JR)
Chip: RTL8922AE (PCI ID 10ec:8922)
Firmware: rtw89/rtw8922a_fw-4.bin, version 0.35.80.3 (8ef4f0cf)
RFE type: 1
I am happy to provide additional debugging information, test patches, or collect further traces if needed.
Thanks,
Jeffrey Wälti
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-03-23 10:58 wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change Jeffrey Wälti
@ 2026-03-24 2:02 ` Ping-Ke Shih
2026-03-25 19:25 ` Jeffrey Wälti
0 siblings, 1 reply; 8+ messages in thread
From: Ping-Ke Shih @ 2026-03-24 2:02 UTC (permalink / raw)
To: Jeffrey Wälti, linux-wireless@vger.kernel.org
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> Hi,
>
> I am experiencing a reproducible HWSI bus lockup on the RTL8922AE
> (rtw89_8922ae) triggered by the connected AP changing its advertised
> bandwidth in a beacon. During the lockup, the radio is unresponsive and the only
> fix I could find is reconnecting to the network.
>
> The issue occurs on every boot within seconds of association, and also during
> normal operation whenever the AP re-advertises its
> channel width.
>
> I have tested with both the in-tree driver on kernel 6.19 and the
> latest out-of-tree driver from morrownr/rtw89 (git HEAD). Both
> reproduce the issue identically.
Please try to disable power save and ASPM by
1) iw wlan0 set power_save off
2) reference and install https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
and then cold reboot.
>
> User-visible impact
> -------------------
>
> During the HWSI busy window, all network traffic basically stops. Existing TCP
> connections stall and time-sensitive applications (VoIP, video calls) break. The
> Wi-Fi/BT coexistence is also disrupted, causing paired Bluetooth devices to
> disconnect.
>
> The issue reproduces on every association and also during
> runtime when the AP periodically re-advertises its bandwidth (sometimes every
> few minutes), making connectivity unreliable.
>
> Boot-to-bug dmesg (trimmed to relevant entries)
> ------------------------------------------------
>
> [ 17.659262] rtw89_8922ae 0000:03:00.0: loaded firmware
> rtw89/rtw8922a_fw-4.bin
> [ 17.659440] rtw89_8922ae 0000:03:00.0: enabling device (0000 -> 0003)
> [ 17.666964] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf),
> cmd version 1, type 1
> [ 17.666968] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf),
> cmd version 1, type 3
> [ 17.685115] rtw89_8922ae 0000:03:00.0: chip rfe_type is 1
> [ 17.685886] input: HD-Audio Generic Mic as
> /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input24
> [ 17.685913] input: HD-Audio Generic Headphone as
> /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input25
> [ 17.687499] rtw89_8922ae 0000:03:00.0: Firmware version 0.1.0.0 (7b393818),
> cmd version 0, type 64
> [ 17.687504] rtw89_8922ae 0000:03:00.0: Firmware element BB version: 00 49 00
> 00
> [ 17.687511] rtw89_8922ae 0000:03:00.0: Firmware element radio A version: 00
> 33 00 00
> [ 17.687516] rtw89_8922ae 0000:03:00.0: Firmware element NCTL version: 00 0f
> 00 00
> [ 17.687536] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> 00 00
> [ 17.687537] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> 00 00
> [ 17.687538] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> 00 00
> [ 17.687546] rtw89_8922ae 0000:03:00.0: Firmware element PWR_TRK version: 00
> 33 00 00
> [ 17.687550] rtw89_8922ae 0000:03:00.0: Firmware element REGD version: 00 49
> 00 08
> [ 17.691873] rtw89_8922ae 0000:03:00.0: rfkill hardware state changed to
> enable
> [ 18.108033] systemd-journald[808]: Received client request to flush runtime
> journal.
> [ 18.367229] input: keyd virtual keyboard as /devices/virtual/input/input26
> [ 18.383013] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 18.383017] Bluetooth: BNEP filters: protocol multicast
> [ 18.383021] Bluetooth: BNEP socket layer initialized
> [ 18.410929] input: keyd virtual pointer as /devices/virtual/input/input27
> [ 18.464298] Bluetooth: hci0: RTL: fw version 0x41c0c905
> [ 18.647322] Bluetooth: hci0: AOSP extensions version v1.00
> [ 18.647546] Bluetooth: MGMT ver 1.23
> [ 18.655814] NET: Registered PF_ALG protocol family
> [ 21.985205] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local
> address=7c:fa:80:c3:5b:f9)
> [ 21.985210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
> [ 22.001200] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local
> address=7c:fa:80:c3:5b:f9)
> [ 22.001210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
> [ 22.002893] wlan0: authenticated
> [ 22.003792] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
> [ 22.005327] wlan0: RX AssocResp from 7c:10:c9:b5:b4:4c (capab=0x1011
> status=0 aid=17)
> [ 22.111182] wlan0: associated
> [ 22.111255] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from
> 7c:10:c9:b5:b4:4c
> [ 22.111263] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by
> 7c:10:c9:b5:b4:4c
> [ 32.623170] hid-sensor-hub 0020:1022:0001.0004: hidraw3: SENSOR HUB HID
> v0.00 Device [hid-amdsfh 1022:0001] on pcie_mp2_amd
> [ 33.076564] wlan0: AP 7c:10:c9:b5:b4:4c changed bandwidth in beacon, new used
> config is 5220.000 MHz, width 5 (5250.000/0 MHz)
> [ 33.090085] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.102460] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.114775] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.127371] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.141826] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.153783] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.165901] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.178402] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.191675] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.205185] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.217544] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.229788] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.242802] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.257200] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.269858] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.282153] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.295625] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.307822] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.320258] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.332693] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.345004] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.360051] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.373084] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.385703] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.397827] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.411372] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.426744] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.438969] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.451407] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.464456] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.477296] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.489589] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.502064] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> [ 33.514235] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> is busy
> [ 33.514249] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from
> 7c:10:c9:b5:b4:4c
> [ 34.491697] rfkill: input handler disabled
> [ 34.778186] Bluetooth: RFCOMM TTY layer initialized
> [ 34.778198] Bluetooth: RFCOMM socket layer initialized
> [ 34.778201] Bluetooth: RFCOMM ver 1.11
> [ 39.723603] rfkill: input handler enabled
> [ 40.871391] rfkill: input handler disabled
> [ 41.010414] nvme nvme0: using unchecked data buffer
> [ 43.272141] warning: `ThreadPoolForeg' uses wireless extensions which will
> stop working for Wi-Fi 7 hardware; use nl80211
>
> Environment
> -----------
>
> Linux version 6.19.9-1-cachyos (linux-cachyos@cachyos) (clang version 22.1.1,
> LLD 22.1.1) #1 SMP PREEMPT_DYNAMIC Thu, 19 Mar 2026 20:13:27 +0000
>
> 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8922AE
> 802.11be PCIe Wireless Network Adapter [10ec:8922] (rev 01)
> Subsystem: Lenovo Device [17aa:4922]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 112
> IOMMU group: 15
> Region 0: I/O ports at 2000 [size=256]
> Region 2: Memory at 80b00000 (64-bit, non-prefetchable) [size=1M]
> Capabilities: <access denied>
> Kernel driver in use: rtw89_8922ae
> Kernel modules: rtw89_8922ae
>
> rtw89_8922ae 12288 0
> rtw89_8922a 77824 1 rtw89_8922ae
> rtw89_pci 131072 1 rtw89_8922ae
> rtw89_core 1236992 2 rtw89_8922a,rtw89_pci
> mac80211 1806336 2 rtw89_core,rtw89_pci
> cfg80211 1523712 3 rtw89_core,rtw89_8922a,mac80211
> rfkill 45056 9 rtw89_core,bluetooth,ideapad_laptop,cfg80211
>
> Hardware: Lenovo Yoga 7 2-in-1 14AKP10 (machine type 83JR)
> Chip: RTL8922AE (PCI ID 10ec:8922)
> Firmware: rtw89/rtw8922a_fw-4.bin, version 0.35.80.3 (8ef4f0cf)
> RFE type: 1
>
> I am happy to provide additional debugging information, test patches, or collect
> further traces if needed.
Please help to test the latest kernel 7.0-rc with additional patch [1].
[1] https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek.com/
Ping-Ke
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-03-24 2:02 ` Ping-Ke Shih
@ 2026-03-25 19:25 ` Jeffrey Wälti
2026-03-26 0:23 ` Ping-Ke Shih
0 siblings, 1 reply; 8+ messages in thread
From: Jeffrey Wälti @ 2026-03-25 19:25 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
<pkshih@realtek.com> wrote:
> Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > Hi,
> >
> > I am experiencing a reproducible HWSI bus lockup on the RTL8922AE
> > (rtw89_8922ae) triggered by the connected AP changing its advertised
> > bandwidth in a beacon. During the lockup, the radio is unresponsive and the only
> > fix I could find is reconnecting to the network.
> >
> > The issue occurs on every boot within seconds of association, and also during
> > normal operation whenever the AP re-advertises its
> > channel width.
> >
> > I have tested with both the in-tree driver on kernel 6.19 and the
> > latest out-of-tree driver from morrownr/rtw89 (git HEAD). Both
> > reproduce the issue identically.
>
> Please try to disable power save and ASPM by
> 1) iw wlan0 set power_save off
> 2) reference and install https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> and then cold reboot.
>
> >
> > User-visible impact
> > -------------------
> >
> > During the HWSI busy window, all network traffic basically stops. Existing TCP
> > connections stall and time-sensitive applications (VoIP, video calls) break. The
> > Wi-Fi/BT coexistence is also disrupted, causing paired Bluetooth devices to
> > disconnect.
> >
> > The issue reproduces on every association and also during
> > runtime when the AP periodically re-advertises its bandwidth (sometimes every
> > few minutes), making connectivity unreliable.
> >
> > Boot-to-bug dmesg (trimmed to relevant entries)
> > ------------------------------------------------
> >
> > [ 17.659262] rtw89_8922ae 0000:03:00.0: loaded firmware
> > rtw89/rtw8922a_fw-4.bin
> > [ 17.659440] rtw89_8922ae 0000:03:00.0: enabling device (0000 -> 0003)
> > [ 17.666964] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf),
> > cmd version 1, type 1
> > [ 17.666968] rtw89_8922ae 0000:03:00.0: Firmware version 0.35.80.3 (8ef4f0cf),
> > cmd version 1, type 3
> > [ 17.685115] rtw89_8922ae 0000:03:00.0: chip rfe_type is 1
> > [ 17.685886] input: HD-Audio Generic Mic as
> > /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input24
> > [ 17.685913] input: HD-Audio Generic Headphone as
> > /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input25
> > [ 17.687499] rtw89_8922ae 0000:03:00.0: Firmware version 0.1.0.0 (7b393818),
> > cmd version 0, type 64
> > [ 17.687504] rtw89_8922ae 0000:03:00.0: Firmware element BB version: 00 49 00
> > 00
> > [ 17.687511] rtw89_8922ae 0000:03:00.0: Firmware element radio A version: 00
> > 33 00 00
> > [ 17.687516] rtw89_8922ae 0000:03:00.0: Firmware element NCTL version: 00 0f
> > 00 00
> > [ 17.687536] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> > 00 00
> > [ 17.687537] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> > 00 00
> > [ 17.687538] rtw89_8922ae 0000:03:00.0: Firmware element TXPWR version: 00 46
> > 00 00
> > [ 17.687546] rtw89_8922ae 0000:03:00.0: Firmware element PWR_TRK version: 00
> > 33 00 00
> > [ 17.687550] rtw89_8922ae 0000:03:00.0: Firmware element REGD version: 00 49
> > 00 08
> > [ 17.691873] rtw89_8922ae 0000:03:00.0: rfkill hardware state changed to
> > enable
> > [ 18.108033] systemd-journald[808]: Received client request to flush runtime
> > journal.
> > [ 18.367229] input: keyd virtual keyboard as /devices/virtual/input/input26
> > [ 18.383013] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> > [ 18.383017] Bluetooth: BNEP filters: protocol multicast
> > [ 18.383021] Bluetooth: BNEP socket layer initialized
> > [ 18.410929] input: keyd virtual pointer as /devices/virtual/input/input27
> > [ 18.464298] Bluetooth: hci0: RTL: fw version 0x41c0c905
> > [ 18.647322] Bluetooth: hci0: AOSP extensions version v1.00
> > [ 18.647546] Bluetooth: MGMT ver 1.23
> > [ 18.655814] NET: Registered PF_ALG protocol family
> > [ 21.985205] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local
> > address=7c:fa:80:c3:5b:f9)
> > [ 21.985210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
> > [ 22.001200] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local
> > address=7c:fa:80:c3:5b:f9)
> > [ 22.001210] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
> > [ 22.002893] wlan0: authenticated
> > [ 22.003792] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
> > [ 22.005327] wlan0: RX AssocResp from 7c:10:c9:b5:b4:4c (capab=0x1011
> > status=0 aid=17)
> > [ 22.111182] wlan0: associated
> > [ 22.111255] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from
> > 7c:10:c9:b5:b4:4c
> > [ 22.111263] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by
> > 7c:10:c9:b5:b4:4c
> > [ 32.623170] hid-sensor-hub 0020:1022:0001.0004: hidraw3: SENSOR HUB HID
> > v0.00 Device [hid-amdsfh 1022:0001] on pcie_mp2_amd
> > [ 33.076564] wlan0: AP 7c:10:c9:b5:b4:4c changed bandwidth in beacon, new used
> > config is 5220.000 MHz, width 5 (5250.000/0 MHz)
> > [ 33.090085] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.102460] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.114775] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.127371] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.141826] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.153783] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.165901] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.178402] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.191675] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.205185] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.217544] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.229788] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.242802] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.257200] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.269858] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.282153] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.295625] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.307822] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.320258] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.332693] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.345004] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.360051] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.373084] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.385703] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.397827] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.411372] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.426744] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.438969] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.451407] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.464456] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.477296] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.489589] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.502064] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
> > [ 33.514235] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI
> > is busy
> > [ 33.514249] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from
> > 7c:10:c9:b5:b4:4c
> > [ 34.491697] rfkill: input handler disabled
> > [ 34.778186] Bluetooth: RFCOMM TTY layer initialized
> > [ 34.778198] Bluetooth: RFCOMM socket layer initialized
> > [ 34.778201] Bluetooth: RFCOMM ver 1.11
> > [ 39.723603] rfkill: input handler enabled
> > [ 40.871391] rfkill: input handler disabled
> > [ 41.010414] nvme nvme0: using unchecked data buffer
> > [ 43.272141] warning: `ThreadPoolForeg' uses wireless extensions which will
> > stop working for Wi-Fi 7 hardware; use nl80211
> >
> > Environment
> > -----------
> >
> > Linux version 6.19.9-1-cachyos (linux-cachyos@cachyos) (clang version 22.1.1,
> > LLD 22.1.1) #1 SMP PREEMPT_DYNAMIC Thu, 19 Mar 2026 20:13:27 +0000
> >
> > 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8922AE
> > 802.11be PCIe Wireless Network Adapter [10ec:8922] (rev 01)
> > Subsystem: Lenovo Device [17aa:4922]
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B- DisINTx+
> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
> > <MAbort- >SERR- <PERR- INTx-
> > Latency: 0
> > Interrupt: pin A routed to IRQ 112
> > IOMMU group: 15
> > Region 0: I/O ports at 2000 [size=256]
> > Region 2: Memory at 80b00000 (64-bit, non-prefetchable) [size=1M]
> > Capabilities: <access denied>
> > Kernel driver in use: rtw89_8922ae
> > Kernel modules: rtw89_8922ae
> >
> > rtw89_8922ae 12288 0
> > rtw89_8922a 77824 1 rtw89_8922ae
> > rtw89_pci 131072 1 rtw89_8922ae
> > rtw89_core 1236992 2 rtw89_8922a,rtw89_pci
> > mac80211 1806336 2 rtw89_core,rtw89_pci
> > cfg80211 1523712 3 rtw89_core,rtw89_8922a,mac80211
> > rfkill 45056 9 rtw89_core,bluetooth,ideapad_laptop,cfg80211
> >
> > Hardware: Lenovo Yoga 7 2-in-1 14AKP10 (machine type 83JR)
> > Chip: RTL8922AE (PCI ID 10ec:8922)
> > Firmware: rtw89/rtw8922a_fw-4.bin, version 0.35.80.3 (8ef4f0cf)
> > RFE type: 1
> >
> > I am happy to provide additional debugging information, test patches, or collect
> > further traces if needed.
>
> Please help to test the latest kernel 7.0-rc with additional patch [1].
>
> [1] https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek.com/
>
> Ping-Ke
>
>
Thank you for coming back to me so quickly, I just encountered the same thing with kernel 7.0-rc5.
[26055.113514] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[26055.113528] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[26055.133089] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 2/3)
[26055.150902] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[26055.150914] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[26055.153246] wlan0: authenticated
[26055.153721] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
[26055.155584] wlan0: RX AssocResp from 7c:10:c9:b5:b4:4c (capab=0x1011 status=0 aid=27)
[26055.271023] wlan0: associated
[26055.271237] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[26055.271248] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 7c:10:c9:b5:b4:4c
[26065.984663] wlan0: AP 7c:10:c9:b5:b4:4c changed bandwidth in beacon, new used config is 5220.000 MHz, width 5 (5250.000/0 MHz)
[26065.999102] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.012897] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.026604] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.040218] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.055075] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.066562] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.078117] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.090357] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.102961] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.115725] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.127339] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.139004] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.150442] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.161916] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.173963] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.185870] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.197456] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.209340] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.221632] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.233635] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.245872] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.259756] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.271685] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.283509] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.295651] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.308285] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.320675] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.332706] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.344874] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.356848] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.369061] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.381196] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.393249] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26066.405227] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26066.405240] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[26078.276959] wlan0: authenticate with 7c:10:c9:b5:b4:48 (local address=7c:fa:80:c3:5b:f9)
[26078.276970] wlan0: send auth to 7c:10:c9:b5:b4:48 (try 1/3)
[26078.295560] wlan0: authenticate with 7c:10:c9:b5:b4:48 (local address=7c:fa:80:c3:5b:f9)
[26078.295573] wlan0: send auth to 7c:10:c9:b5:b4:48 (try 1/3)
[26078.305323] wlan0: authenticated
[26078.307561] wlan0: associate with 7c:10:c9:b5:b4:48 (try 1/3)
[26078.313095] wlan0: RX AssocResp from 7c:10:c9:b5:b4:48 (capab=0x1411 status=0 aid=33)
[26078.424096] wlan0: associated
[26165.453429] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are enabled
[26226.049306] wlan0: disconnect from AP 7c:10:c9:b5:b4:48 for new auth to 7c:10:c9:b5:b4:4c
[26226.283858] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[26226.283870] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[26226.284759] wlan0: authenticated
[26226.286909] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
[26226.289664] wlan0: RX ReassocResp from 7c:10:c9:b5:b4:4c (capab=0x1011 status=0 aid=13)
[26226.400500] wlan0: associated
[26226.400560] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[26226.400566] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 7c:10:c9:b5:b4:4c
[26237.305703] wlan0: AP 7c:10:c9:b5:b4:4c changed bandwidth in beacon, new used config is 5220.000 MHz, width 5 (5250.000/0 MHz)
[26237.323124] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.338894] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.352942] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.366488] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.380974] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.396258] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.410103] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.423962] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.439875] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.454635] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.468377] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.482203] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.496234] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.510190] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.524248] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.536842] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.550513] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.564329] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.578157] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.591944] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.605710] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.621850] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.635990] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.650297] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.664291] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.679167] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.694107] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.708096] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.722032] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.735945] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.749689] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.763441] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.777281] rtw89_8922ae 0000:03:00.0: poll HWSI is busy
[26237.791136] rtw89_8922ae 0000:03:00.0: [rtw89_phy_write_full_rf_v2_a] HWSI is busy
[26237.791148] wlan0: Ignore NSS change to invalid 4 in VHT opmode notif from 7c:10:c9:b5:b4:4c
[26323.825259] wlan0: deauthenticating from 7c:10:c9:b5:b4:4c by local choice (Reason: 3=DEAUTH_LEAVING)
[26324.373581] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[26324.373593] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[26324.391589] wlan0: authenticate with 7c:10:c9:b5:b4:4c (local address=7c:fa:80:c3:5b:f9)
[26324.391624] wlan0: send auth to 7c:10:c9:b5:b4:4c (try 1/3)
[26324.393858] wlan0: authenticated
[26324.394270] wlan0: associate with 7c:10:c9:b5:b4:4c (try 1/3)
[26324.395784] wlan0: RX AssocResp from 7c:10:c9:b5:b4:4c (capab=0x1011 status=0 aid=20)
[26324.503689] wlan0: associated
[26324.503778] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 7c:10:c9:b5:b4:4c
Jeffrey Wälti
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-03-25 19:25 ` Jeffrey Wälti
@ 2026-03-26 0:23 ` Ping-Ke Shih
2026-04-01 11:24 ` Jeffrey Wälti
0 siblings, 1 reply; 8+ messages in thread
From: Ping-Ke Shih @ 2026-03-26 0:23 UTC (permalink / raw)
To: Jeffrey Wälti; +Cc: linux-wireless@vger.kernel.org
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
>
> <pkshih@realtek.com> wrote:
>
> >
> > Please try to disable power save and ASPM by
> > 1) iw wlan0 set power_save off
> > 2) reference and install
> https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > and then cold reboot.
Have you tested with these conditions?
[...]
> >
> > Please help to test the latest kernel 7.0-rc with additional patch [1].
> >
> > [1]
> https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> .com/
Have you also applied this patch?
> >
> > Ping-Ke
> >
> >
>
> Thank you for coming back to me so quickly, I just encountered the same thing
> with kernel 7.0-rc5.
>
Please confirm my questions above.
Ping-Ke
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-03-26 0:23 ` Ping-Ke Shih
@ 2026-04-01 11:24 ` Jeffrey Wälti
2026-04-02 2:36 ` Ping-Ke Shih
0 siblings, 1 reply; 8+ messages in thread
From: Jeffrey Wälti @ 2026-04-01 11:24 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
Ping-Ke Shih <pkshih@realtek.com> wrote:
> Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> >
> > <pkshih@realtek.com> wrote:
> >
> > >
> > > Please try to disable power save and ASPM by
> > > 1) iw wlan0 set power_save off
I'm sorry, this is my first time interacting with the mailing list and I overlooked the other instructions. It seems like disabling power save gets rid of the issue of Wi-Fi timeouts. I haven't been able to reproduce the issue with `iw wlan0 set power_save off` yet, even without any of the other fixes on kernel 6.19.10 and 7.0-rc6.
> > > 2) reference and install
> > https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > > and then cold reboot.
>
> Have you tested with these conditions?
Using this patch eliminates the issue of Bluetooth devices disconnecting, when switching between networks.
> [...]
>
> > >
> > > Please help to test the latest kernel 7.0-rc with additional patch [1].
> > >
> > > [1]
> > https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> > .com/
>
> Have you also applied this patch?
I tested kernel 7.0-rc6 with this patch applied on top for ~1 day now and haven't been able to reproduce, even with power save enabled. However, it is a bit difficult to reliably trigger the issue as it seems to trigger more on certain networks than others etc.
> > >
> > > Ping-Ke
> > >
> > >
> >
> > Thank you for coming back to me so quickly, I just encountered the same thing
> > with kernel 7.0-rc5.
> >
>
> Please confirm my questions above.
>
> Ping-Ke
>
>
In summary:
- Disabling power save seems to stop the timeouts but Bluetooth issues remain
- Disabling ASPM features fixes the Bluetooth issue
- kernel 7.0-rc6 with the additional patch fixes Wi-Fi timeouts but not the Bluetooth disconnects
I hope that answers your questions.
Jeffrey
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-04-01 11:24 ` Jeffrey Wälti
@ 2026-04-02 2:36 ` Ping-Ke Shih
[not found] ` <nPBjkph3lQo2eiuYIDyn7Mx8rg_pYRHNkQ-yyIVecS7isXyz4KC77Kud29sqnGKgCVgZS_IM1Jj28gx1RN4iaLuyKhS_MZVUnXhy-BVGCfQ=@waelti.dev>
0 siblings, 1 reply; 8+ messages in thread
From: Ping-Ke Shih @ 2026-04-02 2:36 UTC (permalink / raw)
To: Jeffrey Wälti; +Cc: linux-wireless@vger.kernel.org
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
>
> Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > >
> > > <pkshih@realtek.com> wrote:
> > >
> > > >
> > > > Please try to disable power save and ASPM by
> > > > 1) iw wlan0 set power_save off
>
> I'm sorry, this is my first time interacting with the mailing list and I overlooked the other instructions.
> It seems like disabling power save gets rid of the issue of Wi-Fi timeouts. I haven't been able to
> reproduce the issue with `iw wlan0 set power_save off` yet, even without any of the other fixes on kernel
> 6.19.10 and 7.0-rc6.
>
> > > > 2) reference and install
> > > https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > > > and then cold reboot.
> >
> > Have you tested with these conditions?
>
> Using this patch eliminates the issue of Bluetooth devices disconnecting, when switching between
> networks.
>
> > [...]
> >
> > > >
> > > > Please help to test the latest kernel 7.0-rc with additional patch [1].
> > > >
> > > > [1]
> > > https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> > > .com/
> >
> > Have you also applied this patch?
>
> I tested kernel 7.0-rc6 with this patch applied on top for ~1 day now and haven't been able to reproduce,
> even with power save enabled. However, it is a bit difficult to reliably trigger the issue as it seems
> to trigger more on certain networks than others etc.
>
> > > >
> > > > Ping-Ke
> > > >
> > > >
> > >
> > > Thank you for coming back to me so quickly, I just encountered the same thing
> > > with kernel 7.0-rc5.
> > >
> >
> > Please confirm my questions above.
> >
> > Ping-Ke
> >
> >
>
> In summary:
> - Disabling power save seems to stop the timeouts but Bluetooth issues remain
> - Disabling ASPM features fixes the Bluetooth issue
> - kernel 7.0-rc6 with the additional patch fixes Wi-Fi timeouts but not the Bluetooth disconnects
>
> I hope that answers your questions.
It looks like additional patch can fix the WiFi timeouts problem, and
disabling ASPM feature can fix Bluetooth issue. I think you can keep
(2) + (3) setting as workaround.
I'd talk with BT coexistence team internally to figure out the cause
of Bluetooth disconnection.
Ping-Ke
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
[not found] ` <nPBjkph3lQo2eiuYIDyn7Mx8rg_pYRHNkQ-yyIVecS7isXyz4KC77Kud29sqnGKgCVgZS_IM1Jj28gx1RN4iaLuyKhS_MZVUnXhy-BVGCfQ=@waelti.dev>
@ 2026-04-03 10:43 ` Jeffrey Wälti
2026-04-07 0:38 ` Ping-Ke Shih
0 siblings, 1 reply; 8+ messages in thread
From: Jeffrey Wälti @ 2026-04-03 10:43 UTC (permalink / raw)
To: Ping-Ke Shih; +Cc: linux-wireless@vger.kernel.org
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > >
> > > Ping-Ke Shih <pkshih@realtek.com> wrote:
> > >
> > > > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > > > >
> > > > > <pkshih@realtek.com> wrote:
> > > > >
> > > > > >
> > > > > > Please try to disable power save and ASPM by
> > > > > > 1) iw wlan0 set power_save off
> > >
> > > I'm sorry, this is my first time interacting with the mailing list and I overlooked the other instructions.
> > > It seems like disabling power save gets rid of the issue of Wi-Fi timeouts. I haven't been able to
> > > reproduce the issue with `iw wlan0 set power_save off` yet, even without any of the other fixes on kernel
> > > 6.19.10 and 7.0-rc6.
> > >
> > > > > > 2) reference and install
> > > > > https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > > > > > and then cold reboot.
> > > >
> > > > Have you tested with these conditions?
> > >
> > > Using this patch eliminates the issue of Bluetooth devices disconnecting, when switching between
> > > networks.
> > >
> > > > [...]
> > > >
> > > > > >
> > > > > > Please help to test the latest kernel 7.0-rc with additional patch [1].
> > > > > >
> > > > > > [1]
> > > > > https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> > > > > .com/
> > > >
> > > > Have you also applied this patch?
> > >
> > > I tested kernel 7.0-rc6 with this patch applied on top for ~1 day now and haven't been able to reproduce,
> > > even with power save enabled. However, it is a bit difficult to reliably trigger the issue as it seems
> > > to trigger more on certain networks than others etc.
> > >
> > > > > >
> > > > > > Ping-Ke
> > > > > >
> > > > > >
> > > > >
> > > > > Thank you for coming back to me so quickly, I just encountered the same thing
> > > > > with kernel 7.0-rc5.
> > > > >
> > > >
> > > > Please confirm my questions above.
> > > >
> > > > Ping-Ke
> > > >
> > > >
> > >
> > > In summary:
> > > - Disabling power save seems to stop the timeouts but Bluetooth issues remain
> > > - Disabling ASPM features fixes the Bluetooth issue
> > > - kernel 7.0-rc6 with the additional patch fixes Wi-Fi timeouts but not the Bluetooth disconnects
> > >
> > > I hope that answers your questions.
> >
> > It looks like additional patch can fix the WiFi timeouts problem, and
> > disabling ASPM feature can fix Bluetooth issue. I think you can keep
> > (2) + (3) setting as workaround.
> >
> > I'd talk with BT coexistence team internally to figure out the cause
> > of Bluetooth disconnection.
>
> As always, thank you very much for coming back to me so quickly and working on a fix. Please do let me know if there is any progress on the issue or if you need any more help testing a patch.
Hi again,
I'm sorry for coming back to you so quickly once again, but I am sad to report, that I just encountered the same issue again with kernel 7.0-rc6 and the custom patch applied. After resume the Wi-Fi connection ran at less than 1/100 of the expected speed and wouldn't come back up, until I reconnected to the same network. It seems like just the custom patch was not enough to fix the underlying issue, but it did fix the HWSI lock up. This is what dmesg tells me.
[126462.035430] PM: suspend exit
[126465.615935] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
[126465.615944] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
[126465.634818] wlan0: send auth to 68:67:c7:2a:20:43 (try 2/3)
[126465.654072] wlan0: send auth to 68:67:c7:2a:20:43 (try 3/3)
[126465.673115] wlan0: authentication with 68:67:c7:2a:20:43 timed out
[126466.065780] wlan0: authenticate with 68:67:c7:2a:20:42 (local address=7c:fa:80:c3:5b:f9)
[126466.065789] wlan0: send auth to 68:67:c7:2a:20:42 (try 1/3)
[126468.082718] wlan0: send auth to 68:67:c7:2a:20:42 (try 2/3)
[126470.107802] wlan0: send auth to 68:67:c7:2a:20:42 (try 3/3)
[126471.070743] wlan0: aborting authentication with 68:67:c7:2a:20:42 by local choice (Reason: 3=DEAUTH_LEAVING)
[126474.858695] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
[126474.858705] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
[126474.879430] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
[126474.879439] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
[126474.884633] wlan0: authenticated
[126474.885578] wlan0: associate with 68:67:c7:2a:20:43 (try 1/3)
[126474.899521] wlan0: RX AssocResp from 68:67:c7:2a:20:43 (capab=0x1011 status=0 aid=20)
[126475.002744] wlan0: associated
[126475.002799] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 68:67:c7:2a:20:43
[126490.802365] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are enabled
[126627.760736] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are enabled
(Here I decide to manually reconnect to the same network)
[126737.556015] wlan0: deauthenticating from 68:67:c7:2a:20:43 by local choice (Reason: 3=DEAUTH_LEAVING)
[126738.215678] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
[126738.215697] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
[126740.272244] wlan0: send auth to 68:67:c7:2a:20:43 (try 2/3)
[126740.291264] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
[126740.291271] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
[126740.293310] wlan0: authenticated
[126740.294214] wlan0: associate with 68:67:c7:2a:20:43 (try 1/3)
[126740.303679] wlan0: RX AssocResp from 68:67:c7:2a:20:43 (capab=0x1011 status=0 aid=21)
[126740.409430] wlan0: associated
[126740.409517] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 68:67:c7:2a:20:43
I will resume testing with the power save function turned off, to check if that still is a working workaround for now.
Jeffrey
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change
2026-04-03 10:43 ` Jeffrey Wälti
@ 2026-04-07 0:38 ` Ping-Ke Shih
0 siblings, 0 replies; 8+ messages in thread
From: Ping-Ke Shih @ 2026-04-07 0:38 UTC (permalink / raw)
To: Jeffrey Wälti; +Cc: linux-wireless@vger.kernel.org
Jeffrey Wälti <jeffrey@waelti.dev> wrote:
>
> Jeffrey Wälti <jeffrey@waelti.dev> wrote:
>
> > Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > > >
> > > > Ping-Ke Shih <pkshih@realtek.com> wrote:
> > > >
> > > > > Jeffrey Wälti <jeffrey@waelti.dev> wrote:
> > > > > >
> > > > > > <pkshih@realtek.com> wrote:
> > > > > >
> > > > > > >
> > > > > > > Please try to disable power save and ASPM by
> > > > > > > 1) iw wlan0 set power_save off
> > > >
> > > > I'm sorry, this is my first time interacting with the mailing list and I overlooked the other
> instructions.
> > > > It seems like disabling power save gets rid of the issue of Wi-Fi timeouts. I haven't been able
> to
> > > > reproduce the issue with `iw wlan0 set power_save off` yet, even without any of the other fixes
> on kernel
> > > > 6.19.10 and 7.0-rc6.
> > > >
> > > > > > > 2) reference and install
> > > > > > https://github.com/lwfinger/rtw89/blob/main/70-rtw89.conf
> > > > > > > and then cold reboot.
> > > > >
> > > > > Have you tested with these conditions?
> > > >
> > > > Using this patch eliminates the issue of Bluetooth devices disconnecting, when switching between
> > > > networks.
> > > >
> > > > > [...]
> > > > >
> > > > > > >
> > > > > > > Please help to test the latest kernel 7.0-rc with additional patch [1].
> > > > > > >
> > > > > > > [1]
> > > > > > https://lore.kernel.org/linux-wireless/20260310080146.31113-4-pkshih@realtek
> > > > > > .com/
> > > > >
> > > > > Have you also applied this patch?
> > > >
> > > > I tested kernel 7.0-rc6 with this patch applied on top for ~1 day now and haven't been able to
> reproduce,
> > > > even with power save enabled. However, it is a bit difficult to reliably trigger the issue as
> it seems
> > > > to trigger more on certain networks than others etc.
> > > >
> > > > > > >
> > > > > > > Ping-Ke
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > Thank you for coming back to me so quickly, I just encountered the same thing
> > > > > > with kernel 7.0-rc5.
> > > > > >
> > > > >
> > > > > Please confirm my questions above.
> > > > >
> > > > > Ping-Ke
> > > > >
> > > > >
> > > >
> > > > In summary:
> > > > - Disabling power save seems to stop the timeouts but Bluetooth issues remain
> > > > - Disabling ASPM features fixes the Bluetooth issue
> > > > - kernel 7.0-rc6 with the additional patch fixes Wi-Fi timeouts but not the Bluetooth disconnects
> > > >
> > > > I hope that answers your questions.
> > >
> > > It looks like additional patch can fix the WiFi timeouts problem, and
> > > disabling ASPM feature can fix Bluetooth issue. I think you can keep
> > > (2) + (3) setting as workaround.
> > >
> > > I'd talk with BT coexistence team internally to figure out the cause
> > > of Bluetooth disconnection.
> >
> > As always, thank you very much for coming back to me so quickly and working on a fix. Please do let
> me know if there is any progress on the issue or if you need any more help testing a patch.
>
> Hi again,
>
> I'm sorry for coming back to you so quickly once again, but I am sad to report, that I just encountered
> the same issue again with kernel 7.0-rc6 and the custom patch applied.
What did custom patch you mentioned? The additional patch I mentioned?
> After resume the Wi-Fi connection
> ran at less than 1/100 of the expected speed and wouldn't come back up, until I reconnected to the same
> network. It seems like just the custom patch was not enough to fix the underlying issue, but it did
> fix the HWSI lock up. This is what dmesg tells me.
>
> [126462.035430] PM: suspend exit
> [126465.615935] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
> [126465.615944] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
> [126465.634818] wlan0: send auth to 68:67:c7:2a:20:43 (try 2/3)
> [126465.654072] wlan0: send auth to 68:67:c7:2a:20:43 (try 3/3)
> [126465.673115] wlan0: authentication with 68:67:c7:2a:20:43 timed out
This said that it failed to TX auth or RX auth. I suggest to disable
Bluetooth entirely to see it can improve.
> [126466.065780] wlan0: authenticate with 68:67:c7:2a:20:42 (local address=7c:fa:80:c3:5b:f9)
> [126466.065789] wlan0: send auth to 68:67:c7:2a:20:42 (try 1/3)
> [126468.082718] wlan0: send auth to 68:67:c7:2a:20:42 (try 2/3)
> [126470.107802] wlan0: send auth to 68:67:c7:2a:20:42 (try 3/3)
> [126471.070743] wlan0: aborting authentication with 68:67:c7:2a:20:42 by local choice (Reason:
> 3=DEAUTH_LEAVING)
> [126474.858695] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
> [126474.858705] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
> [126474.879430] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
> [126474.879439] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
> [126474.884633] wlan0: authenticated
> [126474.885578] wlan0: associate with 68:67:c7:2a:20:43 (try 1/3)
> [126474.899521] wlan0: RX AssocResp from 68:67:c7:2a:20:43 (capab=0x1011 status=0 aid=20)
> [126475.002744] wlan0: associated
> [126475.002799] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 68:67:c7:2a:20:43
> [126490.802365] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are
> enabled
> [126627.760736] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast] and [Long_Life] are
> enabled
>
> (Here I decide to manually reconnect to the same network)
>
> [126737.556015] wlan0: deauthenticating from 68:67:c7:2a:20:43 by local choice (Reason:
> 3=DEAUTH_LEAVING)
> [126738.215678] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
> [126738.215697] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
> [126740.272244] wlan0: send auth to 68:67:c7:2a:20:43 (try 2/3)
> [126740.291264] wlan0: authenticate with 68:67:c7:2a:20:43 (local address=7c:fa:80:c3:5b:f9)
> [126740.291271] wlan0: send auth to 68:67:c7:2a:20:43 (try 1/3)
> [126740.293310] wlan0: authenticated
> [126740.294214] wlan0: associate with 68:67:c7:2a:20:43 (try 1/3)
> [126740.303679] wlan0: RX AssocResp from 68:67:c7:2a:20:43 (capab=0x1011 status=0 aid=21)
> [126740.409430] wlan0: associated
> [126740.409517] wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by 68:67:c7:2a:20:43
>
> I will resume testing with the power save function turned off, to check if that still is a working
> workaround for now.
Please test it.
Ping-Ke
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-04-07 0:38 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-23 10:58 wifi: rtw89: rtw8922ae: HWSI bus lockup during RF recalibration on AP bandwidth change Jeffrey Wälti
2026-03-24 2:02 ` Ping-Ke Shih
2026-03-25 19:25 ` Jeffrey Wälti
2026-03-26 0:23 ` Ping-Ke Shih
2026-04-01 11:24 ` Jeffrey Wälti
2026-04-02 2:36 ` Ping-Ke Shih
[not found] ` <nPBjkph3lQo2eiuYIDyn7Mx8rg_pYRHNkQ-yyIVecS7isXyz4KC77Kud29sqnGKgCVgZS_IM1Jj28gx1RN4iaLuyKhS_MZVUnXhy-BVGCfQ=@waelti.dev>
2026-04-03 10:43 ` Jeffrey Wälti
2026-04-07 0:38 ` Ping-Ke Shih
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox