bf_next not NULL!
Adrian Chadd
adrian.chadd at gmail.com
Wed Aug 3 22:42:17 UTC 2016
ok. I'll go dig an ar9227 out of storage and set it up to see what's going on.
please do this:
sysctl dev.ath.0.hal.debug=0x18
then paste me the results from 'dmesg' over some period of time (eg
between good/bad/good times.)
Thanks,
-adrian
On 3 August 2016 at 15:36, Andrew Stevenson <andrew at ugh.net.au> wrote:
>
> On 02 Aug 2016, at 22:53, Adrian Chadd <adrian.chadd at gmail.com> wrote:
>
>> sysctl dev.ath.0.hal.force_full_reset=1
>> while true; do
>> sysctl dev.ath.0.force_bstuck=1
>> sleep 300
>> done
>>
>> .. see if that fixes things.
>
> Definitely not fixed. It does sometimes seem to be good immediately after the sysctl runs - but then at other times its back to its old tricks with lost packets and the sysctl doesn’t seem to bring it back - however it seems to have stopped the dropping of all the clients.
>
> Thanks,
>
> Andrew
More information about the freebsd-wireless
mailing list