linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Bastian Bittorf <bittorf@bluebottle.com>
Cc: openwrt-devel@lists.openwrt.org, linux-wireless@vger.kernel.org,
	feint@lists.subsignal.org, "Rafał Miłecki" <zajec5@gmail.com>,
	b43-dev <b43-dev@lists.infradead.org>
Subject: Re: WRT54g / b43 / mac802.11 BREAKTHROUGH
Date: Wed, 22 Aug 2012 18:21:26 +0200	[thread overview]
Message-ID: <50350706.609@hauke-m.de> (raw)
In-Reply-To: <1342612598.5006a476022c6@mail.bluebottle.com>

On 07/18/2012 01:56 PM, Bastian Bittorf wrote:
> hi devs!
> 
> yesterday we had a breaktrough debugging b43 in our hackspace maschinenraum/m18[1,2]
> at weimar.freifunk.net[3,4] - since a long time our darling wrt54g suffers from a
> hanging wifi and bad performance[5], but the workaround is easy: now it's up to
> you to fix the rootcause.
> 
> our testsetup, where we could _reproduce_ reliably a stopping TX is like this:
> 
> laptop ---lan--- "A"-wrt54g/adhoc ~~~   air  ~~~ "B"-anyrouter/adhoc
> 
> now make a testdownload with the laptop from B.
> wireless will stop working after ~10 seconds.
> 
> wifi up will reanimate and our freifunk-cron.minutely-check
> will do this automagically. (read further, this is not the solution)
> 
> we tried to limit the rateset to e.g. lower rates, but this does NOT change
> the behaviour. what works is: define a rateset on BOTH router which makes
> it impossible to change the band, e.g.:
> 
> iw dev $WIFIDEV set bitrates legacy-2.4 1 2 5.5 11
> OR
> iw dev $WIFIDEV set bitrates legacy-2.4 6 9 12 18 24 36 48 54
> 
> now we had a great performance, 10 Gigabytes of wireless transfer,
> no stopping TX anymore and an empty box of beer. three things to do now:
> 
> 1) why does a band change (can be seen through minstrel) is a problem?
> 
> 2) we have to make in config-option to force a band, or a rateset:
> 	e.g. uci set wireless.radio0.hwmode=11g
> 	e.g. uci set wireless.radio0.bitrates='6 9 12 18 24 36 48 54'
> 
> 3) spread to word:
>    there is a great frustration in the community about b43,
>    but the old drivers _have_ to die, it's about time - really.
> 
> thanks for your work,
> bye storchi, andi, bastian + m18 crew
> 
> [1] http://blog.maschinenraum.tk/
> [2] http://blog.maschinenraum.tk/2012/07/15/bitcoin-vending-machine-exchange-euro-coins-for-bitcoin-wallets/
> [3] http://wireless.subsignal.org
> [4] http://wireless.subsignal.org/index.php?title=Main_Page_en
> [5] https://dev.openwrt.org/ticket/7552

I tried this on some of my devices (BCM4318 G-PHY and BCM4322 N-PHY) and
it is easily reproducible on all tested devices when restricting the
rates to 11 and 12 MBit/s.

I have the Broadcom device working as an Access point (on a MIPS SoC)
and a Laptop with an Intel Wifi device is connected to it. I generated
the traffic with iperf. If the Access Points sends the traffic the
problem occurs, if it is just receiving there is not problem.

After the problem occurred b43_generate_txhdr is called rarely ( every
~10 seconds) and I am not able to stay connected or connect to the
network any more. I am not familiar with the internal flow in b43 or
mac80211 could someone give me a hint where to look.

I can not see any special changes between CCK and OFDM rates before it
goes down there are many changes without a problem before it goes down.

Currently I do not have a Broadcom wifi card running in a x86 device
just mips devices could someone try to reproduce the problem on a x86
device.

I added the b43 mailing list and Rafał.

Hauke

  parent reply	other threads:[~2012-08-22 16:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 11:56 WRT54g / b43 / mac802.11 BREAKTHROUGH Bastian Bittorf
2012-07-19  1:40 ` Gábor Stefanik
2012-07-19  7:18   ` Andreas Bräu
2012-07-19 10:03     ` [maschinenraum] " npl
2012-07-19 14:59     ` Larry Finger
2012-07-20  9:50       ` Bastian Bittorf
2012-07-20  9:06   ` Bastian Bittorf
2012-08-22 16:21 ` Hauke Mehrtens [this message]
2012-08-22 17:00   ` G.W. Haywood
2012-08-22 17:49   ` Rafał Miłecki
2012-08-22 18:17     ` Hauke Mehrtens
2012-08-22 18:45   ` Larry Finger
2012-08-22 21:05     ` Hauke Mehrtens
2012-08-22 21:19       ` Larry Finger
2012-08-25 14:50         ` Hauke Mehrtens
2012-08-24 17:18       ` Bastian Bittorf
2012-08-24 17:13     ` Bastian Bittorf
2013-02-14 20:35 ` Bastian Bittorf
2013-02-15 19:47   ` Larry Finger
2013-02-18  1:49   ` Larry Finger

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=50350706.609@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=b43-dev@lists.infradead.org \
    --cc=bittorf@bluebottle.com \
    --cc=feint@lists.subsignal.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=zajec5@gmail.com \
    /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).