From: Larry Finger <Larry.Finger@lwfinger.net>
To: openwrt-devel@lists.openwrt.org, linux-wireless@vger.kernel.org,
Bastian Bittorf <bittorf@bluebottle.com>
Subject: Re: WRT54g / b43 / mac802.11 BREAKTHROUGH
Date: Sun, 17 Feb 2013 19:49:09 -0600 [thread overview]
Message-ID: <51218895.1050602@lwfinger.net> (raw)
In-Reply-To: <20130214203553.GA27934@medion.lan>
On 02/14/2013 02:35 PM, Bastian Bittorf wrote:
Bastian,
> * Bastian Bittorf <bittorf@bluebottle.com> [18.07.2012 17:43]:
>> 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.
>
> [...]
>
> another issues was found, see https://dev.openwrt.org/ticket/7552#comment:69
>
> "...under high load and have found that probably some of the silent freezes
> are due to overflow of the RX DMA buffer, seems like b43 does not
> handlre such a situation at all."
>
> https://dev.openwrt.org/attachment/ticket/7552/840-b43-workaround-rx-fifo-overflow.patch
>
> the patch is working so far, but is only a workaround.
> has somebody a better code-idea?
Changing the maximum number of slots is certainly the correct thing to do.
Making that change on a netbook that would hang on high throughput cured its
problem. After some heavy usage, I found the following in the dmesg output:
b43-phy0 debug: DMA-64 rx_ring: Used slots 109/128, Failed frames 0/0 = 0.0%,
===================
Clearly 64 slots is not sufficient. I am currently testing to see how large it
can be made as I am not sure that 128 gives enough free space.
Larry
prev parent reply other threads:[~2013-02-18 2:16 UTC|newest]
Thread overview: 29+ 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
2012-08-22 16:21 ` Hauke Mehrtens
2012-08-22 17:00 ` G.W. Haywood
2012-08-22 17:49 ` Rafał Miłecki
2012-08-22 17:49 ` Rafał Miłecki
2012-08-22 18:17 ` Hauke Mehrtens
2012-08-22 18:17 ` Hauke Mehrtens
2012-08-22 18:45 ` Larry Finger
2012-08-22 18:45 ` Larry Finger
2012-08-22 21:05 ` Hauke Mehrtens
2012-08-22 21:05 ` Hauke Mehrtens
2012-08-22 21:19 ` Larry Finger
2012-08-22 21:19 ` Larry Finger
2012-08-25 14:50 ` Hauke Mehrtens
2012-08-25 14:50 ` Hauke Mehrtens
2012-08-24 17:18 ` Bastian Bittorf
2012-08-24 17:18 ` Bastian Bittorf
2012-08-24 17:13 ` 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 [this message]
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=51218895.1050602@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bittorf@bluebottle.com \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-devel@lists.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 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.