From: Fabio Rossi <rossi.f@inwind.it>
To: linux-wireless@vger.kernel.org
Cc: Michael Buesch <mb@bu3sch.de>, Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: ath5k: no further txbuf available, dropping packet
Date: Mon, 26 Oct 2009 21:57:36 +0100 [thread overview]
Message-ID: <200910262157.36141.rossi.f@inwind.it> (raw)
In-Reply-To: <200910231608.18676.mb@bu3sch.de>
On Friday 23 October 2009 16:08:16 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
I got the same message but in managed mode with the latest git wireless
testing (v2.6.32-rc5-40584-g9b469da)
prev parent reply other threads:[~2009-10-26 21:00 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
2009-10-24 15:05 ` Michael Buesch
2009-10-24 15:32 ` Michael Buesch
2009-10-26 20:57 ` Fabio Rossi [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=200910262157.36141.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mb@bu3sch.de \
--cc=me@bobcopeland.com \
--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 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.