From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted
Date: Thu, 29 Apr 2010 22:21:27 +0200 [thread overview]
Message-ID: <4BD9EA47.9080505@free.fr> (raw)
In-Reply-To: <1272530496.5866.50.camel@tor-desktop>
Tor Krill a ?crit :
> On Thu, 2010-04-29 at 16:26 +0800, Daniel Yingqiang Ma wrote:
>
>> This patch indeed improve the link quality of my AP powered by ath9k.
>>
>> It seems there are plenty of this kind of corruptted packet. Any one
>> know it's reason?
>>
>
> FYI,
>
> This patch, in modified form went into wireless-testing and linux-next a
> few days ago
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=3a37495268ab45507b4cab9d4cb18c5496ab7a10
>
> And it indeed fixed a lot of our issues :). Unfortunately we still
> experience failures with ath9k in AP mode with these symptoms.
>
> We lose connectivity on STA side, we still seems to be associated but
> are unable to transfer any data. Any reconnection fails.
>
> A strange observation is that in some/all(?) cases we are able to
> associate using a STA in pure A/G-mode and transfer data.
>
> If anyone is interested we would gladly provide dumps/debug information
> on this. (Gathering dumps as we speak)
>
> /Tor
>
>
I'm experiencing the very same : Using an ath9k STA to connect with a
802.11abg AP is fine (even if it is ath9k in 802.11a/g mode!), but using
ath9k STA to connect to a 802.11n AP leads to poor performance and after
some time, it fails to connect even to a 802.11ag AP.... Reloading the
kernel module and I'm back online.
I have done lots of capture and observed few things :
- BlockAckRequest never show up (I am wondering if they are filtered by
the monitor code or simply not sent)
- in syslog, I got lots of message like : "phy0: release an RX reorder
frame due to timeout on earlier frames"
- performance are bad (like 1 or 2 Mbits) even if everything is sent at
MCS7 (confirmed by minstrel_ht rate control).
- in capture, there is often a 1 .. 3 ms delay with previous frames.
Regards,
Benoit
next prev parent reply other threads:[~2010-04-29 20:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 19:10 [ath9k-devel] ath9k: receive stops working in AP-mode and 802.11n Johan Hovold
2010-04-16 10:48 ` [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted (was: ath9k: receive stops working in AP-mode and 802.11n) Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 1/6] ath9k: clean up rx skb post-process logic Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 2/6] ath9k: do not mark frames with RXKEY_IX_INVALID as decrypted Johan Hovold
2010-04-16 11:32 ` Jouni Malinen
2010-04-20 8:35 ` Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 3/6] ath9k: do not mark frames with RX_DECRYPT_BUSY " Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 4/6] ath9k: do not mark frames with RX_KEY_MISS " Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 5/6] ath9k: check error flags even if rx frame is marked ok Johan Hovold
2010-04-16 10:52 ` [ath9k-devel] [RFC][PATCH 6/6] ath9k: clear mic error flag on encrypted frames Johan Hovold
2010-04-20 8:25 ` [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted Johan Hovold
2010-04-20 8:28 ` [ath9k-devel] [RFC][PATCH 1/2] ath9k: fix corrupt frames being forwarded to mac80211 Johan Hovold
2010-04-20 8:38 ` Johan Hovold
2010-04-20 8:28 ` [ath9k-devel] [RFC][PATCH 2/2] ath9k: use also AR_DecryptBusyErr to determine decrypt errors Johan Hovold
2010-04-20 9:10 ` [ath9k-devel] ath9k: corrupt frames forwarded to mac80211 as decrypted Ranga Rao Ravuri
2010-04-20 11:06 ` Johan Hovold
2010-04-20 11:35 ` Johan Hovold
2010-04-29 8:26 ` Daniel Yingqiang Ma
2010-04-29 8:41 ` Tor Krill
2010-04-29 9:35 ` Daniel Yingqiang Ma
2010-04-29 18:08 ` Ben Gamari
2010-04-29 20:08 ` Will Dyson
2010-04-30 9:07 ` Tor Krill
2010-04-29 20:21 ` Benoit PAPILLAULT [this message]
2010-04-30 9:50 ` Tor Krill
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=4BD9EA47.9080505@free.fr \
--to=benoit.papillault@free.fr \
--cc=ath9k-devel@lists.ath9k.org \
/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