linux-kernel - Re: Fwd: ath11k: QCN9074: ce desc not available for wmi command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1ba68ccb-9faa-8f9f-64cb-cf74dc0a2184@quicinc.com>
Date:   Mon, 4 Sep 2023 15:17:25 +0530
From:   Manikanta Pubbisetty <quic_mpubbise@...cinc.com>
To:     Tyler Stachecki <stachecki.tyler@...il.com>
CC:     Linux regressions mailing list <regressions@...ts.linux.dev>,
        "Bagas Sanjaya" <bagasdotme@...il.com>,
        Kalle Valo <quic_kvalo@...cinc.com>,
        "Johannes Berg" <johannes@...solutions.net>,
        Jakub Kicinski <kuba@...nel.org>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
        Linux Atheros 11K <ath11k@...ts.infradead.org>
Subject: Re: Fwd: ath11k: QCN9074: ce desc not available for wmi command

On 9/4/2023 5:00 AM, Tyler Stachecki wrote:
>> On 25.07.23 11:17, Manikanta Pubbisetty wrote:
>>
>> FWIW, Bagas Sanjaya just forwarded the report and the reporter is not
>> CCed afaics (bugzilla privacy policy does not allow this, which
>> complicates things a lot :-/ ). You have to use bugzilla to reach the
>> reporter: https://bugzilla.kernel.org/show_bug.cgi?id=217536
> 
> 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.

> 
> I tried backing out the threaded NAPI commit and, as mentioned, everything
> begins working again on the host with 1 MSI-X vector. I have also seen some
> other oddities with the system only working with 1 MSI-X vector, such as
> the modem not working when I boot with hpet=disabled. I am guessing it is
> not related, but mentioning it just in case.
> 
> The only other thing I'll mention is that the CE desc errors are *only* seen
> after upping the link (via `ip link set wlp1s0 up`). After this point, doing
> something as simple as reading the temperature of the modem fails and the
> kernel log starts printing the errors described above. Prior to that, however,
> no error messages are seen.
>

True, I had worked with the reporter for quite some time. To me at 
first, it seemed like a problem with improper configuration of the MSI 
DATA in the QCN9074 hardware. I'm investigating further.

> I'm happy to be of service to test any changes you might suggest. Thanks
> for the threaded NAPI work, by the way - it definitely provides a boost!
> 

Sure, Thanks a lot.

Manikanta