From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Sujith Manoharan <sujith@msujith.org>,
"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: Thu, 21 Feb 2013 15:53:12 -0800 [thread overview]
Message-ID: <5126B368.9010209@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmo=FC=jdJ9VyZtZy_nbdGhCCfJ9dhS3993fwneGhFjoBJg@mail.gmail.com>
On 02/21/2013 03:49 PM, Adrian Chadd wrote:
> .. so the current code correctly soft fails all of those frames and
> puts them back onto the relevant software queues, right?
I might have been mistaken. Further testing makes me think the
pending-frames are properly dealt with. I see them show back up
in the tx-complete logic about 30 second after the first chip reset logic hits.
That seems quite long to me, but then again, it appears that without a chip
reset, they never show back up in the tx-complete logic at all (and thus
the hang).
I'm testing now with just the pending-frames lockup check with a plain
chip reset as work-around (and no fiddling with pending-frames counter).
Thanks,
Ben
>
>
> Adrian
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-02-21 23:53 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
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 [this message]
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=5126B368.9010209@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--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).