From: Andreas Hartmann <andihartmann@01019freenet.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: Wed, 04 Jan 2012 09:38:02 +0100 [thread overview]
Message-ID: <4F040FEA.3080703@01019freenet.de> (raw)
In-Reply-To: <2766356.70ylY68Gqi@helmutmobil.site>
Hi Helmut,
happy new year for you, too!
Helmut Schaa schrieb:
> Hi Andreas,
>
> Am Samstag, 31. Dezember 2011, 21:35:04 schrieb Andreas Hartmann:
>> Andreas Hartmann schrieb:
>>> Hello,
>>>
>>> I tested compat-wireless-3.2-rc6-3 with kernel 3.1 and a rt2860 device
>>> running in AP mode (80211.n - 40 MHz). During
>>>
>>> netperf -t TCP_STREAM -H ap
>>>
>>> the data stream mostly stalls (-> the device receives data) after a few
>>> seconds and never comes up any more. The connection is completely death.
>>> I have to restart wpa_supplicant to get it working again.
>>>
>>>
>>>
>>> I tried to isolate the problem the following way:
>>>
>>> 1. Running compat-wireless-3.2-rc6-3 with the rt2x00 level from
>>> compat-wireless-3.1.1-1. The problem didn't gone.
>>>
>>> 2. Running compat-wireless-3.1.1-1 with the rt2x00 based changes in
>>> compat-wireless-3.2-rc6-3. I can't see the problem any more.
>>>
>>>
>>> That's why I think, that the problem must be outside the rt2x00 changes.
>>> But there are many changes outside :-).
>>
>>
>> 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?
I would try to scan the traffic with a third device in monitor mode
(airmon-ng). But: 802.11n uses more than one channel. How can I get
them? airmon-ng can't be told to listen to more than one channel at a
time (or better: I probably don't know how to do it :-)).
Do you have an idea, how to completely trace 802.11n?
Thanks,
Andreas
next prev parent reply other threads:[~2012-01-04 8:40 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 [this message]
2012-01-04 15:04 ` Helmut Schaa
2012-01-05 8:44 ` Andreas Hartmann
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=4F040FEA.3080703@01019freenet.de \
--to=andihartmann@01019freenet.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).