linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 18:02:08 -0800	[thread overview]
Message-ID: <51258020.1060906@candelatech.com> (raw)
In-Reply-To: <20773.31273.604966.176099@gargle.gargle.HOWL>

On 02/20/2013 05:36 PM, Sujith Manoharan wrote:
> Ben Greear wrote:
>>   From the AP lockup case, dmesg is full of stuff like this:
>>
>> [ 1819.538577] vap1: delba from 00:3f:d1:e4:32:51 (initiator) tid 0 reason code 37
>> [ 1819.640602] vap1: Rx A-MPDU request on 00:6f:f9:68:b1:31 tid 0 result 0
>> [ 1819.690601] vap1: Rx A-MPDU request on 00:01:ab:ba:da:d3 tid 0 result 0
>> [ 1819.778013] vap1: RX session timer expired on 00:59:82:d1:d8:8c tid 0
>> [ 1819.778040] vap1: Rx BA session stop requested for 00:59:82:d1:d8:8c tid 0 recipient reason: 39
>> [ 1819.814600] vap1: delba from 00:59:82:d1:d8:8c (initiator) tid 0 reason code 37
>> [ 1819.820010] vap1: RX session timer expired on 00:eb:69:fc:4b:db tid 0
>> [ 1819.820034] vap1: Rx BA session stop requested for 00:eb:69:fc:4b:db tid 0 recipient reason: 39
>> [ 1819.863631] vap1: delba from 00:eb:69:fc:4b:db (initiator) tid 0 reason code 37
>> [ 1819.978012] vap1: RX session timer expired on 00:39:9a:d1:0e:10 tid 0
>> [ 1819.978035] vap1: Rx BA session stop requested for 00:39:9a:d1:0e:10 tid 0 recipient reason: 39
>> [ 1820.014580] vap1: delba from 00:39:9a:d1:0e:10 (initiator) tid 0 reason code 37
>
> The ADDBA sessions are being torn down aggressively.
>
>> TXERR Filtered:            224          0         0         0
>
> The recipient has gone out of range and frames are being filtered here.
> As a quick test, can you disable PowerSave on the client and check if the issue
> still happens ?

Powersave is always disabled in our tests...can't use it with multiple VIFS
as far as I know...

System doesn't recover if we drop the attenuation back to optimal levels, btw.

Ben

>
> Sujith
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2013-02-21  2:02 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
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 [this message]
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=51258020.1060906@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).