All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Paul Stewart <pstew@google.com>
Subject: Re: [PATCH 1/2] ath9k: recover the chip from tx/rx stuck
Date: Wed, 01 Feb 2012 09:31:50 -0800	[thread overview]
Message-ID: <4F297706.3060404@candelatech.com> (raw)
In-Reply-To: <1328112335-19265-1-git-send-email-rmanohar@qca.qualcomm.com>

On 02/01/2012 08:05 AM, Rajkumar Manoharan wrote:
> In the following scenario, where the distance b/w STA and AP is ~10m
> or in a shield environment by placing an attenuator with reduced AP
> txpower, the station started reporting with beacon loss and got
> disconnected whenever the chariot endpoint was initiated with BiDi
> traffic. In such state, two different stuck cases were observed.
>
>    * rx clear is stuck at low for more than 100ms
>    * dcu chain and complete state is stuck.
>
> This patch detects the stuck state if the beacons are not received for
> more than 300ms. In the above matching conditions, trigger a chip
> reset to recover. This issue was originally reported in 3.0 kernel with
> AR9382 chip by having two stations associated with two different APs in
> the same channel and was attenuated/controlled by Azimuth ADEPT-n box.

Can't the AP be configured for larger beacon intervals?  Maybe have it
be some multiple of that instead of a fixed 300ms?

Thanks,
Ben

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


  parent reply	other threads:[~2012-02-01 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 16:05 [PATCH 1/2] ath9k: recover the chip from tx/rx stuck Rajkumar Manoharan
2012-02-01 16:05 ` [PATCH 2/2] ath9k_hw: improve ANI processing and rx desensitizing parameters Rajkumar Manoharan
2012-02-02 22:09   ` Adrian Chadd
2012-02-03  5:56     ` Rajkumar Manoharan
2012-02-04 10:28       ` Adrian Chadd
2012-02-06  7:10         ` Rajkumar Manoharan
2012-02-07 21:41           ` Adrian Chadd
2012-02-10  0:55             ` Adrian Chadd
2012-02-01 17:31 ` Ben Greear [this message]
2012-02-01 18:50   ` [PATCH 1/2] ath9k: recover the chip from tx/rx stuck Rajkumar Manoharan
2012-02-01 19:03     ` Ben Greear
2012-02-01 19:35 ` Ben Greear
2012-02-02  3:49   ` Rajkumar Manoharan
2012-02-02  3:08 ` Sujith Manoharan
2012-02-02  3:56   ` Rajkumar Manoharan
2012-02-02  4:09     ` Sujith Manoharan
2012-02-02  4:46       ` Rajkumar Manoharan
     [not found]       ` <CAJ-VmomK0cD5rYbSYOQ7xwJLADdbD=a4JVG1bcd4QdTpV+uN2Q@mail.gmail.com>
2012-02-03  6:04         ` Rajkumar Manoharan
2012-02-04 10:30           ` Adrian Chadd
2012-02-02  4:56 ` 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=4F297706.3060404@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=pstew@google.com \
    --cc=rmanohar@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.