From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 3.7.6+: ath9k: tx logic locks up after taking attenuation very high.
Date: Wed, 20 Feb 2013 21:41:51 -0800 [thread overview]
Message-ID: <5125B39F.3010200@candelatech.com> (raw)
In-Reply-To: <20773.31380.740958.31338@gargle.gargle.HOWL>
On 02/20/2013 05:38 PM, Sujith Manoharan wrote:
> Ben Greear wrote:
>> For instance, in this case, why do we have pending frames, the axq-stopped,
>> and no axq depth? Is that an invalid state to begin with? Once
>> it gets in the hung state, those numbers never change. I'd assume
>> something should be poking more packets out of the pending frames
>> down into the axq logic?
>
> Something is broken in the xmit path, definitely.
Ok, so here's a question: In the ath_tx_complete method,
the pending_frames counter is only decremented if txq == c->tx.txq_map[q].
Maybe it should always be decremented?
What kinds of things could cause txq to not equal the txq-map[q]?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-02-21 5:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:18 3.7.6+: ath9k: tx logic locks up after taking attenuation very high Ben Greear
2013-02-12 0:11 ` Sujith Manoharan
2013-02-13 16:41 ` Ben Greear
2013-02-19 2:14 ` Sujith Manoharan
2013-02-19 2:36 ` Sujith Manoharan
2013-02-19 5:18 ` Ben Greear
2013-02-20 22:51 ` Ben Greear
2013-02-21 1:06 ` Ben Greear
2013-02-21 1:38 ` Sujith Manoharan
2013-02-21 5:41 ` Ben Greear [this message]
2013-02-21 17:34 ` Ben Greear
2013-02-21 23:11 ` Ben Greear
2013-02-21 23:49 ` Adrian Chadd
2013-02-21 23:53 ` Ben Greear
2013-02-21 23:56 ` Adrian Chadd
2013-02-22 0:11 ` Ben Greear
2013-02-22 4:23 ` Sujith Manoharan
2013-02-21 1:36 ` Sujith Manoharan
2013-02-21 2:02 ` Ben Greear
2013-02-21 2:04 ` Sujith Manoharan
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=5125B39F.3010200@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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).