From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k and stuck xmit queue?
Date: Thu, 06 Jan 2011 15:39:03 -0800 [thread overview]
Message-ID: <4D265297.4010009@candelatech.com> (raw)
In-Reply-To: <4D23C3A9.9020007@candelatech.com>
On 01/04/2011 05:04 PM, Ben Greear wrote:
> I added a patch to my tree to print out some extra info,
> in particular the 'axq-stopped' bit. I notice that when
> I have 60 STA interfaces sometimes it seems to get stuck
> and cannot send any data. A printout of the debug in that
> case is below.
I found a similar scenario, but to me even weirder:
Note that the queue is stopped, but has no depth, and not
even any pending frames?
I do notice that the hw-tx-start is less than the number of
processed descriptors. That seems to normally go along with
the tx-hang issues..perhaps caused by chip resets or similar?
hw-tx-start: 53128 0 0 37325
hw-tx-proc-desc: 53103 0 0 37200
txq-memory-address: de70b3d0 de70b464 de70b33c de70b2a8
axq-qnum: 2 3 1 0
axq-depth: 0 0 0 0
axq-ampdu_depth: 0 0 0 0
axq-stopped 1 0 0 0
tx-in-progress 0 0 0 0
pending-frames 0 0 0 0
txq_headidx: 0 0 0 0
txq_tailidx: 0 0 0 0
axq_q empty: 0 1 1 0
axq_acq empty: 1 1 1 1
txq_fifo_pending: 1 1 1 1
txq_fifo[0] empty: 1 1 1 1
txq_fifo[1] empty: 1 1 1 1
txq_fifo[2] empty: 1 1 1 1
txq_fifo[3] empty: 1 1 1 1
txq_fifo[4] empty: 1 1 1 1
txq_fifo[5] empty: 1 1 1 1
txq_fifo[6] empty: 1 1 1 1
txq_fifo[7] empty: 1 1 1 1
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-01-06 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 1:04 ath9k and stuck xmit queue? Ben Greear
2011-01-06 23:39 ` Ben Greear [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=4D265297.4010009@candelatech.com \
--to=greearb@candelatech.com \
--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).