From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Robert Shade <robert.shade@gmail.com>,
Christian Lamparter <chunkeey@googlemail.com>,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
Marco Fonseca <marco@tampabay.rr.com>
Subject: Re: [ath9k-devel] Auth Packet TX Delay
Date: Tue, 26 Mar 2013 10:27:52 -0700 [thread overview]
Message-ID: <5151DA98.7030903@candelatech.com> (raw)
In-Reply-To: <CAJ-VmontjZ2+RWCK50gf5RADkMeCbCc=HfstVAffkCHCtTmNew@mail.gmail.com>
On 03/26/2013 10:16 AM, Adrian Chadd wrote:
> ... and the odd thing here is that during scanning, it should be
> flushing the queues entirely so any new frame being transmitted
> _SHOULD_ result in:
>
> * TxDP for that queue being written (either FIFO or otherwise);
> * TxE for that queue being set.
>
> So unless the queue is "full" already and isn't being drained, I'm
> kinda curious as to why TX isn't starting.
At least for the problems I saw, it was fairly easy to spot the
problem once you looked at the xmit debugfs file. There would
be 127 pending-frames, axq-depth and ampdu-depth were zero,
queue is stopped, and it stays like that for many seconds or minutes.
Just resetting the NIC didn't help...I had to also tell the reset to
not retry any packets and to set the pending-frames to zero. After
that, packets started transmitting again, and often after several
seconds I'd see at least most of the old stuck packets be processed
to one degree or another (pending frames would go negative since I
had forced it to zero earlier).
I still do not know the root cause of this, nor have I had time to look
at it in any more detail..the work-around is good enough for me for now
and I have higher priority issues currently...
I only saw the problem in the data queue (BE), but maybe it can happen
in other queues as well.
Or of course it could be completely un-related to the problem in
this email thread....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-03-26 17:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMgrJ3Y9=K4umoLD=htrrW-Wn4Hgi7qfaKDpY55_GKd=KgD==A@mail.gmail.com>
2013-01-15 22:06 ` Auth Packet TX Delay Robert Shade
2013-01-16 23:09 ` Adrian Chadd
2013-01-17 1:00 ` Robert Shade
2013-01-17 3:12 ` Adrian Chadd
2013-02-06 2:51 ` Robert Shade
2013-02-06 3:08 ` Adrian Chadd
2013-02-06 12:53 ` Robert Shade
2013-02-06 22:58 ` Robert Shade
2013-02-07 5:06 ` Adrian Chadd
2013-02-07 16:25 ` [ath9k-devel] " David Littell
2013-02-07 19:43 ` Robert Shade
2013-02-07 21:40 ` Adrian Chadd
2013-02-08 18:48 ` Robert Shade
2013-02-09 7:39 ` Adrian Chadd
2013-03-24 18:55 ` Robert Shade
2013-03-24 21:52 ` Adrian Chadd
2013-03-24 22:40 ` Robert Shade
2013-03-24 22:58 ` Christian Lamparter
2013-03-25 0:03 ` Adrian Chadd
2013-03-25 2:23 ` Adrian Chadd
2013-03-25 16:12 ` Christian Lamparter
2013-03-25 16:45 ` Adrian Chadd
2013-03-26 12:21 ` Robert Shade
2013-03-26 13:23 ` Robert Shade
2013-03-26 16:28 ` Adrian Chadd
2013-03-26 16:29 ` Robert Shade
2013-03-26 17:13 ` [ath9k-devel] " Ben Greear
2013-03-26 17:16 ` Adrian Chadd
2013-03-26 17:27 ` Ben Greear [this message]
2013-03-26 17:33 ` Adrian Chadd
2013-03-26 17:45 ` Ben Greear
2013-03-27 0:55 ` Robert Shade
2013-03-27 3:11 ` Robert Shade
2013-03-27 16:33 ` Adrian Chadd
2013-03-26 17:14 ` Adrian Chadd
2013-03-26 14:13 ` Marco Fonseca
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=5151DA98.7030903@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marco@tampabay.rr.com \
--cc=robert.shade@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).