From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
openwrt-devel@lists.openwrt.org,
Marek Lindner <lindner_marek@yahoo.de>,
sven@narfation.org, Gabor Juhos <juhosg@openwrt.org>,
Adrian Chadd <adrian.chadd@gmail.com>
Subject: Re: AR9330 hornet board stops beaconing after a few days (0xdeadbeef)
Date: Tue, 4 Sep 2012 19:12:15 +0200 [thread overview]
Message-ID: <20120904171215.GA5953@pandem0nium> (raw)
In-Reply-To: <CAD2nsn2wGCsYV2NW9VSVnvmQhnEk0EXW1vn6eaTYg_4-1w8ecQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Shafi,
On Mon, Sep 03, 2012 at 07:23:26PM +0530, Mohammed Shafi wrote:
> seems we are getting beacon stuck, though its not sufficient for triggering
> chip reset (or) atleast start noise floor calibration. Is this is in a congested
> environment ? we can dump cycle counters . I think we need to have a
> WAR of chip reset if the cycle counters (busy is too high) inspite the MAC hang
> signature . let me try too to figure out that WAR is already available (or)
> we got to enable it.
I'm living at a small village, and one or two neighbors may have access points too,
but that's it - this should be far from beeing busy. We mostly use these APs for
surfing with smart phones, this is also far from congesting them. ;)
TBH I don't really understand what you are talking about regarding WAR, etc, can
you please explain? What can we do to analyse the problem better?
Thanks,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-04 17:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 16:53 AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Simon Wunderlich
2012-08-19 22:04 ` Simon Wunderlich
2012-08-22 5:20 ` Mohammed Shafi
2012-08-22 18:57 ` Adrian Chadd
2012-08-23 9:28 ` Simon Wunderlich
2012-08-23 17:10 ` Gabor Juhos
2012-08-23 19:26 ` Adrian Chadd
2012-08-23 14:59 ` Mohammed Shafi
2012-08-23 15:19 ` Sven Eckelmann
2012-08-23 15:27 ` Sven Eckelmann
2012-09-02 20:01 ` Simon Wunderlich
2012-09-03 13:53 ` Mohammed Shafi
2012-09-03 14:34 ` Sven Eckelmann
2012-09-04 17:12 ` Simon Wunderlich [this message]
2012-09-05 5:12 ` Mohammed Shafi
2012-09-05 14:08 ` Adrian Chadd
2012-09-05 14:20 ` Sven Eckelmann
2012-09-13 16:51 ` Simon Wunderlich
2012-09-13 16:59 ` Adrian Chadd
2012-09-13 17:55 ` [OpenWrt-Devel] " Felix Fietkau
2012-09-14 9:47 ` [RFC] ath9k: Work around complete stuck of hw Sven Eckelmann
2012-09-14 11:33 ` Felix Fietkau
2012-09-23 10:04 ` Sven Eckelmann
2013-11-20 20:57 ` [OpenWrt-Devel] AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Bastian Bittorf
2013-11-20 21:00 ` Sven Eckelmann
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=20120904171215.GA5953@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=adrian.chadd@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=juhosg@openwrt.org \
--cc=lindner_marek@yahoo.de \
--cc=linux-wireless@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=shafi.wireless@gmail.com \
--cc=sven@narfation.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).