linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Rossi <rossi.f@inwind.it>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org,
	Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
	ath5k-devel@lists.ath5k.org
Subject: Re: ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet"
Date: Fri, 8 Jan 2010 23:34:16 +0100	[thread overview]
Message-ID: <201001082334.16066.rossi.f@inwind.it> (raw)
In-Reply-To: <b6c5339f0911102013k20d927d3mc021d25bf6703303@mail.gmail.com>

Hi Bob,
I have tried your patch as I get many errors as in subject when I transfer 
huge files (I'm using as a test a 1GB file). With the patch I have the same 
errors.

I'm using wireless-testing.git (v2.6.33-rc2-47131-gc72a18c) in managed mode 
(no AP).

Fabio

On Wednesday 11 November 2009 05:13:03 Bob Copeland wrote:

> Yes, there is a good reason (there are no buffers for the hardware to
> play with).  Actually mac80211 tx is never supposed to return anything
> but TX_OK.
> 
> Try this patch (it needs work which is why it's not upstream yet):
> 
> http://patchwork.kernel.org/patch/56785/
> 

  parent reply	other threads:[~2010-01-08 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 17:12 ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" Arnd Hannemann
2009-11-11  4:13 ` Bob Copeland
2009-12-14 15:30   ` ath5k: 2.6.32-rc6 David Srbecky
2010-01-08 22:34   ` Fabio Rossi [this message]
2010-01-09  3:41     ` ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" Bob Copeland
2010-01-12  0:19       ` Fabio Rossi
2010-01-12 16:35         ` Bob Copeland
2010-01-13 21:28           ` Fabio Rossi
2010-01-20 10:39   ` ath5k: 2.6.32-rc6 &quot;no further txbuf available, dropping packet&quot; Pavel Ulpi

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=201001082334.16066.rossi.f@inwind.it \
    --to=rossi.f@inwind.it \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=hannemann@nets.rwth-aachen.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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).