From: Bob Copeland <me@bobcopeland.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: ath5k: no further txbuf available, dropping packet
Date: Sat, 24 Oct 2009 09:19:29 -0400 [thread overview]
Message-ID: <20091024131929.GB31897@hash.localnet> (raw)
In-Reply-To: <200910231608.18676.mb@bu3sch.de>
On Fri, Oct 23, 2009 at 04:08:16PM +0200, Michael Buesch wrote:
> ath5k breaks in AP mode after some operation time and keeps throwing
> this message:
>
> [2096249.446071] ath5k phy0: no further txbuf available, dropping packet
>
> Driver is yesterday's compat-wireless on 2.6.31.1
Ok looked a bit more at this. I don't see a leak, but I think the
txbufs aren't getting reaped. Otherwise, we should reenable the queues
when we get back 40 TX completion interrupts.
I'm a bit short on time to track it down, but one thing to try is
commenting out the following from ath5k_beacon_send (will break buffering
but you can test non-ps clients):
skb = ieee80211_get_buffered_bc(sc->hw, sc->vif);
while (skb) {
ath5k_tx_queue(sc->hw, skb, sc->cabq);
skb = ieee80211_get_buffered_bc(sc->hw, sc->vif);
}
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-10-24 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 14:08 ath5k: no further txbuf available, dropping packet Michael Buesch
2009-10-23 14:36 ` Bob Copeland
2009-10-24 13:19 ` Bob Copeland [this message]
2009-10-24 15:05 ` Michael Buesch
2009-10-24 15:32 ` Michael Buesch
2009-10-26 20:57 ` Fabio Rossi
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=20091024131929.GB31897@hash.localnet \
--to=me@bobcopeland.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mb@bu3sch.de \
--cc=mickflemm@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).