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

[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 found that this
> actually stops scan from working well and reliably.
>
> Notably, I've found that we get a scan completion notification and
> then we can't restart a subsequent scan for some reason.
>
> I may have to revert this and put in something slightly more explicit
> - eg, we put on an explicit full scan timeout and we explicitly
> complete the scan if we don't finish it in time.
>
>
> -adrian
>
>
> On 21 May 2016 at 16:24, Andriy Voskoboinyk  wrote:
>> Tested with wpi(4) and urtwn(4) in STA mode.
>>
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: bf_next not NULL!

[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 it 
back to life.

I will wait for it to die again so I can get messages before and after with 
debugging actually switched on…

Andrew
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"