bf_next not NULL!

[Andrew Stevenson]

On 04 Aug 2016, at 09:50, Adrian Chadd <adrian.chadd at gmail.com> wrote:

> Hi,
> 
> Recompile with ATH_DEBUG, AH_DEBUG, ATH_DIAGAPI

I don’t know if the debug code actually changes something or its just Murphy’s law but everything has, so far, been working since. Maybe this email will be enough to break it…and there we go.

10 packets transmitted, 6 packets received, 40.0% packet loss
round-trip min/avg/max/stddev = 37.029/135.772/222.928/66.821 ms

The same messages are repeated in dmesg so here is a sample:

ath0: stuck beacon; resetting (bmiss count 4)
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
ath0: stuck beacon; resetting (bmiss count 4)
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
ath0: stuck beacon; resetting (bmiss count 4)
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
ath0: stuck beacon; resetting (bmiss count 4)
ar5416StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)
ath0: stuck beacon; resetting (bmiss count 4)

Thanks,

Andrew