From: James Prestwood <prestwoj@gmail.com>
To: Baochen Qiang <quic_bqiang@quicinc.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/2] wifi: ath10k: fix invalid VHT parameters
Date: Mon, 19 Aug 2024 04:47:49 -0700 [thread overview]
Message-ID: <6e93a6c8-015f-4649-8c72-d21fa9f9fde9@gmail.com> (raw)
In-Reply-To: <e49b05be-7fdd-4007-9137-e46703812fa1@quicinc.com>
Hi Baochen,
On 8/19/24 2:45 AM, Baochen Qiang wrote:
>
> On 8/14/2024 11:46 PM, James Prestwood wrote:
>> Hi Baochen,
>>
>> On 7/15/24 5:38 AM, James Prestwood wrote:
>>> Hi Baochen,
>>>
>>> I've compiled both changes and so far those messages are gone.
>>>
>>> Tested-By: James Prestwood <prestwoj@gmail.com> # on QCA6174 hw3.2
>> I just noticed another one actually:
>>
>> invalid vht params rate 585 100kbps nss 1 mcs 4
> Ah :(
>
> James, could you share some info about this? like hardware target, firmware version, AP model, and any specific steps to hit this.
This is running with your fixes in this patch set, which did fix the
majority of the "invalid vht params" messages, but then recently I
noticed some others.
The hardware:
kernel: ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id
0x00340aff sub 168c:3363
kernel: ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6
features wowlan,ignore-otp,mfp crc32 bf907c7c
And its actually a few more than I thought:
ath10k_pci 0000:02:00.0: invalid vht params rate 900 100kbps nss 3 mcs 4
ath10k_pci 0000:02:00.0: invalid vht params rate 867 100kbps nss 2 mcs 6
ath10k_pci 0000:02:00.0: invalid vht params rate 540 100kbps nss 3 mcs 3
ath10k_pci 0000:02:00.0: invalid vht params rate 1500 100kbps nss 3 mcs 7
I unfortunately don't have a way to reproduce it. We just see this now
somewhat rarely, e.g. 13 of the above in the last 3 days. I assume its
just when the MCS/NSS changes and we hit a rate that isn't mapped right
like the few you fixed.
Thanks,
James
>
>> Thanks,
>>
>> James
>>
>>> On 7/10/24 7:03 PM, Baochen Qiang wrote:
>>>> supported_vht_mcs_rate_nss1 and supported_vht_mcs_rate_nss2 in host do not
>>>> align with firmware's definitions, resulting in some warnings. Fix them.
>>>>
>>>> Baochen Qiang (2):
>>>> wifi: ath10k: fix invalid VHT parameters in
>>>> supported_vht_mcs_rate_nss1
>>>> wifi: ath10k: fix invalid VHT parameters in
>>>> supported_vht_mcs_rate_nss2
>>>>
>>>> drivers/net/wireless/ath/ath10k/mac.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>>
>>>> base-commit: db1ce56e6e1d395dd42a3cd6332a871d9be59c45
next prev parent reply other threads:[~2024-08-19 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 2:03 [PATCH 0/2] wifi: ath10k: fix invalid VHT parameters Baochen Qiang
2024-07-11 2:03 ` [PATCH 1/2] wifi: ath10k: fix invalid VHT parameters in supported_vht_mcs_rate_nss1 Baochen Qiang
2024-07-22 23:23 ` Jeff Johnson
2024-09-28 9:11 ` Kalle Valo
2024-07-11 2:03 ` [PATCH 2/2] wifi: ath10k: fix invalid VHT parameters in supported_vht_mcs_rate_nss2 Baochen Qiang
2024-07-22 23:23 ` Jeff Johnson
2024-08-19 18:13 ` Paul Menzel
2024-07-15 12:38 ` [PATCH 0/2] wifi: ath10k: fix invalid VHT parameters James Prestwood
2024-08-14 15:46 ` James Prestwood
2024-08-19 9:45 ` Baochen Qiang
2024-08-19 11:47 ` James Prestwood [this message]
2024-08-20 1:51 ` 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=6e93a6c8-015f-4649-8c72-d21fa9f9fde9@gmail.com \
--to=prestwoj@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--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