linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [WIP] p54: deal with allocation failures in rx path
Date: Sat, 04 Jul 2009 11:40:14 -0500	[thread overview]
Message-ID: <4A4F85EE.5090007@lwfinger.net> (raw)
In-Reply-To: <200907041211.49115.chunkeey@web.de>

Christian Lamparter wrote:
> 
> hmm, is it possible for you to log the usb transfer?
> A excellent tool for this is usbmon (userspace)... can be found here: 
> 	http://git.sipsolutions.net/usbmon.git
> 
> usbmon -s 3000 -i $(USB_ID) (which is usually number between 1 and the amount of connected usb devices))  > dst
> 
> and set p54common nohwcrypt=1, if you don't want to show GK/TK around ;-)

I have logged the usb transfers, but not yet analyzed them. This time
I got a new failure - I hit this warning at
           net/mac80211/tx.c:1299
                        retries++;
                        if (WARN(retries > 10, "tx refused but queue
active\n"))
                                goto drop;
                        goto retry;


If I have analyzed this correctly, I hit this section of
p54_tx_qos_accounting_alloc at drivers/net/wireless/p54/txrx.c:204.
I'm running the splitup patches.

        if (unlikely(queue->len > queue->limit &&
IS_QOS_QUEUE(p54_queue))) {
                spin_unlock_irqrestore(&priv->tx_stats_lock, flags);
                return -ENOSPC;
        }

Any suggestions on debugging this would be appreciated.

Larry


  reply	other threads:[~2009-07-04 16:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 22:53 [WIP] p54: deal with allocation failures in rx path Christian Lamparter
2009-07-04  1:09 ` Larry Finger
2009-07-04  2:16 ` Larry Finger
2009-07-04 10:11   ` Christian Lamparter
2009-07-04 16:40     ` Larry Finger [this message]
2009-07-04 17:28       ` Christian Lamparter
2009-07-04 19:56         ` Larry Finger
2009-07-04 21:14           ` Larry Finger
2009-07-05 13:59             ` Christian Lamparter
2009-07-05 17:49               ` Larry Finger
2009-07-05 22:05                 ` Christian Lamparter
2009-07-06  1:36                   ` Larry Finger
2009-07-06 13:16                     ` Christian Lamparter
2009-07-04  7:52 ` Johannes Berg
2009-07-05  0:56 ` Max Filippov
2009-07-05 14:00   ` Christian Lamparter
2009-07-05 19:16     ` Max Filippov
2009-07-05 22:46       ` Max Filippov
2009-07-06 13:11 ` Max Filippov
2009-07-06 14:00   ` Christian Lamparter
2009-07-06 14:18     ` Max Filippov

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=4A4F85EE.5090007@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).