kern/163318: [ath] ath(4) stops working
Adrian Chadd
adrian at freebsd.org
Wed Jan 4 07:25:38 UTC 2012
Hi,
Thanks for that. Hm. The problem is still not clear. There's no state
transition, so I guess it's going into scan mode and out of scan mode
again.
How about doing this:
wlandebug +state +power
sysctl dev.ath.X.debug=0x00040000
That enables the _driver_ state checking. That should log when
ath_scan_start and ath_scan_end are called.
This is definitely a tricky one..
Adrian
More information about the freebsd-wireless
mailing list