All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: linux-wireless@vger.kernel.org
Subject: Compat-wireless-3.2-rc6-3 is broken for rt2860 device
Date: Sat, 31 Dec 2011 14:49:13 +0100	[thread overview]
Message-ID: <4EFF12D9.3010602@01019freenet.de> (raw)

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 :-).


So far, I removed the following patches from compat-wireless-3.2-rc6-3:

mac80211: fix race between the AGG SM and the Tx data path
mac80211: don't stop a single aggregation session twice
mac80211: uAPSD - fix IEEE80211_FCTL_MOREDATA bit setting
mac80211: fix race condition caused by late addBA response

But they seem not to be the culprit.


I tried to remove these patches, too, but this wasn't possible:

mac80211: don't stop a single aggregation session twice
mac80211: fix another race in aggregation start



Does anybody has an idea, which patch could have raised this problem?



Kind regards,
Andreas Hartmann

             reply	other threads:[~2011-12-31 14:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 13:49 Andreas Hartmann [this message]
2011-12-31 20:35 ` Compat-wireless-3.2-rc6-3 is broken for rt2860 device 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
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=4EFF12D9.3010602@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.