From: Ben Greear <greearb@candelatech.com>
To: Chaoxing Lin <Chaoxing.Lin@ultra-3eti.com>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Help on AMPDU stuck in transmit queue
Date: Thu, 16 Jun 2011 09:04:25 -0700 [thread overview]
Message-ID: <4DFA2989.10503@candelatech.com> (raw)
In-Reply-To: <BD54DDEB2546894FAB0731EA7B0EDF8D05822A57@RockMX01.rock.corp>
On 06/16/2011 07:32 AM, Chaoxing Lin wrote:
> Hi Linux wireles experts,
>
> Here is my problem. If anyone can throw some ideas, I would appreciate it.
>
> I have a customized router board which has one wireless card (ath9160) and one Ethernet port. The ath9160 is (and must be) put in client mode. My customization is to translate packet strictly between Ethernet port and wireless port so that the board can be used for old PC to access wireless network.
>
> I am running kernel 2.6.38.5. I made a mini module which always forwards data packets between wireless port and Ethernet port.
> In addition, I made two small changes as follows.
> 1. On wireless Tx path (in ieee80211_subif_start_xmit() defined in mac80211). The change is to replace source address (the MAC of old PC) with wireless radio MAC (ath9160).
> 2. On wireless Rx path (in ieee80211_deliver_skb() defined in mac80211). The change is to replace destination address (ath9160 MAC) with MAC of my old PC.
>
> My customization works very well when 802.11n is disabled on AP which is hostapd based on nl80211 driver.
> When 802.11n is enabled on AP, my customization works only for the first few minutes. (Ping packets from old PC to AP go through well). After a few minutes, wireless radio (ath9160) on my customized router board won't transmit any ping packet. I see AMPDU stuck in transmit queue based on the info from /debugfs/ieee80211/phy0/ath9k/xmit as follows
>
> BE BK VI VO
>
> MPDUs Queued: 126 0 0 4261
> MPDUs Completed: 126 0 0 4261
> Aggregates: 0 0 0 0
> AMPDUs Queued: 4002 0 0 0
> AMPDUs Completed: 3877 0 0 0
> AMPDUs Retried: 0 0 0 0
> AMPDUs XRetried: 1 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
> TX-Pkts-All: 4004 0 0 4261
> TX-Bytes-All: 462852 0 0 105128
>
>
> I noticed that when 11n is disable, MPDUs are sent and the "MPDUs queued" == "MPDUs completed".
> When 11n is enabled, AMPDUs are sent and the "AMPDUs queued"=="AMPDUs Complete" only for the first few minutes. After that, "AMPDUs Complete" stop incrementing.
>
> I also sniffed the air, the "NULL data packet" is still sent out as usual (it's also reflected in the number "MPDUs Queued and Completed" in VO queue). But no ping packets at all.
>
> Without my customization, the wireless client (standalone) on router board works very well with the AP with 11n enabled. This eliminates the AP or client issue.
>
> I also tried another radio (ar9380). The symptom is exactly the same.
>
> Any help on the following is highly appreciated.
> 1. Point out the issue, or
> 2. Throw some idea on how to investigate, or
> 3. Tell me how that AMPDU works in ath9k (mac80211).
> 4. Anywhere in ath9k or mac80211 that is sensitive to the address change.
You might try a later kernel. I saw problems of this type too a while back,
but not lately. (I'm using 2.6.39-wl+ for most testing, though the
latest linus 3.0.0-rc3 kernel seems to work fine too in limited testing.)
Thanks,
Ben
>
>
> Thanks
>
> Chaoxing
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-16 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 14:32 Help on AMPDU stuck in transmit queue Chaoxing Lin
2011-06-16 16:04 ` Ben Greear [this message]
2011-06-21 16:16 ` Chaoxing Lin
2011-06-21 20:10 ` Emmanuel Grumbach
2011-06-22 13:56 ` Chaoxing Lin
2011-06-22 18:40 ` Emmanuel Grumbach
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=4DFA2989.10503@candelatech.com \
--to=greearb@candelatech.com \
--cc=Chaoxing.Lin@ultra-3eti.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).