Re: mcs index related error on 2,4ghz

From: Bhagavathi Perumal S <bperumal@codeaurora.org>
To: ath11k@lists.infradead.org
Subject: Re: mcs index related error on 2,4ghz
Date: Tue, 09 Apr 2019 15:45:09 +0530	[thread overview]
Message-ID: <d50abbeb09a9591c5b3cc064656c68bc@codeaurora.org> (raw)
In-Reply-To: <e4bd96eef6fa4e579a084a03846b2cc6@euamsexm01f.eu.qualcomm.com>

On 2019-04-09 14:39, Bhagavathi Perumal S wrote:
> Hi,
> 
> When i assoc on 5GHz I am able to pass traffic, when i assoc on the
> 2,4GHz i get the following stack trace upon every received frame. Is
> this a known problem ?
> 
>      John
> 
> 
> [  334.373726] Rate marked as an HT rate but passed status->rate_idx
> is not an MCS index [0-76]: 248 (0xf8) [  334.373796] ------------[
> cut here ]------------ [  334.382261] WARNING: at
> backports-next-ath11k-20190320/net/mac80211/rx.c:4562
> [  334.386865] Modules linked in: pppoe ppp_async iptable_nat ath11k
> pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4
> mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state
> xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment
> xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_redirect
> nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6
> nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle
> iptable_filter ip_tables crc_ccitt compat ip6t_REJECT nf_reject_ipv6
> nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables
> x_tables qca_nss_drv qca_nss_dp qca_ssdk gpio_button_hotplug [ 
> 334.451348] [  334.451701] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G
> W       4.4.60 #0 [  334.453270] Hardware name: Qualcomm Technologies,
> Inc.
> IPQ807x/AP-HK01-C1 (DT)
> [  334.460305] task: ffffffc001c1c3c0 ti: ffffffc001c1c3c0 task.ti:
> ffffffc001c1c3c0
> [  334.467501] PC is at ieee80211_rx_napi+0xec/0x838 [mac80211] [ 
> 334.475024] LR is at ieee80211_rx_napi+0xec/0x838 [mac80211] [ 
> 334.480700] pc : [<ffffffbffc4cd0f4>] lr : [<ffffffbffc4cd0f4>]
> pstate: 60000145
> [  334.486344] sp : ffffffc001c139a0
> [  334.493714] x29: ffffffc001c139a0 x28: 0000000000000000 [ 
> 334.502042] x27: 0000000000000001 x26: ffffffc036fd6e28 [  334.507337]
> x25: 0000000000000001 x24: ffffffc001c13b50 [  334.512632] x23:
> 0000000000000000 x22: ffffffc036fd6e28 [  334.517928] x21:
> ffffffc0393e0f80 x20: ffffffc0393e1e30 [  334.523222] x19:
> ffffffc036fd6e00 x18: 0000000000000000 [  334.528517] x17:
> 0000007fb04147d4 x16: ffffffc00016727c [  334.533813] x15:
> 003b9aca00000000 x14: 206e6120746f6e20 [  334.539108] x13:
> 7369207864695f65 x12: 7461723e2d737574 [  334.544402] x11:
> 6174732064657373 x10: 6170207475622065 [  334.549698] x9 :
> 746172205448206e x8 : 5d36372d305b2078 [  334.554993] x7 :
> 65646e692053434d x6 : ffffffc001c8b0ab [  334.560289] x5 :
> 0000000000000001 x4 : 0000000000000000 [  334.565584] x3 :
> 0000000000000000 x2 : 00000000000040d4 [  334.570878] x1 :
> ffffffc001c1c3c0 x0 : 000000000000005c [  334.576173] [  334.576351]
> ---[ end trace c291179c5ae60576 ]---

It is known issue, and fixed in fw. And the future fw release will have 
the fix.

Thanks,
Bhagavathi.

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k