Re: bf_next not NULL!

2016-08-12 Thread Andrew Stevenson
On 06 Aug 2016, at 10:33, Adrian Chadd wrote: > 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. It has been running for 5 days or so now with force_full_reset but without the forcebstuck loop in case i

Re: bf_next not NULL!

2016-08-12 Thread Adrian Chadd
hi, So I think it's two things: * not doing the "tear down TX/RX DMA right" bugs that I've never really sat down and fixed, and * yeah, this is drifting out of NF calibration and going deaf - that's where the NF calibration doesn't finish in the window, which normally happens because something is

Please commit this patch: Add an option for wpa_supplicant to create the control interface socket

2016-08-12 Thread Yuri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211213 Thanks, Yuri ___ 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"