Messages in this thread | | | From | Tyler Stachecki <> | Date | Thu, 26 Oct 2023 19:06:49 -0400 | Subject | Re: Fwd: ath11k: QCN9074: ce desc not available for wmi command |
| |
On Mon, Sep 4, 2023 at 5:47 AM Manikanta Pubbisetty <quic_mpubbise@quicinc.com> wrote: > > Hi Manikanta, > > > > I just wanted to report that this is likely related to QCN9074 when the host > > system only has 1 MSI-X vector available for the modem and/or related to a > > product named "WPEQ-405AX". > > > > I have two different hosts running the exact same kernel, same QCN9074 > > firmware (WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1), etc. The only > > differences are that the one which does not work is running on a slightly > > older Intel SBC, with the older one leveraging mPCIe instead of PCIe and > > only having one MSI-X vector. > > Yes, you are right. This seems to be a problem with some hardware having > QCN9074. We have tried to reproduce this problem in QC on different > hardware but could not reproduce it even once. Not even with one MSI vector.
Just as a heads up, this "Sparklan WPEQ-405AX" version of QCN9074 may be adding to some of the confusion here and so there may be two problems. As mentioned previously, CE desc errors stopped after reverting the threaded NAPI patch. However, there's something odd about this modem - it does not work with the board-2.bin that Kalle provides as the OP noted.
Upon request, the vendor of this modem provides a board.bin for WPEQ-405AX compatible with a copy of amss/m3 which appears to be WLAN.HK.2.4.0.1-01838-QCAHKSWPL_SILICONZ-1 (based on checksums). I found out the hard way that the ABI of the BDFs changed for WLAN.HK.2.5.0 firmwares and beyond, making things non-backwards compatible with the board.bin that the vendor provides.. which is unfortunate as the vendor would not supply a BDF built against 2.5.0+ when requested.
The board-2.bin that Kalle allows the modem start, but it fails to associate or really do anything useful beyond announcing a SSID in AP mode.
Anyways: I think it's mostly just an issue with the IRQ affinity -- maybe the threaded NAPI patch is changing it somehow...
Cheers, Tyler
| |