From: Kalle Valo <kvalo@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
James Prestwood <prestwoj@gmail.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9
Date: Wed, 26 Jun 2024 13:16:58 +0300 [thread overview]
Message-ID: <878qyshuud.fsf@kernel.org> (raw)
In-Reply-To: <082024ce-fdd4-4fb1-8055-6d25f7d2e524@molgen.mpg.de> (Paul Menzel's message of "Wed, 26 Jun 2024 11:12:15 +0200")
Paul Menzel <pmenzel@molgen.mpg.de> writes:
> Am 26.06.24 um 10:53 schrieb Baochen Qiang:
>
>> OK, there are two issues here:
>> 1. invalid HT rate: "ath10k_pci 0000:02:00.0: invalid ht params rate
>> 1440 100kbps nss 2 mcs 7".
>> As commented by Wen quite some time ago, this has been fixed from
>> firmware side, and firmware newer than [ver:241] has the fix
>> included.
I assume this means that the firmware version
WLAN.RM.4.4.1-00241-QCARMSWPZ-1 or newer has the fix.
>> 2. invaid VHT rate: "ath10k_pci 0000:3a:00.0: invalid vht params
>> rate 1920 100kbps nss 2 mcs 9".
>> After checking with firmware team, I thought this is because there
>> is
>> a mismatch in rate definition between host and firmware: In host, the
>> rate for 'nss 2 mcs 9' is defined as {1560, 1733}, see
>> supported_vht_mcs_rate_nss2[]. While in firmware this is defined as
>> {1730, 1920}. So seems we can update host definition to avoid this
>> issue.
> Looking through the logs since May 2024, I have four different logs:
>
> 1. invalid vht params rate 878 100kbps nss 3 mcs 2
> 2. invalid vht params rate 960 100kbps nss 1 mcs 9
> 3. invalid vht params rate 1730 100kbps nss 2 mcs 9
> 4. invalid vht params rate 1920 100kbps nss 2 mcs 9
>
> I believe it’s only happening with Cisco networks. I am happy to test
> a patch.
>
> By the way, is the firmware version logged by Linux?
>
> ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
> 0x00340aff sub 1a56:1535
> ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0
> testmode 0
> ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6
> features wowlan,ignore-otp,mfp crc32 bf907c7c
> ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
> ath10k_pci 0000:3a:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp
> max-sta 32 raw 0 hwcrypto 1
>
> Is it 4.4.1-00288?
Yes, that should be WLAN.RM.4.4.1-00288-QCARMSWPZ-1. But I don't know
why 'QCARMSWPZ-1' is not printed by ath10k, maybe we have a bug
somewhere.
> How can I find the file in `/lib/firmware/`?
It should be in ath10k/QCA6174/hw3.0/firmware-6.bin.
All firmware releases are available here:
https://git.codelinaro.org/clo/ath-firmware/ath10k-firmware/-/tree/main/QCA6174/hw3.0/4.4.1?ref_type=heads
And more info here:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-06-26 10:17 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 [this message]
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
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=878qyshuud.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.