Re: bf_next not NULL!

2016-08-06 Thread Adrian Chadd
hi, ok. Try running with 'sysctl dev.ath.0.hal.force_full_reset=1' enabled. It looks like the DMA engine reset isn't fully resetting things. Good, this i can likely reproduce. -adrian On 6 August 2016 at 00:48, Andrew Stevenson wrote: > OK a bit less incompetently this time. This is dmesg wi

Re: bf_next not NULL!

2016-08-06 Thread Andrew Stevenson
OK a bit less incompetently this time. This is dmesg with duplicate lines suppressed. The first field is the number of times the line was duplicated. 164 ar5416DoCalibration: IQ Calibration, state 2, calValid 0x4 0 ar5416GetMibCycleCounts: cycle counter wrap. ExtBusy = 0 32 ar5416D