Hi Juergen,
I think it is quite important highlight that even if there are stuck
beacons reported, the AP is still functional although the client may
experienced reassociation intermittently. When I used trunk branch, the
AP is not recoverable and require a reboot.
I see from your can that the stuck beacon appears 6 times within 10
seconds. If it is recoverable, you should wait to see how often it
would occur again.
Regards,
Punky
Juergen Adolph wrote:
----- "Kim-man 'Punky' TSE" <[email protected]> schrieb:
Hi Juergen,
Hi Punky,
I encountered one stuck beacon after 1 day of running.
I found 6 errors in 12h:
is this long enough or should I longer test?
[ 301.470651] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
[ 303.282184] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
[ 304.980084] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
[ 306.790151] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
[ 308.692854] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
[ 310.493159] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss
count: 11)
The download
didn't break and the link is recoverable, so I continue to run it until tonight.
yes, here also so.
Regards,
Jürgen
--
Regards,
Punky
Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
- Network Engineering, Development Platform and Consultation
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
