Re: bf_next not NULL!

2016-08-05 Thread Andrew Stevenson
On 04 Aug 2016, at 09:50, Adrian Chadd 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

Re: bf_next not NULL!

2016-08-05 Thread Adrian Chadd
thanks! -a On 5 August 2016 at 14:32, Andrew Stevenson wrote: > > On 05 Aug 2016, at 21:22, Andrew Stevenson wrote: > >> >> The same messages are repeated in dmesg so here is a sample: >> > > But of course I forgot to sysctl dev.ath.0.hal.debug=0x18 after restarting > with the new kernel… >

Re: bf_next not NULL!

2016-08-05 Thread Andrew Stevenson
On 05 Aug 2016, at 21:22, Andrew Stevenson wrote: > > The same messages are repeated in dmesg so here is a sample: > But of course I forgot to sysctl dev.ath.0.hal.debug=0x18 after restarting with the new kernel… It was currently broken but sysctl dev.ath.0.hal.force_full_reset=1 brought i

Re: svn commit: r300383 - head/sys/net80211

2016-08-05 Thread Adrian Chadd
Also, the scan code now also seems to alternate between g and n channels on 2ghz; and it never seems to update the chanlist if it's interrupted. So yeah, hm. Avos, any ideas? -adrian On 5 August 2016 at 16:42, Adrian Chadd wrote: > Hi, > > Just a reminder and notice to others - yeah, I've fo