From: Tyler Stachecki <stachecki.tyler@gmail.com>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Kalle Valo <quic_kvalo@quicinc.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Atheros 11K <ath11k@lists.infradead.org>
Subject: Re: Fwd: ath11k: QCN9074: ce desc not available for wmi command
Date: Sun, 3 Sep 2023 19:30:59 -0400 [thread overview]
Message-ID: <ZPUXMx0H/8U9j15F@luigi.stachecki.net> (raw)
In-Reply-To: <1945f748-fb71-f1c1-83a2-ba0470daf817@quicinc.com>
> 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.
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.
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!
Regards,
Tyler
next prev parent reply other threads:[~2023-09-03 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 7:07 Bagas Sanjaya
2023-06-26 12:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-11 6:57 ` Kalle Valo
2023-07-25 9:17 ` Manikanta Pubbisetty
2023-07-26 9:21 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-26 9:49 ` Manikanta Pubbisetty
2023-09-03 23:30 ` Tyler Stachecki [this message]
2023-09-04 9:47 ` Manikanta Pubbisetty
2023-10-26 23:06 ` Tyler Stachecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPUXMx0H/8U9j15F@luigi.stachecki.net \
--to=stachecki.tyler@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=bagasdotme@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kvalo@quicinc.com \
--cc=quic_mpubbise@quicinc.com \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®