All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Bob Copeland <me@bobcopeland.com>
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 17:32:38 +0200	[thread overview]
Message-ID: <200910241732.40651.mb@bu3sch.de> (raw)
In-Reply-To: <200910241705.39104.mb@bu3sch.de>

On Saturday 24 October 2009 17:05:37 Michael Buesch wrote:
> On Saturday 24 October 2009 15:19:29 Bob Copeland wrote:
> > 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);
> >         }
> > 
> 
> I didn't try this, yet, but PS buffering seems to be broken anyway.
> If I connect the n810 (which does PS) to the ath5k AP, I cannot ping
> the n810 unless I also transfer (ping) _from_ the n810 simultaneously.
> I did not monitor the traffic, yet, but to me it seems the AP is unable
> to notify that the PS device should wake up (TIM problems?). By pinging from
> the n810, I frequently force-wakeup the device, so traffic to the device
> also works (more or less).
> 

Ok on the monitor log it looks like the ath5k AP simply sends data while
the STA is in PS, instead of buffering it and updating the TIM.
So if I ping the STA, it keeps sending packets and doesn't set the TIM,
but don't get any repsonse of course, because the STA is power saving.
If I simultaneously ping from the STA, the buffering and TIM handling suddenly
seems to start working. The AP indicates traffic via TIM and the STA sends PS polls.

-- 
Greetings, Michael.

  reply	other threads:[~2009-10-24 15:32 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 [this message]
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=200910241732.40651.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --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 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.