Created attachment 304388 [details] dmesg_ath11k_debug_output Hello, We are trying to connect 2x QCN9074 together (one as AP, the other as client). Using Ubuntu 22.04 hwe 5.19 generic kernel allows to pair both units in 800.11ac 80MHz only. Any other combinations of 802.11ax or ac/ax with 160MHz bandwidth does not work. The client kernel freezes when associating to QCN9074 AP without specific logs and requires reboot. I'll post another bug once I can get more logs. Since quite some patches came through since 5.19 - some of them related to 160MHz bandwidth. I tried multiple newer mainline kernels without success and usually the same error. Building kernel from latest ath master branch: 6.4.0-rc4-wt-ath+ gives the following dmesg output: [ 353.587072] ath11k_pci 0000:04:00.0: BAR 0: assigned [mem 0xa4200000-0xa43fffff 64bit] [ 353.587180] ath11k_pci 0000:04:00.0: MSI vectors: 1 [ 353.587186] ath11k_pci 0000:04:00.0: qcn9074 hw1.0 [ 353.741799] mhi mhi0: Requested to power ON [ 353.741806] mhi mhi0: Power on setup success [ 353.912479] mhi mhi0: Wait for device to enter SBL or Mission mode [ 354.007221] ath11k_pci 0000:04:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [ 354.007225] ath11k_pci 0000:04:00.0: fw_version 0x2403072e fw_build_timestamp 2021-06-06 23:27 fw_build_id [ 355.333791] ath11k_pci 0000:04:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems [ 355.729786] ath11k_pci 0000:04:00.0 wlp4s0: renamed from wlan0 [ 358.960477] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 36866 [ 358.960481] ath11k_pci 0000:04:00.0: failed to send WMI_STA_POWERSAVE_PARAM_CMDID [ 358.960484] ath11k_pci 0000:04:00.0: could not set uapsd params -105 [ 358.960485] ath11k_pci 0000:04:00.0: failed to set sta uapsd: -105 [ 362.032472] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 90113 [ 362.032477] ath11k_pci 0000:04:00.0: failed to send WMI_REQUEST_STATS cmd [ 362.032479] ath11k_pci 0000:04:00.0: could not request fw stats (-105) [ 362.032480] ath11k_pci 0000:04:00.0: failed to request fw pdev stats: -105 [ 365.104479] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 20482 [ 365.104483] ath11k_pci 0000:04:00.0: failed to submit WMI_VDEV_DELETE_CMDID [ 365.104485] ath11k_pci 0000:04:00.0: failed to delete WMI vdev 0: -105 [ 365.104487] ath11k_pci 0000:04:00.0: failed to delete vdev 0: -105 [ 368.176472] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 16387 [ 368.176476] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 368.176479] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 [ 371.248474] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 16387 [ 371.248478] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 371.248480] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 [ 374.320393] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 16387 [ 374.320397] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 374.320400] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 Both PCs are Intel x86 (same bug for AMD). We have multiple references of QCN9074 that we tested: - Sparklan WPEQ-405AX (our preferred one, as they are the only vendor I know that went through FCC certification) - This unit can associate to APs only with the firmware Sparklan provided. Otherwise, link strength is reported low and barely no APs are listed after scanning. - Emwicon WMX7406 - has better performances with Sparklan's vendor FW. Works with ath11k-firmware 2.7.0.1 but shows lower TX mostly. Tested FW (non exhaustive): # ath11k-firmware 2.5.0.1 823915206101779f8cab6b89066e1040 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin 668f53050a92db5b4281ae5f26c7e35d /lib/firmware/ath11k/QCN9074/hw1.0/board-2.bin fcca36959c5f56f9f0fb7015083dc806 /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin # ath11k-firmware 2.7.0.1 465d0a063d049f7e4b79d267a035c6c7 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin 668f53050a92db5b4281ae5f26c7e35d /lib/firmware/ath11k/QCN9074/hw1.0/board-2.bin ad8fafb9c1deab744c972469be916e72 /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin # Vendor firmware 1e88ff2e2b5bcf7f130397cb5b21ef39 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin 7b3ce8686713a724946466ec1fefc2f4 /lib/firmware/ath11k/QCN9074/hw1.0/board.bin d0a6f7ccd52f9e3886f0bc96309f7b9a /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin Attached dmesg log with ath11k debug_mask=0xFFFF and lspci. Thank you
Created attachment 304389 [details] lspci
(In reply to Tanguy S. from comment #0) > Created attachment 304388 [details] > dmesg_ath11k_debug_output > > Hello, > > We are trying to connect 2x QCN9074 together (one as AP, the other as > client). > > Using Ubuntu 22.04 hwe 5.19 generic kernel allows to pair both units in > 800.11ac 80MHz only. Any other combinations of 802.11ax or ac/ax with 160MHz > bandwidth does not work. The client kernel freezes when associating to > QCN9074 AP without specific logs and requires reboot. I'll post another bug > once I can get more logs. > > Since quite some patches came through since 5.19 - some of them related to > 160MHz bandwidth. I tried multiple newer mainline kernels without success > and usually the same error. > > Building kernel from latest ath master branch: 6.4.0-rc4-wt-ath+ gives the > following dmesg output: > > [ 353.587072] ath11k_pci 0000:04:00.0: BAR 0: assigned [mem > 0xa4200000-0xa43fffff 64bit] > [ 353.587180] ath11k_pci 0000:04:00.0: MSI vectors: 1 > [ 353.587186] ath11k_pci 0000:04:00.0: qcn9074 hw1.0 > [ 353.741799] mhi mhi0: Requested to power ON > [ 353.741806] mhi mhi0: Power on setup success > [ 353.912479] mhi mhi0: Wait for device to enter SBL or Mission mode > [ 354.007221] ath11k_pci 0000:04:00.0: chip_id 0x0 chip_family 0x0 board_id > 0xff soc_id 0xffffffff > [ 354.007225] ath11k_pci 0000:04:00.0: fw_version 0x2403072e > fw_build_timestamp 2021-06-06 23:27 fw_build_id > [ 355.333791] ath11k_pci 0000:04:00.0: leaving PCI ASPM disabled to avoid > MHI M2 problems > [ 355.729786] ath11k_pci 0000:04:00.0 wlp4s0: renamed from wlan0 > [ 358.960477] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 36866 > [ 358.960481] ath11k_pci 0000:04:00.0: failed to send > WMI_STA_POWERSAVE_PARAM_CMDID > [ 358.960484] ath11k_pci 0000:04:00.0: could not set uapsd params -105 > [ 358.960485] ath11k_pci 0000:04:00.0: failed to set sta uapsd: -105 > [ 362.032472] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 90113 > [ 362.032477] ath11k_pci 0000:04:00.0: failed to send WMI_REQUEST_STATS cmd > [ 362.032479] ath11k_pci 0000:04:00.0: could not request fw stats (-105) > [ 362.032480] ath11k_pci 0000:04:00.0: failed to request fw pdev stats: -105 > [ 365.104479] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 20482 > [ 365.104483] ath11k_pci 0000:04:00.0: failed to submit > WMI_VDEV_DELETE_CMDID > [ 365.104485] ath11k_pci 0000:04:00.0: failed to delete WMI vdev 0: -105 > [ 365.104487] ath11k_pci 0000:04:00.0: failed to delete vdev 0: -105 > [ 368.176472] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 16387 > [ 368.176476] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd > [ 368.176479] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 > [ 371.248474] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 16387 > [ 371.248478] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd > [ 371.248480] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 > [ 374.320393] ath11k_pci 0000:04:00.0: ce desc not available for wmi > command 16387 > [ 374.320397] ath11k_pci 0000:04:00.0: failed to send WMI_PDEV_SET_PARAM cmd > [ 374.320400] ath11k_pci 0000:04:00.0: failed to enable PMF QOS: (-105 > > Both PCs are Intel x86 (same bug for AMD). We have multiple references of > QCN9074 that we tested: > - Sparklan WPEQ-405AX (our preferred one, as they are the only vendor I know > that went through FCC certification) - This unit can associate to APs only > with the firmware Sparklan provided. Otherwise, link strength is reported > low and barely no APs are listed after scanning. > - Emwicon WMX7406 - has better performances with Sparklan's vendor FW. Works > with ath11k-firmware 2.7.0.1 but shows lower TX mostly. > > Tested FW (non exhaustive): > # ath11k-firmware 2.5.0.1 > 823915206101779f8cab6b89066e1040 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin > 668f53050a92db5b4281ae5f26c7e35d > /lib/firmware/ath11k/QCN9074/hw1.0/board-2.bin > fcca36959c5f56f9f0fb7015083dc806 /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin > > # ath11k-firmware 2.7.0.1 > 465d0a063d049f7e4b79d267a035c6c7 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin > 668f53050a92db5b4281ae5f26c7e35d > /lib/firmware/ath11k/QCN9074/hw1.0/board-2.bin > ad8fafb9c1deab744c972469be916e72 /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin > > # Vendor firmware > 1e88ff2e2b5bcf7f130397cb5b21ef39 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin > 7b3ce8686713a724946466ec1fefc2f4 > /lib/firmware/ath11k/QCN9074/hw1.0/board.bin > d0a6f7ccd52f9e3886f0bc96309f7b9a /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin > > > Attached dmesg log with ath11k debug_mask=0xFFFF and lspci. > > Thank you Can you bisect between v5.19 and v6.4-rc4 please?
Here is the log for git bisect on linux stable tree. git bisect start '--' 'drivers/bus/mhi' 'drivers/soc/qcom' 'drivers/net/wireless/ath/ath11k' 'net/qrtr' 'net/mac80211' # status: waiting for both good and bad commits # bad: [830b3c68c1fb1e9176028d02ef86f3cf76aa2476] Linux 6.1 git bisect bad 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 # status: waiting for good commit(s), bad commit known # good: [ad6c047b2e2f276568ab504deff51d711420b4d3] Linux 6.0.19 git bisect good ad6c047b2e2f276568ab504deff51d711420b4d3 # good: [076d5b10b22aab9cf021912798ef105699f9fc9c] wifi: ath11k: Fix QCN9074 firmware boot on x86 git bisect good 076d5b10b22aab9cf021912798ef105699f9fc9c # good: [4fe89d07dcc2804c8b562f6c7896a45643d34b2f] Linux 6.0 git bisect good 4fe89d07dcc2804c8b562f6c7896a45643d34b2f # bad: [6cf5e9066dd3332cf4c77ea95a116f70e7f9acf7] Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git git bisect bad 6cf5e9066dd3332cf4c77ea95a116f70e7f9acf7 # good: [b38d15294ffe9b87b092d310f321e2d0a9d2b3b2] Merge remote-tracking branch 'wireless/main' into wireless-next git bisect good b38d15294ffe9b87b092d310f321e2d0a9d2b3b2 # bad: [a20ed60bb357776301c2dad7b4a4f0db97e143e9] wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected git bisect bad a20ed60bb357776301c2dad7b4a4f0db97e143e9 # good: [876eb84882a8b2fc4036e735a2de52141aebb6a5] wifi: ath11k: implement SRAM dump debugfs interface git bisect good 876eb84882a8b2fc4036e735a2de52141aebb6a5 # bad: [3fecca0e7de885c71cf28065015832b78023aa6f] wifi: ath11k: Fix miscellaneous spelling errors git bisect bad 3fecca0e7de885c71cf28065015832b78023aa6f # bad: [13aa2fb692d3717767303817f35b3e650109add3] wifi: ath11k: Enable threaded NAPI git bisect bad 13aa2fb692d3717767303817f35b3e650109add3 # good: [43e7c3505ec70db3d3c6458824d5fa40f62e3e7b] wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register() git bisect good 43e7c3505ec70db3d3c6458824d5fa40f62e3e7b # first bad commit: [13aa2fb692d3717767303817f35b3e650109add3] wifi: ath11k: Enable threaded NAPI Info on commit: commit 13aa2fb692d3717767303817f35b3e650109add3 Author: Manikanta Pubbisetty <quic_mpubbise@quicinc.com> Date: Mon Sep 5 12:48:03 2022 +0530 wifi: ath11k: Enable threaded NAPI Enable threaded NAPI on all ath11k targets. Unlike traditional NAPI poll which runs in softirq context and on the core which scheduled the NAPI, threaded NAPI makes use of kernel threads which are under direct control of the scheduler and helps in balancing the NAPI processing load across multiple CPUs thereby improving throughput. In the case of WCN6750, enabling threaded NAPI has improved 160 MHz RX throughput by nearly 400 Mbps. Similar gains can be expected on other ath11k devices as well. Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1 Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com> Link: https://lore.kernel.org/r/20220905071805.31625-2-quic_mpubbise@quicinc.com diff --git a/drivers/net/wireless/ath/ath11k/ahb.c b/drivers/net/wireless/ath/ath11k/ahb.c index 31e9cf31457a..2bf709b0b12a 100644 --- a/drivers/net/wireless/ath/ath11k/ahb.c +++ b/drivers/net/wireless/ath/ath11k/ahb.c @@ -359,6 +359,7 @@ static void ath11k_ahb_ext_irq_enable(struct ath11k_base *ab) struct ath11k_ext_irq_grp *irq_grp = &ab->ext_irq_grp[i]; if (!irq_grp->napi_enabled) { + dev_set_threaded(&irq_grp->napi_ndev, true); napi_enable(&irq_grp->napi); irq_grp->napi_enabled = true; } diff --git a/drivers/net/wireless/ath/ath11k/pcic.c b/drivers/net/wireless/ath/ath11k/pcic.c index 926b0cb7b061..74ed99af833b 100644 --- a/drivers/net/wireless/ath/ath11k/pcic.c +++ b/drivers/net/wireless/ath/ath11k/pcic.c @@ -459,6 +459,7 @@ void ath11k_pcic_ext_irq_enable(struct ath11k_base *ab) struct ath11k_ext_irq_grp *irq_grp = &ab->ext_irq_grp[i]; if (!irq_grp->napi_enabled) { + dev_set_threaded(&irq_grp->napi_ndev, true); napi_enable(&irq_grp->napi); irq_grp->napi_enabled = true; } I will try building ath master tree without this commit and see if I it works.
Interestingly, in approximately 1/20 reboots the bug would not appear. Which makes the bisection a little more tedious.
Reverting this commit allows to fix the issue. However, would be interesting to understand why, as it would still be helpful to have an extra 400Mbps in RX.
I'm experiencing the same problem, I'm using WL3000HX from compex with Qualcomm Atheros QCN9074 chipset. I'm using OpenWRT with kernel version 5.15.118 on the ARM platform. I have compared it with the same wifi network card and the same software environment (openWRT kernel 5.15.118) on Intel X86_64 and I have not observed these problems. I have also tried it with the most recent version with kernel 6.1 on ARM (RaspberryPi CM4) and of course I see the same problems. On certain occasions it works 5/20 (powerOff/PowerOn). this is my dmesg [ 0.172101] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges: [ 0.172133] brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff] [ 0.172178] brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000 [ 0.172219] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x007fffffff -> 0x0000000000 [ 0.229659] brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC) [ 0.229833] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00 [ 0.229853] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.229872] pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff]) [ 0.229924] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400 [ 0.230009] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.233506] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.233658] pci 0000:01:00.0: [17cb:1104] type 00 class 0x028000 [ 0.233702] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 0.233862] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 0.233921] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link) [ 0.237288] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.237329] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6001fffff] [ 0.237353] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x6001fffff 64bit] [ 0.237385] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.237401] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6001fffff] [ 0.237605] pcieport 0000:00:00.0: enabling device (0000 -> 0002) [ 0.237734] pcieport 0000:00:00.0: PME: Signaling with IRQ 44 [ 0.238030] pcieport 0000:00:00.0: AER: enabled with IRQ 44 [ 5.187884] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x6001fffff 64bit] [ 5.196015] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002) [ 5.202407] ath11k_pci 0000:01:00.0: MSI vectors: 1 [ 5.207286] ath11k_pci 0000:01:00.0: qcn9074 hw1.0 [ 5.212079] ath11k_pci 0000:01:00.0: FW memory mode: 2 [ 5.653126] ath11k_pci 0000:01:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [ 5.661967] ath11k_pci 0000:01:00.0: fw_version 0x290c8569 fw_build_timestamp 2023-03-25 06:50 fw_build_id [ 7.055753] ath11k_pci 0000:01:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems [ 7.417851] ath11k_pci 0000:01:00.0: htt event 48 not handled [ 126.580689] ath11k_pci 0000:01:00.0: ce desc not available for wmi command 36866 [ 126.588126] ath11k_pci 0000:01:00.0: failed to send WMI_STA_POWERSAVE_PARAM_CMDID [ 126.595651] ath11k_pci 0000:01:00.0: could not set uapsd params -105 [ 126.602038] ath11k_pci 0000:01:00.0: failed to set sta uapsd: -105 [ 129.690755] ath11k_pci 0000:01:00.0: ce desc not available for wmi command 90113 [ 129.698192] ath11k_pci 0000:01:00.0: failed to send WMI_REQUEST_STATS cmd [ 129.705012] ath11k_pci 0000:01:00.0: could not request fw stats (-105) [ 129.711561] ath11k_pci 0000:01:00.0: failed to request fw pdev stats: -105 [ 132.730822] ath11k_pci 0000:01:00.0: ce desc not available for wmi command 90113 [ 132.738256] ath11k_pci 0000:01:00.0: failed to send WMI_REQUEST_STATS cmd [ 132.745081] ath11k_pci 0000:01:00.0: could not request fw stats (-105) [ 132.751629] ath11k_pci 0000:01:00.0: failed to request fw pdev stats: -105 [ 135.770877] ath11k_pci 0000:01:00.0: ce desc not available for wmi command 90113 [ 135.778299] ath11k_pci 0000:01:00.0: failed to send WMI_REQUEST_STATS cmd [ 135.785110] ath11k_pci 0000:01:00.0: could not request fw stats (-105) [ 135.791656] ath11k_pci 0000:01:00.0: failed to request fw pdev stats: -105 [ 138.810960] ath11k_pci 0000:01:00.0: ce desc not available for wmi command 90113 [ 138.818381] ath11k_pci 0000:01:00.0: failed to send WMI_REQUEST_STATS cmd [ 138.825195] ath11k_pci 0000:01:00.0: could not request fw stats (-105) [ 138.831740] ath11k_pci 0000:01:00.0: failed to request fw pdev stats: -105
I submitted the revert and will queue for v6.5: https://patchwork.kernel.org/project/linux-wireless/patch/20230720151444.2016637-1-kvalo@kernel.org/
Extremely sorry for having this missed due to incorrect mail filters on my machine. I have looked the logs attached to the buganizer. The issue from the logs looks like it is happening during the boot. Generally, issues like these "ce desc not available for wmi command" occur when there is no room in the copy engine pipe for driver to enqueue the command to the firmware and in many cases these would have happen when firmware is reaping the ring slowly. It is puzzling to know that thread NAPI is causing this and reverting this got the issue fixed. NAPI generally acts on the RX rings and has nothing to do with the TX. This issue is seen just with the kernel upgrade alone? Or firmware has also been upgraded? Meanwhile, I'll try to repro the issue on my local setup and try to root cause the problem. Pls let me know the firmware version that has been used for testing.
We have attempted to reproduce the problem several times but have not been able to repro it. Can you pls provide the commit SHA of ath.git master branch where you saw this problem? Also, pls provide the firmware version used. It will be of great help.
Forgot to add one more point, the ath.git RC4 kernel that we tested has threaded NAPI changes.
Hi Manikanta, Sorry, little late I am out-of-office. The error comes with the latest firmware from ath11k-firmware : ath11k-firmware 2.7.0.1 465d0a063d049f7e4b79d267a035c6c7 /lib/firmware/ath11k/QCN9074/hw1.0/amss.bin 668f53050a92db5b4281ae5f26c7e35d /lib/firmware/ath11k/QCN9074/hw1.0/board-2.bin ad8fafb9c1deab744c972469be916e72 /lib/firmware/ath11k/QCN9074/hw1.0/m3.bin Commit for the 6.4 kernel I used is : c60d15f389ef9832a8da410e438d81b10327751f Also, from the git bisect log above with latest 2.7.0 FW and commit 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 was showing the same bug. Let me know if you need anything else.
Thanks Tanguy, let me retest with this combination. Is that the device crashes only during connection? If we forget all WiFi networks and then reboot, the same bug is seen?
Seems to me that the issue happens before connection, during initialization I guess. The list of available APs is blank in that case.
Hi Tanguy S, This commit c60d15f389ef9832a8da410e438d81b10327751f is not to be seen in ath.git master branch. Have you tested this on linus linux.git? We have tried with a nearest commit in ath.git but issue doesn't seem to be reproducible. Hence planning to prepare a debug change, can u pls let us know the kernel source that you are using, I can prepare a patch on that source to be in parity. Thanks
Hi Manikanta, Have you tried with commit 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 ? This one should be on ath.git. I will get on Monday the ath.git commit for the 6.4 kernel I used. Thanks
Sure, thanks a lot.
With this commit 830b3c68c1fb1e9176028d02ef86f3cf76aa2476 and latest firmware from ath11k-firmware git, no issue is seen and able to connect successfully. [ 12.890203] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem 0xdf000000-0xdf1fffff 64bit] [ 12.893844] ath11k_pci 0000:01:00.0: MSI vectors: 16 [ 12.893855] ath11k_pci 0000:01:00.0: qcn9074 hw1.0 [ 12.917608] NET: Registered PF_QIPCRTR protocol family [ 12.959175] acpi device:0f: registered as cooling_device9 [ 13.084647] mhi mhi0: Requested to power ON [ 13.085092] mhi mhi0: Power on setup success [ 13.184903] mhi mhi0: Wait for device to enter SBL or Mission mode [ 13.285198] ath11k_pci 0000:01:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [ 13.285259] ath11k_pci 0000:01:00.0: fw_version 0x270206d0 fw_build_timestamp 2022-08-04 12:48 fw_build_id WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 [ 13.324921] systemd-udevd (314) used greatest stack depth: 12264 bytes left [ 15.181323] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0 [ 15.379658] systemd-udevd (675) used greatest stack depth: 12008 bytes left [ 18.675014] e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 18.675426] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 1069.013424] wlp1s0: authenticate with f0:61:c0:fd:fd:52 [ 1069.528122] wlp1s0: send auth to f0:61:c0:fd:fd:52 (try 1/3) [ 1069.535867] iw (1278) used greatest stack depth: 10800 bytes left [ 1069.639503] wlp1s0: send auth to f0:61:c0:fd:fd:52 (try 2/3) [ 1069.642236] wlp1s0: send auth to f0:61:c0:fd:fd:52 (try 3/3) [ 1069.644787] wlp1s0: authentication with f0:61:c0:fd:fd:52 timed out [ 1093.282720] wlp1s0: authenticate with a8:5b:f7:e6:2e:92 [ 1093.771163] wlp1s0: send auth to a8:5b:f7:e6:2e:92 (try 1/3) [ 1093.774862] wlp1s0: authenticated [ 1093.777128] wlp1s0: associate with a8:5b:f7:e6:2e:92 (try 1/3) [ 1093.780316] wlp1s0: RX AssocResp from a8:5b:f7:e6:2e:92 (capab=0x401 status=0 aid=1) [ 1093.790668] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0 link becomes ready Could you please help in running the debug patch and get me dmesg output? Since we are not able to repro, not able to make any progress on this.
Yes sure, can you provide me with the debug patch ? Could MSI vectors be an issue ? Bglowacz and I have only 1 MSI vector while you have 16.
Sure, let me prepare the patch and share it with you. >> Could MSI vectors be an issue ? Bglowacz and I have only 1 MSI vector while >> you >> have 16. Let me try this, this seems to be a good point. Meanwhile, if you don't mind testing this change, can you please test this patch?https://patchwork.kernel.org/project/linux-wireless/patch/20230601033840.2997-1-quic_bqiang@quicinc.com/? Keep the threaded NAPI changes and add the above patch. Basically, there seems to be a problem with single MSI interrupts on PCIe devices and the above patch is a fix for this. I'm hoping the above patch will be the solution for this issue because this seems to be a problem with interrupts not firing to the CPU. Can you pls give it a try? I'll make my machine boot with 1 MSI and let you know the observation. Thanks
>> Can you pls give it a try? I'll make my machine boot with 1 MSI and let you >> know the observation. Just tried with the patch but the issue remains. [ 16.240076] ath11k_pci 0000:06:00.0: BAR 0: assigned [mem 0xf7600000-0xf77fffff 64bit] [ 16.240090] ath11k_pci 0000:06:00.0: enabling device (0000 -> 0002) [ 16.241253] ath11k_pci 0000:06:00.0: MSI vectors: 1 [ 16.241258] ath11k_pci 0000:06:00.0: qcn9074 hw1.0 [ 16.580317] ath11k_pci 0000:06:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff [ 16.580322] ath11k_pci 0000:06:00.0: fw_version 0x270206d0 fw_build_timestamp 2022-08-04 12:48 fw_build_id WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 [ 17.901085] ath11k_pci 0000:06:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems [ 17.902139] ath11k_pci 0000:06:00.0: wmi wmi_ext_service_bitmap 0:0x5e45be01, 1:0x2d94d02, 2:0x1f7010c6, 3:0xee7d5c34 [ 17.902143] ath11k_pci 0000:06:00.0: wmi wmi_ext2_service__bitmap 0:0x1331b785, 1:0xa080f2a8, 2:0x021f, 3:0x0000 [ 17.902145] ath11k_pci 0000:06:00.0: wmi event service available [ 17.902398] ath11k_pci 0000:06:00.0: wmi event service ready [ 17.902466] ath11k_pci 0000:06:00.0: wmi preferred_hw_mode:0 [ 17.902469] ath11k_pci 0000:06:00.0: wmi event service ready ext [ 17.902607] ath11k_pci 0000:06:00.0: wmi event service ready ext2 [ 17.902715] ath11k_pci 0000:06:00.0: wmi cmd wmi init [ 18.193162] ath11k_pci 0000:06:00.0: wmi unsupported event id 0x4026 [ 18.208102] ath11k_pci 0000:06:00.0: wmi processing regulatory ext channel list [ 18.208106] ath11k_pci 0000:06:00.0: wmi status_code REG_SET_CC_STATUS_PASS [ 18.208108] ath11k_pci 0000:06:00.0: wmi 6 GHz AP BW: LPI (2 - 160), SP (0 - 0), VLP (0 - 0) [ 18.208111] ath11k_pci 0000:06:00.0: wmi 6 GHz DEFAULT CLIENT BW: LPI (2 - 160), SP (2 - 160), VLP (0 - 0) [ 18.208113] ath11k_pci 0000:06:00.0: wmi 6 GHz SUBORDINATE CLIENT BW: LPI (2 - 160), SP (2 - 160), VLP (0 - 0) [ 18.208115] ath11k_pci 0000:06:00.0: wmi cc_ext US dsf 1 BW: min_2ghz 0 max_2ghz 40 min_5ghz 2 max_5ghz 160 [ 18.208118] ath11k_pci 0000:06:00.0: wmi num_2ghz_reg_rules 1 num_5ghz_reg_rules 5 [ 18.208119] ath11k_pci 0000:06:00.0: wmi num_6ghz_reg_rules_ap_lpi: 1 num_6ghz_reg_rules_ap_sp: 0 num_6ghz_reg_rules_ap_vlp: 0 [ 18.208121] ath11k_pci 0000:06:00.0: wmi 6 GHz Regular client: num_6ghz_reg_rules_lpi: 1 num_6ghz_reg_rules_sp: 2 num_6ghz_reg_rules_vlp: 0 [ 18.208123] ath11k_pci 0000:06:00.0: wmi 6 GHz Subordinate client: num_6ghz_reg_rules_lpi: 1 num_6ghz_reg_rules_sp: 2 num_6ghz_reg_rules_vlp: 0 [ 18.208125] ath11k_pci 0000:06:00.0: wmi number of reg rules in 2 GHz band: 1 [ 18.208127] ath11k_pci 0000:06:00.0: wmi reg rule 1: (2402 - 2472 @ 40) (6, 30) (FLAGS 0) [ 18.208129] ath11k_pci 0000:06:00.0: wmi CC: US 5 GHz reg rules number 5 from fw, 1 number of invalid 5 GHz rules [ 18.208131] ath11k_pci 0000:06:00.0: wmi number of reg rules in 5 GHz band: 4 [ 18.208133] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5170 - 5250 @ 80) (0, 30) (FLAGS 0) [ 18.208135] ath11k_pci 0000:06:00.0: wmi reg rule 2: (5250 - 5330 @ 80) (0, 24) (FLAGS 8) [ 18.208136] ath11k_pci 0000:06:00.0: wmi reg rule 3: (5490 - 5730 @ 160) (0, 24) (FLAGS 8) [ 18.208138] ath11k_pci 0000:06:00.0: wmi reg rule 4: (5735 - 5895 @ 160) (0, 30) (FLAGS 0) [ 18.208140] ath11k_pci 0000:06:00.0: wmi number of reg rules in INDOOR AP band: 1 [ 18.208142] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5945 - 7125 @ 160) (0, 27) (FLAGS 512) [ 18.208144] ath11k_pci 0000:06:00.0: wmi number of reg rules in STANDARD POWER AP band: 0 [ 18.208146] ath11k_pci 0000:06:00.0: wmi number of reg rules in VERY LOW POWER AP band: 0 [ 18.208147] ath11k_pci 0000:06:00.0: wmi 6 GHz AP type INDOOR AP [ 18.208149] ath11k_pci 0000:06:00.0: wmi number of reg rules in DEFAULT CLIENT band: 1 [ 18.208150] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5945 - 7125 @ 160) (0, 21) (FLAGS 512) [ 18.208152] ath11k_pci 0000:06:00.0: wmi number of reg rules in SUBORDINATE CLIENT band: 1 [ 18.208154] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5945 - 7125 @ 160) (0, 27) (FLAGS 512) [ 18.208156] ath11k_pci 0000:06:00.0: wmi 6 GHz AP type STANDARD POWER AP [ 18.208157] ath11k_pci 0000:06:00.0: wmi number of reg rules in DEFAULT CLIENT band: 2 [ 18.208159] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5945 - 6425 @ 160) (0, 27) (FLAGS 0) [ 18.208161] ath11k_pci 0000:06:00.0: wmi reg rule 2: (6525 - 6885 @ 160) (0, 27) (FLAGS 0) [ 18.208163] ath11k_pci 0000:06:00.0: wmi number of reg rules in SUBORDINATE CLIENT band: 2 [ 18.208164] ath11k_pci 0000:06:00.0: wmi reg rule 1: (5945 - 6425 @ 160) (0, 27) (FLAGS 0) [ 18.208166] ath11k_pci 0000:06:00.0: wmi reg rule 2: (6525 - 6885 @ 160) (0, 27) (FLAGS 0) [ 18.208168] ath11k_pci 0000:06:00.0: wmi 6 GHz AP type VERY LOW POWER AP [ 18.208169] ath11k_pci 0000:06:00.0: wmi number of reg rules in DEFAULT CLIENT band: 0 [ 18.208171] ath11k_pci 0000:06:00.0: wmi number of reg rules in SUBORDINATE CLIENT band: 0 [ 18.208172] ath11k_pci 0000:06:00.0: wmi 6 GHz reg info client type SUBORDINATE CLIENT rnr_tpe_usable 0 unspecified_ap_usable 0 AP sub domain: lpi FCC1_AP_LPI_6GHZ/FCC1_CLIENT_LPI_SUBORDINATE, sp N/A, vlp N/A [ 18.208175] ath11k_pci 0000:06:00.0: wmi 6 GHz client type DEFAULT CLIENT client sub domain: lpi FCC1_CLIENT_LPI_REGULAR_6GHZ, sp FCC1_CLIENT_SP_6GHZ, vlp N/A [ 18.208177] ath11k_pci 0000:06:00.0: wmi 6 GHz client type SUBORDINATE CLIENT client sub domain: lpi FCC1_AP_LPI_6GHZ/FCC1_CLIENT_LPI_SUBORDINATE, sp FCC1_CLIENT_SP_6GHZ, vlp N/A [ 18.208179] ath11k_pci 0000:06:00.0: wmi 6 GHz client_type SUBORDINATE CLIENT 6 GHz super domain FCC1_6GHZ [ 18.208180] ath11k_pci 0000:06:00.0: wmi processed regulatory ext channel list [ 18.208182] ath11k_pci 0000:06:00.0: wmi event reg chan list id 1 [ 18.208468] ath11k_pci 0000:06:00.0: wmi event ready [ 18.208926] ath11k_pci 0000:06:00.0: wmi unsupported event id 0x4021 [ 18.288141] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 18.288622] ath11k_pci 0000:06:00.0: wmi cmd pdev dma ring cfg req pdev_id 0x1 [ 18.292456] ath11k_pci 0000:06:00.0 wlp6s0: renamed from wlan0 [ 22.144958] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 22.145537] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 22.147635] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 34 pdev id 1 value 1 [ 22.147639] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 10 pdev id 1 value 1 [ 22.147642] ath11k_pci 0000:06:00.0: wmi scan prob req oui 5473 [ 22.147644] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 35 pdev id 1 value 0 [ 22.147646] ath11k_pci 0000:06:00.0: wmi cmd pdev dfs phyerr offload enable pdev id 1 [ 22.147649] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 143 pdev id 1 value 1 [ 22.147651] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 1 pdev id 1 value 15 [ 22.147653] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 2 pdev id 1 value 15 [ 22.147658] ath11k_pci 0000:06:00.0: wmi mac channel [0/28] freq 5180 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147660] ath11k_pci 0000:06:00.0: wmi mac channel [1/28] freq 5200 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147662] ath11k_pci 0000:06:00.0: wmi mac channel [2/28] freq 5220 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147664] ath11k_pci 0000:06:00.0: wmi mac channel [3/28] freq 5240 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147666] ath11k_pci 0000:06:00.0: wmi mac channel [4/28] freq 5260 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147668] ath11k_pci 0000:06:00.0: wmi mac channel [5/28] freq 5280 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147669] ath11k_pci 0000:06:00.0: wmi mac channel [6/28] freq 5300 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147671] ath11k_pci 0000:06:00.0: wmi mac channel [7/28] freq 5320 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147673] ath11k_pci 0000:06:00.0: wmi mac channel [8/28] freq 5500 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147675] ath11k_pci 0000:06:00.0: wmi mac channel [9/28] freq 5520 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147677] ath11k_pci 0000:06:00.0: wmi mac channel [10/28] freq 5540 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147679] ath11k_pci 0000:06:00.0: wmi mac channel [11/28] freq 5560 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147680] ath11k_pci 0000:06:00.0: wmi mac channel [12/28] freq 5580 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147682] ath11k_pci 0000:06:00.0: wmi mac channel [13/28] freq 5600 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147684] ath11k_pci 0000:06:00.0: wmi mac channel [14/28] freq 5620 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147686] ath11k_pci 0000:06:00.0: wmi mac channel [15/28] freq 5640 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147688] ath11k_pci 0000:06:00.0: wmi mac channel [16/28] freq 5660 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147690] ath11k_pci 0000:06:00.0: wmi mac channel [17/28] freq 5680 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147691] ath11k_pci 0000:06:00.0: wmi mac channel [18/28] freq 5700 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147693] ath11k_pci 0000:06:00.0: wmi mac channel [19/28] freq 5720 maxpower 48 regpower 48 antenna 0 mode 0 [ 22.147695] ath11k_pci 0000:06:00.0: wmi mac channel [20/28] freq 5745 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147697] ath11k_pci 0000:06:00.0: wmi mac channel [21/28] freq 5765 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147699] ath11k_pci 0000:06:00.0: wmi mac channel [22/28] freq 5785 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147700] ath11k_pci 0000:06:00.0: wmi mac channel [23/28] freq 5805 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147702] ath11k_pci 0000:06:00.0: wmi mac channel [24/28] freq 5825 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147704] ath11k_pci 0000:06:00.0: wmi mac channel [25/28] freq 5845 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147706] ath11k_pci 0000:06:00.0: wmi mac channel [26/28] freq 5865 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147708] ath11k_pci 0000:06:00.0: wmi mac channel [27/28] freq 5885 maxpower 60 regpower 60 antenna 0 mode 0 [ 22.147712] ath11k_pci 0000:06:00.0: wmi no.of chan = 28 len = 804 pdev_id = 1 num_sends = 0 [ 22.147714] ath11k_pci 0000:06:00.0: wmi chan scan list chan[0] = 5180, chan_info->info 20000 [ 22.147716] ath11k_pci 0000:06:00.0: wmi chan scan list chan[1] = 5200, chan_info->info 20000 [ 22.147718] ath11k_pci 0000:06:00.0: wmi chan scan list chan[2] = 5220, chan_info->info 20000 [ 22.147719] ath11k_pci 0000:06:00.0: wmi chan scan list chan[3] = 5240, chan_info->info 20000 [ 22.147721] ath11k_pci 0000:06:00.0: wmi chan scan list chan[4] = 5260, chan_info->info 20480 [ 22.147722] ath11k_pci 0000:06:00.0: wmi chan scan list chan[5] = 5280, chan_info->info 20480 [ 22.147723] ath11k_pci 0000:06:00.0: wmi chan scan list chan[6] = 5300, chan_info->info 20480 [ 22.147725] ath11k_pci 0000:06:00.0: wmi chan scan list chan[7] = 5320, chan_info->info 20480 [ 22.147726] ath11k_pci 0000:06:00.0: wmi chan scan list chan[8] = 5500, chan_info->info 20480 [ 22.147728] ath11k_pci 0000:06:00.0: wmi chan scan list chan[9] = 5520, chan_info->info 20480 [ 22.147729] ath11k_pci 0000:06:00.0: wmi chan scan list chan[10] = 5540, chan_info->info 20480 [ 22.147731] ath11k_pci 0000:06:00.0: wmi chan scan list chan[11] = 5560, chan_info->info 20480 [ 22.147732] ath11k_pci 0000:06:00.0: wmi chan scan list chan[12] = 5580, chan_info->info 20480 [ 22.147734] ath11k_pci 0000:06:00.0: wmi chan scan list chan[13] = 5600, chan_info->info 20480 [ 22.147735] ath11k_pci 0000:06:00.0: wmi chan scan list chan[14] = 5620, chan_info->info 20480 [ 22.147737] ath11k_pci 0000:06:00.0: wmi chan scan list chan[15] = 5640, chan_info->info 20480 [ 22.147738] ath11k_pci 0000:06:00.0: wmi chan scan list chan[16] = 5660, chan_info->info 20480 [ 22.147740] ath11k_pci 0000:06:00.0: wmi chan scan list chan[17] = 5680, chan_info->info 20480 [ 22.147741] ath11k_pci 0000:06:00.0: wmi chan scan list chan[18] = 5700, chan_info->info 20480 [ 22.147742] ath11k_pci 0000:06:00.0: wmi chan scan list chan[19] = 5720, chan_info->info 20480 [ 22.147744] ath11k_pci 0000:06:00.0: wmi chan scan list chan[20] = 5745, chan_info->info 20000 [ 22.147745] ath11k_pci 0000:06:00.0: wmi chan scan list chan[21] = 5765, chan_info->info 20000 [ 22.147747] ath11k_pci 0000:06:00.0: wmi chan scan list chan[22] = 5785, chan_info->info 20000 [ 22.147748] ath11k_pci 0000:06:00.0: wmi chan scan list chan[23] = 5805, chan_info->info 20000 [ 22.147750] ath11k_pci 0000:06:00.0: wmi chan scan list chan[24] = 5825, chan_info->info 20000 [ 22.147751] ath11k_pci 0000:06:00.0: wmi chan scan list chan[25] = 5845, chan_info->info 20000 [ 22.147753] ath11k_pci 0000:06:00.0: wmi chan scan list chan[26] = 5865, chan_info->info 20000 [ 22.147754] ath11k_pci 0000:06:00.0: wmi chan scan list chan[27] = 5885, chan_info->info 20000 [ 22.147756] ath11k_pci 0000:06:00.0: wmi cmd scan chan list channels 28 [ 22.147760] ath11k_pci 0000:06:00.0: wmi cmd lro config pdev_id 0x1 [ 22.147763] ath11k_pci 0000:06:00.0: mac add interface id 0 type 2 subtype 0 map ff [ 22.147766] ath11k_pci 0000:06:00.0: wmi cmd vdev create id 0 type 2 subtype 0 macaddr 00:15:61:27:cd:da pdevid 1 [ 22.147768] ath11k_pci 0000:06:00.0: mac vdev 00:15:61:27:cd:da created, vdev_id 0 [ 22.147771] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 48 value 1 [ 22.147773] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 91 value 1 [ 22.147775] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 34 value 4 [ 22.147777] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 0 value 0 [ 22.147779] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 1 value 1 [ 22.147781] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 2 value 0 [ 22.147783] ath11k_pci 0000:06:00.0: wmi cmd sta powersave mode psmode 0 vdev id 0 [ 22.147785] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 1 value -1 [ 22.147787] ath11k_pci 0000:06:00.0: mac defer protection mode setup, vdev is not ready yet [ 22.147789] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 7 value 1 [ 22.147791] ath11k_pci 0000:06:00.0: mac Set slottime: 1 for VDEV: 0 [ 22.147792] ath11k_pci 0000:06:00.0: wmi cmd vdev set param vdev 0x0 param 8 value 1 [ 22.147794] ath11k_pci 0000:06:00.0: mac Set preamble: 1 for VDEV: 0 [ 22.147797] ath11k_pci 0000:06:00.0: wmi wmm set ac 0 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147799] ath11k_pci 0000:06:00.0: wmi wmm set ac 1 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147801] ath11k_pci 0000:06:00.0: wmi wmm set ac 2 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147803] ath11k_pci 0000:06:00.0: wmi wmm set ac 3 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147805] ath11k_pci 0000:06:00.0: wmi cmd vdev set wmm params [ 22.147807] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 4 value 0 [ 22.147809] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 0 value 0 [ 22.147811] ath11k_pci 0000:06:00.0: wmi wmm set ac 0 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147813] ath11k_pci 0000:06:00.0: wmi wmm set ac 1 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147814] ath11k_pci 0000:06:00.0: wmi wmm set ac 2 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147816] ath11k_pci 0000:06:00.0: wmi wmm set ac 3 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147818] ath11k_pci 0000:06:00.0: wmi cmd vdev set wmm params [ 22.147820] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 4 value 0 [ 22.147822] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 0 value 0 [ 22.147823] ath11k_pci 0000:06:00.0: wmi wmm set ac 0 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147825] ath11k_pci 0000:06:00.0: wmi wmm set ac 1 aifs 0 cwmin 0 cwmax 0 txop 0 acm 0 no_ack 0 [ 22.147827] ath11k_pci 0000:06:00.0: wmi wmm set ac 2 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147829] ath11k_pci 0000:06:00.0: wmi wmm set ac 3 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147831] ath11k_pci 0000:06:00.0: wmi cmd vdev set wmm params [ 22.147832] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 4 value 0 [ 22.147834] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 0 value 0 [ 22.147836] ath11k_pci 0000:06:00.0: wmi wmm set ac 0 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147838] ath11k_pci 0000:06:00.0: wmi wmm set ac 1 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147840] ath11k_pci 0000:06:00.0: wmi wmm set ac 2 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147841] ath11k_pci 0000:06:00.0: wmi wmm set ac 3 aifs 2 cwmin 15 cwmax 1023 txop 0 acm 0 no_ack 0 [ 22.147843] ath11k_pci 0000:06:00.0: wmi cmd vdev set wmm params [ 25.192425] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 36866 [ 25.192440] ath11k_pci 0000:06:00.0: failed to send WMI_STA_POWERSAVE_PARAM_CMDID [ 25.192449] ath11k_pci 0000:06:00.0: wmi cmd set powersave param vdev_id 0 param 4 value 0 [ 25.192459] ath11k_pci 0000:06:00.0: could not set uapsd params -105 [ 25.192465] ath11k_pci 0000:06:00.0: failed to set sta uapsd: -105 [ 28.264431] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 28.264447] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 28.264456] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 28.264465] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 28.264472] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 28.264479] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 31.336429] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 31.336452] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 31.336454] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 31.336456] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 31.336458] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 31.336460] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 34.408345] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 34.408350] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 34.408353] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 34.408355] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 34.408356] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 34.408358] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 37.480373] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 37.480377] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 37.480380] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 37.480382] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 37.480384] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 37.480385] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 40.552370] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 40.552375] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 40.552378] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 40.552380] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 40.552381] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 40.552383] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 43.624401] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 90113 [ 43.624406] ath11k_pci 0000:06:00.0: failed to send WMI_REQUEST_STATS cmd [ 43.624410] ath11k_pci 0000:06:00.0: wmi cmd request stats 0x4 vdev id 0 pdev id 1 [ 43.624412] ath11k_pci 0000:06:00.0: could not request fw stats (-105) [ 43.624413] ath11k_pci 0000:06:00.0: failed to request fw pdev stats: -105 [ 43.624415] ath11k_pci 0000:06:00.0: mac txpower from firmware NaN, reported -2147483648 dBm [ 46.696373] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 46.696378] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 46.696381] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 46.696382] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 50.024346] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 50.024350] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 50.024356] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 50.024358] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 73.046274] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 73.046289] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 73.046298] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 73.046305] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 106.064764] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 106.064778] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 106.064788] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 106.064795] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 149.072433] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 149.072448] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 149.072457] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 149.072464] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 202.064478] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 202.064494] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 202.064505] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 202.064514] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 [ 265.040866] ath11k_pci 0000:06:00.0: ce desc not available for wmi command 12289 [ 265.040881] ath11k_pci 0000:06:00.0: failed to send WMI_START_SCAN_CMDID [ 265.040890] ath11k_pci 0000:06:00.0: wmi cmd start scan [ 265.040897] ath11k_pci 0000:06:00.0: failed to start hw scan: -105 Also, now that I am back, the 6.4 kernel commit is: >> git remote -v origin git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (fetch) origin git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (push) >> git rev-parse HEAD c60d15f389ef9832a8da410e438d81b10327751f (which is the one you cannot find in ath.git)
Oh okay. The reason why I suspected the interrupt part is that the descriptor ring size where the driver is queueing commands to FW is 32, i.e., we can queue upto 32 commands to the firmware at once. As and when, driver receives completions on the command ring, the descriptor corresponding to the command gets freed and driver can queue more commands. From the dmesg that you shared now and from the earlier dmesgs, what I see is driver is able to queue only 32 commands and then this issue "ce desc not available for wmi command" starts coming up. This I still presume is something to do with interrupts only. I'll provide a debug patch to check if the interrupts are coming to the driver. I'm working on the patch.
Created attachment 304862 [details] IRQ logs patch
Created attachment 304863 [details] Credit flow disable
Hi, Even with MSI vectors set to 1, I could not repro the issue. Attaching two patches, could you pls test them individually and get the dmesg logs pls? Thanks
I have tried IRQ logs patch, but I don't see the added debug prints in dmesg. Do I need to set some specific flag ?
Not really, I have used pr_err instead of ath11k_dbg to avoid setting any flag. On my machine I have seen these prints. Could you pls replace pe_err with printk(KERN_ERR and give a try. I can provide a patch for that if needed. Pls let me know. Thanks.
I've used ath11k_err instead, attached dmesg output. I am building the 2nd patch.
Created attachment 304865 [details] log-irq.txt
Created attachment 304866 [details] kernel config
Checked the IRQ logs, after a point we are not getting any interrupts from the device. Not sure what's really happening in the system. If possible, can you pls provide the driver logs with debug_mask=0xFFFF and also give the output of /proc/interrupts after the issue is reproduced? Thanks
Created attachment 304867 [details] dmesg grep ath11k
Created attachment 304868 [details] dmesg full
Created attachment 304869 [details] proc interrupts
Thanks for the logs. I'll analyze these and get back. Curios to know the outcome of 2nd patch? Got a chance to test that? Thanks
Created attachment 304870 [details] log-dmesg-credit-flow-disabled-full removing irqs prints patch and applying credit flow patch the error is different: [ 21.868407] ath11k_pci 0000:06:00.0: htc ep 2 insufficient credits required 1 total 0 [ 21.868422] ath11k_pci 0000:06:00.0: wmi command 16387 timeout [ 21.868431] ath11k_pci 0000:06:00.0: failed to send WMI_PDEV_SET_PARAM cmd [ 21.868439] ath11k_pci 0000:06:00.0: wmi cmd pdev set param 10 pdev id 1 value 1 [ 21.868448] ath11k_pci 0000:06:00.0: failed to enable dynamic bw: -11
Thanks, this proves that the interrupts are blocked from reaching the driver. Two possible cases. 1) Device itself hasn't raised any interrupts, this is unlikely case because device did raise interrupts and then all of a sudden there are no interrupts. 2) There was a misconfiguration of MSI data in the hardware, therefore no interrupts. Can you pls share one set of logs with patch-1 and threaded NAPI disabled? Just wanted to check working vs non-working case. Sorry for the never-ending requests. Thanks
Created attachment 304871 [details] log-dmesg-patch-1-threaded-false-full No problem. Here is the log with dev_set_threaded commented out. The issue is not seen.
Created attachment 304877 [details] diff-lhsthreadedfalse-rhsthreadedtrue From the diff of both non-threaded and threaded napi, the only difference I see is in the ordering of IRQ config and receive. Lines 425, 780 and 878 from diff "pci msi assignment DP num_vectors 1...". In the threaded napi, the function pcic.c:ath11k_pcic_ext_irq_config seems to be called before some interrupts are received. Could this be a concurrency issue ?
Actually, issue is with the CE interrupts (control path) which schedules tasklets, on the other hand datapath interrupts (DP) use threaded NAPI. I still don't understand as to how one simple change like threaded NAPI is blocking the control path interrupts those are unrelated. I'm yet to compare the logs, will check the concurrency aspect too. Thanks for the insights.
Aside from this bug report, I just wanted to share re: > This unit can associate to APs only with the firmware Sparklan provided. > Otherwise, link strength is reported low and barely no APs are listed after > scanning. In looking at the differences between the BDFs from versions 2.4.0 and 2.5.0, I was able to map them to ABI changes in the board files across the two versions to the one that Sparklan provided. Since modifying the board.bin file based on my findings, I am able to run 2.7.0+ on the WPEQ-405AX!
Hi Tyler, Nice one! Do you mind sharing your modified board.bin so we can test it and see if that solves our current open issue with data throughput? Open issue is #217652. If you have 2x QCN9074 would be great if you could report your throughput as well. Thank you
Created attachment 305341 [details] Sparklan WPEQ-405AX board.bin modified for firmware 2.5.0+ Attached a copy of the modified board.bin to this BZ.
Hello, I'm using a 6.1.80-rt26+ kernel with the latest WCN6855 firmware (6510.37) and I had to backport the revert of the "threaded NAPI". [ 7.725067] ath11k_pci 0001:01:00.0: BAR 0: assigned [mem 0x30200000-0x303fffff 64bit] [ 7.725128] ath11k_pci 0001:01:00.0: enabling device (0140 -> 0142) [ 7.735351] ath11k_pci 0001:01:00.0: MSI vectors: 1 [ 7.735382] ath11k_pci 0001:01:00.0: wcn6855 hw2.0 [ 9.669647] ath11k_pci 0001:01:00.0: chip_id 0x2 chip_family 0xb board_id 0xff soc_id 0x400c0200 [ 9.669677] ath11k_pci 0001:01:00.0: fw_version 0x1106196e fw_build_timestamp 2024-01-12 11:30 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 [ 10.150543] ath11k_pci 0001:01:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems [ 10.562927] ath11k_pci 0001:01:00.0 wlP1p1s0: renamed from wlan0 # poweroff [ 615.197998] wlP1p1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 618.215698] ath11k_pci 0001:01:00.0: wmi command 28680 timeout [ 618.215728] ath11k_pci 0001:01:00.0: failed to submit WMI_MGMT_TX_SEND_CMDID cmd [ 618.215728] ath11k_pci 0001:01:00.0: failed to send mgmt frame: -11 [ 618.215759] ath11k_pci 0001:01:00.0: failed to tx mgmt frame, vdev_id 0 :-11 [ 620.519683] ath11k_pci 0001:01:00.0: failed to flush transmit queue, data pkts pending 5 Best regards, Romain
Hi Romain, Turns out the issue I had with IRQs and threaded napi was mostly linked to VT-d not being enabled and therefore not allowing 16 MSI allocations. I wrongly thought that VT-d was enabled, but looking closer I had to upgrade my BIOS and some other options came up. Now I have 16 MSIs (you have only one, and I believe that the driver does not work as expected in that case) and the threaded napi enabled does not break the driver. However, after a couple of experiments I have kept it out. It was triggering swiotlb overflow errors in dmesg and not bringing any performance improvements. I think I saw a recent patch fixing the swiotlb issue. Best
Hi Tanguy, I'm using an Texas Instrument AM5749 ARM SoC with the pcie WCN6855 wifi device and reverting the "threaded NAPI" seems to improve the behaviour of the ath11k_pci driver when it is removed from the kernel during poweroff (ath11k_pci_remove()). I'm not sure what's the root cause of the issue with threaded napi... Best regards, Romain