From: Ben Greear <greearb@candelatech.com>
To: "ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath9k, multiple stations, and AMPDUs
Date: Mon, 20 Sep 2010 22:25:14 -0700 [thread overview]
Message-ID: <4C9841BA.4080700@candelatech.com> (raw)
I think I have narrowed down some problems I see when I create
two STA interfaces on the same radio and associate with the
same AP.
I'm using wireless-testing plus some patches to the rx logic
I posted earlier.
It appears that the ath9k NIC does not transport AMPDUs properly,
and after a few seconds, it's backlog is exhausted and the queues
are stopped in ath_tx_start.
debugfs seems to agree:
[root@atom ~]# cat /debug/ath9k/phy0/xmit
BE BK VI VO
MPDUs Queued: 2 0 0 85
MPDUs Completed: 2 0 0 85
Aggregates: 0 0 0 0
AMPDUs Queued: 144 0 0 0
AMPDUs Completed: 20 0 0 0
AMPDUs Retried: 18 0 0 0
AMPDUs XRetried: 0 0 0 0
FIFO Underrun: 0 0 0 0
TXOP Exceeded: 0 0 0 0
TXTIMER Expiry: 0 0 0 0
DESC CFG Error: 0 0 0 0
DATA Underrun: 0 0 0 0
DELIM Underrun: 0 0 0 0
[root@atom ~]#
I can still receive packets on the interface, but nothing is
transmitted.
I tested against an a/b/g AP (instead of N), and it ran clean
for many minutes.
Any ideas how to debug this further?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-09-21 5:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 5:25 Ben Greear [this message]
2010-09-21 10:10 ` [ath9k-devel] ath9k, multiple stations, and AMPDUs Felix Fietkau
2010-09-21 12:08 ` Ben Greear
2010-09-21 12:19 ` Felix Fietkau
2010-09-21 12:24 ` Johannes Berg
2010-09-21 12:31 ` Johannes Berg
2010-09-21 17:25 ` Ben Greear
2010-09-21 18:00 ` Felix Fietkau
2010-09-21 18:04 ` Ben Greear
2010-09-21 18:06 ` Felix Fietkau
2010-09-21 19:28 ` Johannes Berg
2010-09-21 19:32 ` Felix Fietkau
2010-09-21 20:19 ` Ben Greear
2010-09-21 22:41 ` Felix Fietkau
2010-09-22 4:33 ` Ben Greear
2010-09-22 8:31 ` Felix Fietkau
2010-09-23 4:58 ` Ben Greear
2010-09-23 8:33 ` Johannes Berg
2010-09-23 13:56 ` Ben Greear
2010-09-23 14:05 ` Johannes Berg
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=4C9841BA.4080700@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).