On an AR9342-based AP, we see non-zero counts for
RESET_TYPE_BB_WATCHDOG and RESET_TYPE_BEACON_STUCK when trying to do
large uplink transfers from ~60 clients with some of them 30-40 ft
away.
All the other reset types have a count of zero.
These resets cause all the clients to disconnect.
Any ideas on how to avoid these resets and the subsequent disconnections?
Thanks,
- Harshal
On Wed, Jul 10, 2013 at 11:43 AM, Harshal Chhaya <[email protected]> wrote:
> On an AR9342-based AP, we see non-zero counts for
> RESET_TYPE_BB_WATCHDOG and RESET_TYPE_BEACON_STUCK when trying to do
> large uplink transfers from ~60 clients with some of them 30-40 ft
> away.
>
> All the other reset types have a count of zero.
>
> These resets cause all the clients to disconnect.
>
> Any ideas on how to avoid these resets and the subsequent disconnections?
I forgot to mention that there were three "Failed to stop TX DMA"
messages on the debug port which seem to map to the
RESET_TYPE_BB_WATCHDOG events.
Regards,
- Harshal