rtw89_8852be : wifi and bluetooth interfere

[MK73DS]

Hello,
Recently, I noticed I couldn't use bluetooth headsets with my PC since the audio is very chopped. After some investigation, I found that the wifi is causing interference since both bluetooth and wifi use the same physical antenna. This finding was made clear since from the very moment I turn off my wifi (iwctl adapter phy0 set-property Powered off) the audio is immediately glitchless, and immediately when I turn it back on it starts skipping a lot. This is weird since I'm connected to a 5GHz network and interference shouldn't happen...

However, this wasn't always the case, and bluetooth and wifi were able to coexist without any issue even on a 2.4GHz network, so my hardware (or my BIOS) definitely isn't at fault. I tried to bisect the faulting commit, I only did it on a day by day basis and not on a commit by commit basis in order to save time, here are my findings (format is DD/MM/YYYY) :

• 22/05/2023 (commit hash d25cd62 ) : No problem
• 26/05/2023 (commit hash 2286917 ) : Wifi doesn't work
• 27/05/2023 (commit hash 0d76345 ) : Wifi doesn't work
• 28/05/2023 (commit hash 8705056 ) : Wifi works but interference with bluetooth

I do not have any technical knowledge so I can't really be more precise on what introduced the issue, I am sorry. Also, I can't seem to find any log generated when the glitches happen during playback of audio...

Here are my system infos:

System:
  Host: ?????? Kernel: 6.4.7-arch1-2 arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.27.7 Distro: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82SN v: IdeaPad 5 Pro 16ARH7
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0K17763 WIN
    serial: <superuser required> UEFI: LENOVO v: J4CN36WW date: 12/29/2022
Battery:
  ID-1: BAT0 charge: 57.3 Wh (77.6%) condition: 73.8/75.0 Wh (98.4%)
CPU:
  Info: 8-core AMD Ryzen 7 6800HS Creator Edition [MT MCP] speed (MHz):
    avg: 1800 min/max: 1600/4784
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
  Device-2: Chicony Integrated Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: amdgpu
    unloaded: modesetting dri: radeonsi gpu: amdgpu s-res: 2560x1600
    resolution: 2560x1600
  API: OpenGL v: 4.6 Mesa 23.3.0-devel (git-c9b2f83a2f) renderer: AMD
    Radeon Graphics (rembrandt LLVM 15.0.7 DRM 3.52 6.4.7-arch1-2)
Network:
  Device-1: Realtek driver: rtw89_8852be
Drives:
  Local Storage: total: 476.94 GiB used: 144.64 GiB (30.3%)

Thank you for helping.

Note : I know my kernel comes with this driver. In fact, I noticed the issue first by using the kernel's driver. During my tests, I have removed the rtw89 driver from the kernel so that I'm sure it doesn't interfere with my bisect.

[lwfinger]

Your so-called bisection is essentially useless. You need to specify what commit failed. As this driver is derived from the kernel driver in wireless-next, you may need to bisect to find the exact commit that failed.

The driver has coexistence routines to ensure that BT and wifi can coexist. As your wifi is 5GHz and BT always uses 2.4 GHz, they should not interfere.

[MK73DS]

Thank you for your quick answer. I did bisect commit by commit. The ones where I didn't get any wifi were because of an error in the Makefile that was corrected in a later commit (this one 8705056 ), so what I did is checkout each commit and manually edit the Makefile while testing.

I found that up until this commit ee73802 everything works fine, but the next commit 2ae0853 introduced the bug I experience. I hope this will make it easier for you (or anyone in charge of this kernel) to find out the issue and hopefully fix it.

I agree with you that 5GHz wifi and bluetooth shouldn't interfere, but they do, I don't know why. I am definitely sure I am connected to a 5GHz network from the output of iwctl station wlan0 show and the fact that the only wifi I have at home is 5GHz.

[lwfinger]

That info is a big help. If you have to do this kind of thing again, it is a lot faster to do a 'git bisect'. If necessary, you can make a patch such as was needed for Makefile.

Please do a further test for me. Using a bad version, do the following:

sudo modprobe -rv rtw_8852be
sudo modprobe -rv rtw89core
sudo modprobe -v rtw89core disable_ps_mode=y
sudo modprobe -v rtw_8852be

Does the result work? Please post the console output so that I can see exactly what it printed. Thanks.

[MK73DS]

Thank you for the info, I am not knowledgeable at all when it comes to git and its more advanced commands. Here is the output of the commands you wanted me to try, I'm using the latest commit from the main branch since it is a bad version.

$ sudo modprobe -rv rtw_8852be
rmmod rtw_8852be
rmmod rtw89pci
rmmod rtw_8852b
$ sudo modprobe -rv rtw89core 
rmmod rtw89core
rmmod mac80211
$ sudo modprobe -v rtw89core disable_ps_mode=y
insmod /lib/modules/6.4.7-arch1-2/kernel/net/mac80211/mac80211.ko.zst 
insmod /lib/modules/6.4.7-arch1-2/kernel/drivers/net/wireless/realtek/rtw89/rtw89core.ko disable_ps_mode=y
$ sudo modprobe -v rtw_8852be
insmod /lib/modules/6.4.7-arch1-2/kernel/drivers/net/wireless/realtek/rtw89/rtw89pci.ko 
insmod /lib/modules/6.4.7-arch1-2/kernel/drivers/net/wireless/realtek/rtw89/rtw_8852b.ko 
insmod /lib/modules/6.4.7-arch1-2/kernel/drivers/net/wireless/realtek/rtw89/rtw_8852be.ko

I also confirm that after this, the issue is gone.
I also tried with the driver included in the linux 6.4 kernel, since I have the same issue with it. By replacing rtw_8852be with rtw89_8852be and rtw89core with rtw89_core in the commands you wanted me to try, the issue is also gone (as expected I guess).

I want to thank you very much once more. It is usually rare to get a response for an issue, especially ones that are that helpful.

[lwfinger]

You are welcome. Helping finding the commit that causes a problem is the kind of thing I can help with.

I will report this problem to the person in charge of the driver at Realtek and see what he has to say. If you want to be kept in the loop, E-mail me a address to use. That will expose that address to an open mailing list, and I understand if you want to avoid that.

[lwfinger]

FYI, this is what I wrote under the subject "Regression in rtw89":
A user of my GitHub repo has reported a regression beginning with commit 26a125f550a3 ("wifi: rtw89: correct PS calculation for SUPPORTS_DYNAMIC_PS").
The user finds interference between wifi and the BT device that is part of the package.

We were able to determine that loading rtw89_core with the "disable_ps_mode=y" option does fix the problem. Our discussion of the problem can be seen at #262 (comment).

Reading the patch in question, it seems that a vif count of 1 is not sufficient to enable PS, and that it is also necessary to make sure that BT is not active as well.

[MK73DS]

Amazing, thank you very much. I don't think I will be of any use in the loop and I prefer to not share my email address publicly, sorry. I hope they will address this issue quickly.

[lwfinger]

I understand your point, which is why I asked the question the way I did.

The Realtek developer and I have a good working arrangement, and he got back to me very quickly. He stated that this patch did not break PS, but that it was broken before. This change merely turned it on correctly, as it is essential for battery life in mobile devices. He also suggested a number of things to try:

1. Make sure your firmware is the latest. You will find the wifi firmware at https://lwfinger.com/download/. Copy the two rtw8852b_fw*.bin files to your local computer, and then move them (as root) to /lib/firmware/rtw89/. For the BT firmware, copy all the files from https://lwfinger.com/rtl_bt/ to your computer, and move them (as root) to /lib/firmware/rtl_bt/. After these firmware files are updated, reboot and test the setup for BT interfereence.
2. If it still fails, open two terminal windows and tile them so that both can be seen. In one, enter the command 'sudo iw wlan0 power_save off'. Change the "wlan0" to the name actually used for your device. If you do not already know this, you can get it from the 'sudo dmesg | grep renamed'. At this point, BT should be working.
3. In the second terminal, create a file named script.sh containing the following:
   #!/bin/sh
   while [ true ]
   do
   cat /sys/kernel/debug/ieee80211/phy0/rtw89/btc_info
   date
   sleep 2
   done
4. Run that script using 'sudo bash script.sh'. It will print every 2 seconds.
5. In the first terminal window, toggle between
   'sudo iw wlan0 power_save on'
   and
   'sudo iw wlan0 power_save off'
   while running your head phones. Allow about 10 seconds between the changes.
6. When failure happens, note the time in the second window where the problem started, and post the output from the second terminal with the time where the problem started.

[MK73DS]

Thank you again.

1. Downloading and copying the files didn't work. Maybe because the firmware files I have on my system are compressed .zst files. So I then removed all the .zst files corresponding to the firmware files I downloaded and rebooted. The issue is still present.
2. As you said, as soon as I disable power_save, the issue immediately disappear. At that point, everything works fine.
3. (nothing particular to say, I created the script)
4. (nothing particular to say, I ran the script)
5. As said before, the effect of enabling/disabling the power_save feature is immediate on my bluetooth audio. I still waited the 10 seconds like you suggested.
6. I will post three times the output of the second terminal.

First is when the problem started. It happened as soon as I enabled the power_save feature on my wifi card.

=========================================
WL FW / BT FW           0.29.29.1 / NA
manual                  0
=========================================

 [bt_info]       : raw_data[49 00 c5 00 04 7f] (type:auto/cnt:1576/same:1)
=========================================
========== [BTC COEX INFO (1)] ==========
 [coex_version]  : Coex:7.0.1(branch:19), WL_FW_coex:7.8.0(branch:29)(Match, desired:5.5.0), BT_FW_coex:7(Match, desired:5)
 [sub_module]    : WL_FW:0.29.29.1, BT_FW:0x1fc6b20f(patch)
 [hw_info]       : cv:1, rfe_type:0x1, ant_iso:10, ant_pg:2, 3rd_coex:0, dbcc:0, tx_num:2, rx_num:2
========== [WL Status] ==========
 [status]        : link_mode:9, rf_off:0, power_save:1, scan:N(band:1/phy_map:0x0), connecting:N, roam:N, 4way:N, init_ok:Y
 [port_0]        : role=1(phy-0), connect=2(client_cnt=-1), mode=3, center_ch=42, bw=2, mac_id=0, max_tx_time=0us, max_tx_retry=0
 [port_0]        : rssi=-59dBm(51), busy=0, dir=DL, tx[rate:260/busy_level:0], rx[rate:280/busy_level:0/drop:0]
========== [BT Status] ==========
 [status]        : enable:Y, btg:Y, connect:Y, igno_wl:N, mailbox_avl:Y, rfk_state:0x0
 [profile]       : profile:A2DP, multi-link:N, role:Master, ble-connect:N, CQDDR:N, A2DP_active:Y, PAN_active:N
 [link]          : rssi:-53dBm, tx_rate:3M,  acl_busy!! afh_map[ffff_ffff_ffff_f3f1_fffe], wl_ch_map[en:0/ch:0/bw:32]
 [stat_cnt]      : retry:0, relink:1, rate_chg:11, reinit:0, reenable:1, role-switch:0, afh:0, inq_page:1(inq:0/page:1), igno_wl:1
 [A2DP]          : type:Legacy, bit-pool:63, flush-time:0, vid:0xa, Dev-name:0x2d4857, sut_pwr:0, golden-rx:0
 [bt_info]       : raw_data[49 00 c5 00 04 7f] (type:auto/cnt:1576/same:1)
 [trx_req_cnt]   : Hi-rx = 178, Hi-tx = 0, Lo-rx = 546, Lo-tx = 546 (bt_polut_wl_tx = 0)(BG:0-0/INIT:0-0/LE:0-0)
========== [Mechanism Status (Auto)] ==========
 [status]        : type:shared, reason:NTFY_RADIO_STATE(), action:WL_OFF(), ant_path:5, run_cnt:2220
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> NTFY_WL_STA         -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> NTFY_WL_STA         -> WL_5G          -> OFF_EQ0      -> NTFY_RADIO_STATE    -> WL_OFF         -> OFF_BT       
 [dm_flag]       : wl_only:0, bt_only:0, igno_bt:1, free_run:0, wl_ps_ctrl:0, wl_mimo_ps:0, leak_ap:0, fw_offload:N
 [trx_ctrl]      : wl_rssi_lvl:3, para_lvl:0, wl_tx_pwr:orig, wl_rx_lvl:0, bt_tx_pwr_dec:0, bt_rx_lna:7(Ori-tbl), wl_btg_rx:0
 [dm_ctrl]       : wl_tx_limit[en:0/max_t:5280us/max_retry:31], bt_slot_reg:0-TU, bt_scan_rx_low_pri:0
 [tdma_policy]   : type:0, rx_flow_ctrl:0, tx_pause:0, wl_toggle_n:0, leak_n:0, ext_ctrl:0, policy_type:0
 [slot_list]     :   OFF[100/0xe5555555/0],   B2W[005/0xea5a5a5a/1],    W1[070/0xea5a5a5a/1],    W2[015/0xea5a5a5a/1],   W2B[015/0xea5a5a5a/1]
 [slot_list]     :    B1[250/0xe5555555/0],    B2[007/0xea5a5a5a/0],    B3[005/0xe5555555/0],    B4[050/0xe5555555/0],    LK[020/0xea5a5a5a/1]
 [slot_list]     :   BLK[500/0x55555555/0],   E2G[000/0xea5a5a5a/0],   E5G[000/0xffffffff/1],   EBT[000/0xe5555555/0], ENULL[000/0xaaaaaaaa/1]
 [slot_list]     :   WLK[250/0xea5a5a5a/0], W1FDD[050/0xffffffff/1], B1FDD[050/0xffffdfff/1]
========== [HW Status] ==========
 [scoreboard]    : WL->BT:0x00004083(cnt:443), BT->WL:0x4001051b(total:219, bt_update:14)
 [reg]           : 0_0xda24=0xffffffff, 0_0xda28=0xffffffff, 0_0xda2c=0xf0ffffff, 0_0xda30=0x00000008, 0_0xda4c=0x0000000d, 0_0xda10=0x00000100
 [reg]           : 0_0xda20=0x00000002, 0_0xda34=0x00000100, 0_0xcef4=0x00000000, 0_0x8424=0x00000000, 0_0xd200=0x00000000, 0_0xd220=0x00000000
 [reg]           : 1_0x0980=0x10182250, 1_0x4738=0x8325c500, 1_0x4688=0x1a10ff04, 1_0x4694=0x04fa2a2a
========== [Statistics] ==========
 [summary]       : h2c_cnt=886(fail:1), c2h_cnt=0
 [notify_cnt]    : total=821, show_coex_info=162, power_on=0, init_coex=1, power_off=0, radio_state=398, role_info=2, wl_rfk=5, wl_sta=238
 [notify_cnt]    : scan_start=2, scan_finish=2, switch_band=2, special_pkt=5, timer=4, control=0, customerize=0sam. 05 août 2023 10:18:38 CEST

Second is the output right before the previous one, when power_save was disabled and no issues were present.

=========================================
WL FW / BT FW           0.29.29.1 / NA
manual                  0
=========================================

 [bt_info]       : raw_data[49 00 c5 00 04 7f] (type:auto/cnt:1576/same:1)
=========================================
========== [BTC COEX INFO (1)] ==========
 [coex_version]  : Coex:7.0.1(branch:19), WL_FW_coex:7.8.0(branch:29)(Match, desired:5.5.0), BT_FW_coex:7(Match, desired:5)
 [sub_module]    : WL_FW:0.29.29.1, BT_FW:0x1fc6b20f(patch)
 [hw_info]       : cv:1, rfe_type:0x1, ant_iso:10, ant_pg:2, 3rd_coex:0, dbcc:0, tx_num:2, rx_num:2
========== [WL Status] ==========
 [status]        : link_mode:9, rf_off:0, power_save:0, scan:N(band:1/phy_map:0x0), connecting:N, roam:N, 4way:N, init_ok:Y
 [port_0]        : role=1(phy-0), connect=2(client_cnt=-1), mode=3, center_ch=42, bw=2, mac_id=0, max_tx_time=0us, max_tx_retry=0
 [port_0]        : rssi=-59dBm(51), busy=0, dir=DL, tx[rate:260/busy_level:0], rx[rate:280/busy_level:0/drop:0]
========== [BT Status] ==========
 [status]        : enable:Y, btg:Y, connect:Y, igno_wl:N, mailbox_avl:Y, rfk_state:0x0
 [profile]       : profile:A2DP, multi-link:N, role:Master, ble-connect:N, CQDDR:N, A2DP_active:Y, PAN_active:N
 [link]          : rssi:-53dBm, tx_rate:3M,  acl_busy!! afh_map[ffff_ffff_ffff_f3f1_fffe], wl_ch_map[en:0/ch:0/bw:32]
 [stat_cnt]      : retry:0, relink:1, rate_chg:11, reinit:0, reenable:1, role-switch:0, afh:0, inq_page:1(inq:0/page:1), igno_wl:1
 [A2DP]          : type:Legacy, bit-pool:63, flush-time:0, vid:0xa, Dev-name:0x2d4857, sut_pwr:0, golden-rx:0
 [bt_info]       : raw_data[49 00 c5 00 04 7f] (type:auto/cnt:1576/same:1)
 [trx_req_cnt]   : Hi-rx = 178, Hi-tx = 0, Lo-rx = 546, Lo-tx = 546 (bt_polut_wl_tx = 0)(BG:0-0/INIT:0-0/LE:0-0)
========== [Mechanism Status (Auto)] ==========
 [status]        : type:shared, reason:NTFY_WL_STA(), action:WL_5G(), ant_path:5, run_cnt:2219
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> NTFY_WL_STA         -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> NTFY_WL_STA         -> WL_5G          -> OFF_EQ0      
 [dm_flag]       : wl_only:0, bt_only:0, igno_bt:0, free_run:0, wl_ps_ctrl:0, wl_mimo_ps:0, leak_ap:0, fw_offload:N
 [trx_ctrl]      : wl_rssi_lvl:3, para_lvl:0, wl_tx_pwr:orig, wl_rx_lvl:0, bt_tx_pwr_dec:0, bt_rx_lna:7(Ori-tbl), wl_btg_rx:0
 [dm_ctrl]       : wl_tx_limit[en:0/max_t:5280us/max_retry:31], bt_slot_reg:0-TU, bt_scan_rx_low_pri:0
 [tdma_policy]   : type:0, rx_flow_ctrl:0, tx_pause:0, wl_toggle_n:0, leak_n:0, ext_ctrl:0, policy_type:2
 [slot_list]     :   OFF[100/0xffffffff/1],   B2W[005/0xea5a5a5a/1],    W1[070/0xea5a5a5a/1],    W2[015/0xea5a5a5a/1],   W2B[015/0xea5a5a5a/1]
 [slot_list]     :    B1[250/0xe5555555/0],    B2[007/0xea5a5a5a/0],    B3[005/0xe5555555/0],    B4[050/0xe5555555/0],    LK[020/0xea5a5a5a/1]
 [slot_list]     :   BLK[500/0x55555555/0],   E2G[000/0xea5a5a5a/0],   E5G[000/0xffffffff/1],   EBT[000/0xe5555555/0], ENULL[000/0xaaaaaaaa/1]
 [slot_list]     :   WLK[250/0xea5a5a5a/0], W1FDD[050/0xffffffff/1], B1FDD[050/0xffffdfff/1]
========== [HW Status] ==========
 [scoreboard]    : WL->BT:0x00004083(cnt:443), BT->WL:0x4001051b(total:219, bt_update:14)
 [gnt_status]    : pta_owner:WL, phy-0[gnt_wl:SW-1/gnt_bt:HW-1], phy-1[gnt_wl:SW-1/gnt_bt:HW-1]
 [reg]           : 0_0xda24=0xffffffff, 0_0xda28=0xffffffff, 0_0xda2c=0xf0ffffff, 0_0xda30=0x00000008, 0_0xda4c=0x0000000d, 0_0xda10=0x00000100
 [reg]           : 0_0xda20=0x00000002, 0_0xda34=0x00000100, 0_0xcef4=0x00000000, 0_0x8424=0x00000000, 0_0xd200=0x00000000, 0_0xd220=0x00000000
 [reg]           : 1_0x0980=0x10182250, 1_0x4738=0x8325c500, 1_0x4688=0x1a10ff04, 1_0x4694=0x04fa2a2a
========== [Statistics] ==========
 [summary]       : h2c_cnt=884(fail:1, fw_recv:1083), c2h_cnt=0(fw_send:2137, len:235), rpt_cnt=549(fw_send:548), rpt_map=0x64
 [mailbox]       : send_ok:192, send_fail:0, recv:48257, A2DP_empty:46499(stop:0, tx:181882, ack:170362, nack:2061)
 [RFK/LPS]       : wl_rfk[req:5/go:5/reject:0/tout:0], bt_rfk[req:0], AOAC[RF_on:2031/RF_off:2031]
 [notify_cnt]    : total=818, show_coex_info=160, power_on=0, init_coex=1, power_off=0, radio_state=397, role_info=2, wl_rfk=5, wl_sta=238
 [notify_cnt]    : scan_start=2, scan_finish=2, switch_band=2, special_pkt=5, timer=4, control=0, customerize=0sam. 05 août 2023 10:18:36 CEST

Finally, the output of the second terminal about 10 seconds after the issue started (I don't know if that's useful or not)

=========================================
WL FW / BT FW           0.29.29.1 / NA
manual                  0
=========================================

 [bt_info]       : raw_data[49 00 c7 00 04 7f] (type:auto/cnt:1582/same:1)
=========================================
========== [BTC COEX INFO (1)] ==========
 [coex_version]  : Coex:7.0.1(branch:19), WL_FW_coex:7.8.0(branch:29)(Match, desired:5.5.0), BT_FW_coex:7(Match, desired:5)
 [sub_module]    : WL_FW:0.29.29.1, BT_FW:0x1fc6b20f(patch)
 [hw_info]       : cv:1, rfe_type:0x1, ant_iso:10, ant_pg:2, 3rd_coex:0, dbcc:0, tx_num:2, rx_num:2
========== [WL Status] ==========
 [status]        : link_mode:9, rf_off:0, power_save:1, scan:N(band:1/phy_map:0x0), connecting:N, roam:N, 4way:N, init_ok:Y
 [port_0]        : role=1(phy-0), connect=2(client_cnt=-1), mode=3, center_ch=42, bw=2, mac_id=0, max_tx_time=0us, max_tx_retry=0
 [port_0]        : rssi=-63dBm(47), busy=0, dir=DL, tx[rate:274/busy_level:0], rx[rate:277/busy_level:0/drop:0]
========== [BT Status] ==========
 [status]        : enable:Y, btg:Y, connect:Y, igno_wl:N, mailbox_avl:Y, rfk_state:0x0
 [profile]       : profile:A2DP, multi-link:N, role:Master, ble-connect:N, CQDDR:N, A2DP_active:Y, PAN_active:N
 [link]          : rssi:-51dBm, tx_rate:3M,  acl_busy!! afh_map[ffff_ffff_ffff_f3f1_fffe], wl_ch_map[en:0/ch:0/bw:32]
 [stat_cnt]      : retry:0, relink:1, rate_chg:11, reinit:0, reenable:1, role-switch:0, afh:0, inq_page:1(inq:0/page:1), igno_wl:1
 [A2DP]          : type:Legacy, bit-pool:63, flush-time:0, vid:0xa, Dev-name:0x2d4857, sut_pwr:0, golden-rx:0
 [bt_info]       : raw_data[49 00 c7 00 04 7f] (type:auto/cnt:1582/same:1)
 [trx_req_cnt]   : Hi-rx = 178, Hi-tx = 0, Lo-rx = 546, Lo-tx = 546 (bt_polut_wl_tx = 0)(BG:0-0/INIT:0-0/LE:0-0)
========== [Mechanism Status (Auto)] ==========
 [status]        : type:shared, reason:NTFY_RADIO_STATE(), action:WL_OFF(), ant_path:5, run_cnt:2236
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      -> UPDATE_BT_INFO      -> WL_5G          -> OFF_EQ0      
 [dm_steps]      : -> NTFY_WL_STA         -> WL_5G          -> OFF_EQ0      -> NTFY_RADIO_STATE    -> WL_OFF         -> OFF_BT       
 [dm_steps]      : -> NTFY_RADIO_STATE    -> WL_5G          -> OFF_EQ0      -> NTFY_RADIO_STATE    -> WL_OFF         -> OFF_BT       
 [dm_flag]       : wl_only:0, bt_only:0, igno_bt:1, free_run:0, wl_ps_ctrl:0, wl_mimo_ps:0, leak_ap:0, fw_offload:N
 [trx_ctrl]      : wl_rssi_lvl:3, para_lvl:0, wl_tx_pwr:orig, wl_rx_lvl:0, bt_tx_pwr_dec:0, bt_rx_lna:7(Ori-tbl), wl_btg_rx:0
 [dm_ctrl]       : wl_tx_limit[en:0/max_t:5280us/max_retry:31], bt_slot_reg:0-TU, bt_scan_rx_low_pri:0
 [tdma_policy]   : type:0, rx_flow_ctrl:0, tx_pause:0, wl_toggle_n:0, leak_n:0, ext_ctrl:0, policy_type:0
 [slot_list]     :   OFF[100/0xe5555555/0],   B2W[005/0xea5a5a5a/1],    W1[070/0xea5a5a5a/1],    W2[015/0xea5a5a5a/1],   W2B[015/0xea5a5a5a/1]
 [slot_list]     :    B1[250/0xe5555555/0],    B2[007/0xea5a5a5a/0],    B3[005/0xe5555555/0],    B4[050/0xe5555555/0],    LK[020/0xea5a5a5a/1]
 [slot_list]     :   BLK[500/0x55555555/0],   E2G[000/0xea5a5a5a/0],   E5G[000/0xffffffff/1],   EBT[000/0xe5555555/0], ENULL[000/0xaaaaaaaa/1]
 [slot_list]     :   WLK[250/0xea5a5a5a/0], W1FDD[050/0xffffffff/1], B1FDD[050/0xffffdfff/1]
========== [HW Status] ==========
 [scoreboard]    : WL->BT:0x00004083(cnt:449), BT->WL:0x4001051b(total:223, bt_update:14)
 [reg]           : 0_0xda24=0xffffffff, 0_0xda28=0xffffffff, 0_0xda2c=0xf0ffffff, 0_0xda30=0x00000008, 0_0xda4c=0x0000000d, 0_0xda10=0x00000100
 [reg]           : 0_0xda20=0x00000002, 0_0xda34=0x00000100, 0_0xcef4=0x00000000, 0_0x8424=0x00000000, 0_0xd200=0x00000000, 0_0xd220=0x00000000
 [reg]           : 1_0x0980=0x10182250, 1_0x4738=0x8325c500, 1_0x4688=0x1a10ff04, 1_0x4694=0x04fa2a2a
========== [Statistics] ==========
 [summary]       : h2c_cnt=904(fail:1), c2h_cnt=0
 [notify_cnt]    : total=841, show_coex_info=172, power_on=0, init_coex=1, power_off=0, radio_state=406, role_info=2, wl_rfk=5, wl_sta=240
 [notify_cnt]    : scan_start=2, scan_finish=2, switch_band=2, special_pkt=5, timer=4, control=0, customerize=0sam. 05 août 2023 10:18:48 CEST

I hope this contains all the informations you need.

[lwfinger]

The driver would load the uncompressed version first, thus the .zst stuff would have been ignored, but deleting it did not hurt.

I sent your logs upstream and will let you know when I hear anything.

At least you know how to disable power_save when you want to use BT.

[lwfinger]

Please do two more things for me. Run the command 'lsusb' and post the output. In addition, run the command 'sudo dmesg > dmesg.txt' and attach dmesg.txt to this issue. Thanks.

[MK73DS]

Here's the output of lsusb :

$ lsusb
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 04f2:b758 Chicony Electronics Co., Ltd Integrated Camera
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0fce:320d Sony Ericsson Mobile Communications AB XQ-BC52
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:4853 Realtek Semiconductor Corp. Bluetooth Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And here is the dmesg : dmesg.txt

[lwfinger]

I think I know what your problem is - the system is using the wrong BT driver.

BT will use a generic driver unless your specific device is located in a "blacklist" contained within the driver. Having your USB ID in that badly-named table will blacklist the generic driver and load a specific driver. The IDs for your device are not in that table, thus the driver for Realtek BT devices is not loaded. That will be fixed, but it will take a while for the fix to propagate through the system.

As a temporary fix, 'git clone https://GitHub.com'lwfinger/rtw89-BT.git', 'cd rtw89-BT', make', and 'sudo make install'. That will install a BT driver that will recognize your device. After rebooting, rerun the power_save on/off part of the test. If that still fails, then run the script that dumps btc_info. Send me the output when on and off, and a new dmesg.txt.

[MK73DS]

I can't compile the BT driver, I get this error. Maybe I'm missing a dependency but I checked the readme and it seems I have everything.

make -C /lib/modules/6.4.8-arch1-1/build M=/home/me/rtw89-BT modules
  CC [M]  /home/me/rtw89-BT/btusb.o
/home/me/rtw89-BT/btusb.c: In function ‘btusb_intel_diagnostics’:
/home/me/rtw89-BT/btusb.c:2436:26: error: ‘INTEL_TLV_TYPE_ID’ undeclared (first use in this function)
 2436 |         if (tlv->type != INTEL_TLV_TYPE_ID)
      |                          ^~~~~~~~~~~~~~~~~
/home/me/rtw89-BT/btusb.c:2436:26: note: each undeclared identifier is reported only once for each function it appears in
/home/me/rtw89-BT/btusb.c:2440:14: error: ‘INTEL_TLV_SYSTEM_EXCEPTION’ undeclared (first use in this function)
 2440 |         case INTEL_TLV_SYSTEM_EXCEPTION:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~~
/home/me/rtw89-BT/btusb.c:2441:14: error: ‘INTEL_TLV_FATAL_EXCEPTION’ undeclared (first use in this function)
 2441 |         case INTEL_TLV_FATAL_EXCEPTION:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/me/rtw89-BT/btusb.c:2442:14: error: ‘INTEL_TLV_DEBUG_EXCEPTION’ undeclared (first use in this function); did you mean ‘INTEL_TLV_DEBUG_LOCK’?
 2442 |         case INTEL_TLV_DEBUG_EXCEPTION:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~
      |              INTEL_TLV_DEBUG_LOCK
/home/me/rtw89-BT/btusb.c:2443:14: error: ‘INTEL_TLV_TEST_EXCEPTION’ undeclared (first use in this function)
 2443 |         case INTEL_TLV_TEST_EXCEPTION:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~
/home/me/rtw89-BT/btusb.c: In function ‘btusb_setup_realtek’:
/home/me/rtw89-BT/btusb.c:2582:13: error: implicit declaration of function ‘btrealtek_test_flag’; did you mean ‘btintel_test_flag’? [-Werror=implicit-function-declaration]
 2582 |         if (btrealtek_test_flag(data->hdev, REALTEK_ALT6_CONTINUOUS_TX_CHIP))
      |             ^~~~~~~~~~~~~~~~~~~
      |             btintel_test_flag
/home/me/rtw89-BT/btusb.c:2582:45: error: ‘REALTEK_ALT6_CONTINUOUS_TX_CHIP’ undeclared (first use in this function)
 2582 |         if (btrealtek_test_flag(data->hdev, REALTEK_ALT6_CONTINUOUS_TX_CHIP))
      |                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/me/rtw89-BT/btusb.c: In function ‘btusb_probe’:
/home/me/rtw89-BT/btusb.c:4238:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct btrealtek_data’
 4238 |                 priv_size += sizeof(struct btrealtek_data);
      |                                     ^~~~~~
/home/me/rtw89-BT/btusb.c:4321:23: error: too many arguments to function ‘btintel_configure_setup’
 4321 |                 err = btintel_configure_setup(hdev, btusb_driver.name);
      |                       ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/me/rtw89-BT/btusb.c:26:
/home/me/rtw89-BT/btintel.h:209:5: note: declared here
  209 | int btintel_configure_setup(struct hci_dev *hdev);
      |     ^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252: /home/me/rtw89-BT/btusb.o] Error 1
make[1]: *** [Makefile:2032: /home/me/rtw89-BT] Error 2
make: *** [Makefile:32: all] Error 2

If this is just a temporary fix before the ID of my device is in the blacklist table, then I'm okay with disabling the power saving mode when I use bluetooth for the time being.

[lwfinger]

The code would build on kernel 6.5, but not with 6.4. I have fixed that issue.

I want you to test this fix to see if it is correct, or if we have a problem with the Realtek wifi and/or BT driver.