From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
James Prestwood <prestwoj@gmail.com>,
<linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Chun Wu <chunwu@qti.qualcomm.com>
Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9
Date: Mon, 08 Jul 2024 13:36:42 +0300 [thread overview]
Message-ID: <87o778cgqt.fsf@kernel.org> (raw)
In-Reply-To: <82e10a1a-ed23-4d5c-b691-02e39296a91e@quicinc.com> (Baochen Qiang's message of "Mon, 8 Jul 2024 09:53:08 +0800")
Baochen Qiang <quic_bqiang@quicinc.com> writes:
>>> Checked with firmware team and just know that, the TX rate info is
>>> generated by firmware directly but for RX rate it is from phy side.
>>> From firmware TX rate generation code seems NSS 3 is an impossible
>>> value, so it might be an RX rate generated by phy side. But I could
>>> not tell for now since the log is not complete. Paul, could you
>>> enable full ath10k log and try to reproduce? With full log we can
>>> check whether it is a RX rate issue,
>>
>> Please tell me how I enable full logging.
>
> once boot, first unload ath10k modules by
>
> sudo modprobe -r ath10k_pci
>
> then load ath10k modules with
>
> sudo modprobe ath10k_core debug_mask=0xffffffff
> sudo modprobe ath10k_pci
>
> you should see lots of prints now
BTW the extensive debug messages can slow down the system so there's
also the option of using tracing which is a lot faster:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug#tracing
Though I have not tested that for a long time but I hope it still works.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-07-08 10:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 13:10 invalid vht params rate 1920 100kbps nss 2 mcs 9 Paul Menzel
2024-06-17 15:09 ` James Prestwood
2024-06-17 15:27 ` Kalle Valo
2024-06-17 15:40 ` James Prestwood
2024-06-18 10:33 ` Kalle Valo
2024-06-18 10:48 ` Baochen Qiang
2024-06-26 8:53 ` Baochen Qiang
2024-06-26 9:12 ` Paul Menzel
2024-06-26 10:16 ` Kalle Valo
2024-06-26 11:48 ` Paul Menzel
2024-06-26 12:34 ` Kalle Valo
2024-07-05 2:47 ` Baochen Qiang
2024-07-05 6:55 ` Paul Menzel
2024-07-05 10:51 ` Baochen Qiang
2024-07-05 11:52 ` Paul Menzel
2024-07-08 1:53 ` Baochen Qiang
2024-07-08 10:36 ` Kalle Valo [this message]
2024-07-08 10:33 ` Kalle Valo
2024-07-09 1:33 ` Baochen Qiang
2024-06-27 17:42 ` James Prestwood
2024-06-27 18:25 ` Kalle Valo
2024-06-28 1:25 ` Baochen Qiang
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=87o778cgqt.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=chunwu@qti.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=prestwoj@gmail.com \
--cc=quic_bqiang@quicinc.com \
/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