Re: AR9330 hornet board stops beaconing after a few days (0xdeadbeef)

[Sven Eckelmann <sven@narfation.org>]

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

On Monday 03 September 2012 19:23:26 Mohammed Shafi wrote:
> > # dmesg
> > [...]
> > [900132.160000] ath: phy0: NF calibrated [ext] [chain 0] is -104
> > [900162.160000] ath: phy0: NF calibrated [ctl] [chain 0] is -104
> > [900162.160000] ath: phy0: NF calibrated [ext] [chain 0] is -104
> > [900192.160000] ath: phy0: NF calibrated [ctl] [chain 0] is -104
> > [900192.160000] ath: phy0: NF calibrated [ext] [chain 0] is -104
> > [900197.470000] ath: phy0: missed 1 consecutive beacons
> > [900197.560000] ath: phy0: resume beacon xmit after 1 misses
> > [900222.160000] ath: phy0: NF calibrated [ctl] [chain 0] is -104
> > [900222.160000] ath: phy0: NF calibrated [ext] [chain 0] is -104
> > [900252.160000] ath: phy0: NF calibrated [ctl] [chain 0] is -104
> > [900252.160000] ath: phy0: NF calibrated [ext] [chain 0] is -104
> > [900275.910000] ath: phy0: missed 1 consecutive beacons
> 
> 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.

The test environment is not really "congested". It is not in a city and you 
don't have many access points in range. Only 2/3 clients are using these two 
test access points. I don't know whether there are other things using the 
channel range also used by the access points.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]