From: Michael Buesch <mb@bu3sch.de>
To: Bob Copeland <me@bobcopeland.com>
Cc: dsrbecky@gmail.com, Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: ath5k phy0: no further txbuf available, dropping packet
Date: Mon, 26 Oct 2009 22:34:31 +0100 [thread overview]
Message-ID: <200910262234.33711.mb@bu3sch.de> (raw)
In-Reply-To: <200910262230.57957.mb@bu3sch.de>
On Monday 26 October 2009 22:30:55 Michael Buesch wrote:
> On Monday 26 October 2009 21:52:39 David Srbecky wrote:
> > I am getting this error as well.
>
> Ok, I looked at the code a bit and this looks strange to me.
> There's the TX status handler in base.c which basically looks like this:
>
>
> loop_over_queued_packets() {
> ret = sc->ah->ah_proc_rx_desc(sc->ah, ds, &rs);
Typo. I meant ah_proc_tx_desc()
> if (unlikely(ret == -EINPROGRESS))
> break;
> free_packet_and_return_bufferhead_to_pool();
> }
>
> So the ah_proc_rx_desc callback looks like this:
>
> ah_proc_rx_..._desc()
same here
> {
> ...
> /* No frame has been send or error */
> if (unlikely(!(tx_status->tx_status_1 & AR5K_DESC_TX_STATUS1_DONE)))
> return -EINPROGRESS;
> ...
> }
--
Greetings, Michael.
next prev parent reply other threads:[~2009-10-26 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 20:52 ath5k phy0: no further txbuf available, dropping packet David Srbecky
2009-10-26 21:30 ` Michael Buesch
2009-10-26 21:34 ` Michael Buesch [this message]
2009-10-27 10:09 ` Bob Copeland
2009-10-27 10:29 ` Michael Buesch
2009-11-08 18:12 ` David Srbecky
2009-11-09 15:55 ` Bob Copeland
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=200910262234.33711.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=dsrbecky@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--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 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).