linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: carl9170 A-MPDU transmit problem
Date: Fri, 22 Feb 2013 14:50:44 -0600	[thread overview]
Message-ID: <20130222205044.GD1418@thinkpad-t410> (raw)

Hi Christian,

I was given a D-Link wireless dongle by a colleague who said he was
having trouble with the connection stalling. One thing I noticed right
away when running iperf is that the tx BA sessions seem to be getting
stopped and restarted pretty frequently. I've been doing some debugging,
and here's what I'm seeing.

On the air everything seems to go smoothly for a while, but then the
D-Link adapter stops transmitting data frames for a while. It still
sends CTS and BA frames in response to the AP, just no data frames.
Eventually it sends the action frame with the DELBA request, but
immediately before sending the action frame it sends a single data
frame. This pattern repeats each time this happens.

That final data frame is a bit curious, so I added some tracing to
carl9170. It looks like this frame gets passed down to the hardware as
the last in a batch of A-MPDU frames, but for some reason the hardware
stops transmitting without sending this frame. carl9170 doesn't pass any
more A-MPDU frames to the hardware while tx for that frame is pending,
and when the action frame for the DELBA request finally comes along it
seems to get things moving again.

Do you have any idea what might be causing the hardware to stop
transmitting with one frame left? Any suggestions on how to fix it?

Thanks,
Seth


             reply	other threads:[~2013-02-22 20:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 20:50 Seth Forshee [this message]
2013-02-22 22:07 ` carl9170 A-MPDU transmit problem Christian Lamparter
2013-02-22 22:54   ` Seth Forshee
2013-02-22 23:48     ` Christian Lamparter
2013-02-23  6:46       ` Seth Forshee
2013-02-23 14:07         ` Christian Lamparter
2013-02-23 21:26           ` Alan Stern
2013-02-24  4:52           ` Seth Forshee
2013-02-24 15:54             ` Alan Stern
2013-02-24 22:30               ` Christian Lamparter
2013-02-24 23:41                 ` Alan Stern
2013-02-25 14:51                   ` Seth Forshee
2013-02-25 15:04                   ` Christian Lamparter
2013-02-25 15:29                     ` Alan Stern
2013-02-25 16:03                       ` Christian Lamparter
2013-02-25 19:13                         ` Sarah Sharp
2013-02-25 19:46                           ` Seth Forshee
2013-02-25 19:52                             ` Christian Lamparter
2013-02-25 20:19                             ` Alan Stern
2013-02-25 23:30                               ` Christian Lamparter
2013-02-26 16:50                                 ` Seth Forshee
2013-03-07 17:46                                   ` Seth Forshee
2013-03-07 23:37                                     ` Sarah Sharp
2013-02-25 22:42                             ` Seth Forshee
2013-02-25 20:23                           ` Seth Forshee
2013-02-25 14:44                 ` Seth Forshee

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=20130222205044.GD1418@thinkpad-t410 \
    --to=seth.forshee@canonical.com \
    --cc=chunkeey@googlemail.com \
    --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).