From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/2] ath10k: fix mu-mimo rx status reporting
Date: Wed, 9 Sep 2015 12:33:23 +0300 [thread overview]
Message-ID: <877fo09bto.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1440679653-20289-2-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 27 Aug 2015 14:47:33 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> MU-MIMO Rx involves different interpretation of
> the VHT-SIG-A compared to SU-MIMO.
>
> The incorrect interpretation led ath10k to report
> VHT MCS values greater than 9 which subsequently
> prompted mac80211 to drop such frames. This
> effectively broke Rx with MU-MIMO in many cases
> and manifested with a kernel warning in the log
> which looked like this:
>
> [ 14.552520] WARNING: CPU: 2 PID: 0 at net/mac80211/rx.c:3578 ieee80211_rx+0x26c/0x940 [mac80211]()
> [ 14.552522] Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2
> ... call trace follows ...
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Thanks, patch 2 applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-09-09 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 12:47 [PATCH 1/2] ath10k: change beamformee VHT STS capability Michal Kazior
2015-08-27 12:47 ` [PATCH 2/2] ath10k: fix mu-mimo rx status reporting Michal Kazior
2015-09-09 9:33 ` Kalle Valo [this message]
2015-08-28 12:56 ` [PATCH 1/2] ath10k: change beamformee VHT STS capability Bartosz Markowski
2015-09-02 11:25 ` Bartosz Markowski
2015-09-02 13:55 ` Kalle Valo
2015-09-02 14:45 ` Bartosz Markowski
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=877fo09bto.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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