From: Andreas Hartmann <andihartmann@freenet.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: Compat-wireless-3.2-rc6-3 is broken for rt2860 device
Date: Thu, 05 Jan 2012 09:44:15 +0100 [thread overview]
Message-ID: <4F0562DF.3000200@dualc.maya.org> (raw)
In-Reply-To: <1408490.qSFZVkU7fA@helmutmobil.site>
Helmut Schaa schrieb:
> Hi,
>
> Am Mittwoch, 4. Januar 2012, 09:38:02 schrieb Andreas Hartmann:
>> Helmut Schaa schrieb:
>>>> Removing this patch
>>>>
>>>> mac80211: retry sending failed BAR frames later instead of tearing down
>>>> aggr (http://www.spinics.net/lists/linux-wireless/msg76379.html) makes
>>>> it working again.
>>>>
>>>> Device is: RaLink RT2800 802.11n PCI
>>>
>>> What's the client device connected to the rt2x00 AP?
>>
>> It's a rt3572 usb chip (Linksys WUSB600N v2), driven with the rt3572sta
>> module.
>>
>>> Mind to send a
>>> 802.11 capture wen this stall happens?
>
> Andreas provided me with a capture now. The interesting part is that
> the rt2x00 AP sends bursts of BARs with the same sequence number when
> the stall happens. I only had a quick look at the code in question but
> couldn't see anything wrong at a first glance.
Some additional information:
- The AP initiates BARs for 6 different, successive sequence numbers.
- The first 5 sequence numbers are finished after sending of about 8 (!)
BAR's.
Important: each BAR is responded *instantly* by the STA.
- The BAR for the next sequence number is sent "endless" though the STA
responses to each BAR instantly again.
Another thing: it is striking, that the performance from STA -> AP is at
max 8,5 MBit/s, whereas the performance from AP -> STA can be 15 MBit/s
(all measured with netperf).
Could it be, that somewhere in the stack of the AP the response packet
from STA -> AP get's lost or ignored or blocked?
Kind regards,
Andreas
next prev parent reply other threads:[~2012-01-05 8:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 13:49 Compat-wireless-3.2-rc6-3 is broken for rt2860 device Andreas Hartmann
2011-12-31 20:35 ` Andreas Hartmann
2012-01-03 21:51 ` Helmut Schaa
2012-01-04 8:38 ` Andreas Hartmann
2012-01-04 15:04 ` Helmut Schaa
2012-01-05 8:44 ` Andreas Hartmann [this message]
2012-01-09 10:23 ` Helmut Schaa
2012-01-09 13:29 ` Andreas Hartmann
2012-01-09 13:45 ` Helmut Schaa
2012-01-10 8:03 ` Andreas Hartmann
2012-01-10 9:50 ` Helmut Schaa
2012-01-10 11:56 ` Andreas Hartmann
2012-01-10 12:23 ` Helmut Schaa
2012-01-10 13:01 ` Andreas Hartmann
2012-01-10 13:43 ` Helmut Schaa
2012-01-10 14:41 ` Andreas Hartmann
2012-01-17 9:09 ` Andreas Hartmann
2012-01-20 7:29 ` Andreas Hartmann
2012-01-23 13:29 ` Helmut Schaa
2012-01-23 16:03 ` Andreas Hartmann
2012-01-23 16:36 ` Helmut Schaa
2012-01-23 17:44 ` Andreas Hartmann
2012-01-24 8:07 ` Helmut Schaa
2012-01-24 14:39 ` Stanislaw Gruszka
2012-01-24 15:19 ` Helmut Schaa
2012-01-24 7:29 ` Stanislaw Gruszka
2012-01-24 8:01 ` Andreas Hartmann
2012-01-24 8:06 ` Helmut Schaa
2012-01-04 12:29 ` Andreas Hartmann
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=4F0562DF.3000200@dualc.maya.org \
--to=andihartmann@freenet.de \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).