Date: Tue, 3 Jan 2012 23:25:37 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Joel Dahl <joel@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working Message-ID: <CAJ-Vmo=_3pn9-jnq6wTsoCnGhFj5meH2UpdJixdAW7_r5-OtwA@mail.gmail.com> In-Reply-To: <201201040720.q047K68h092526@freefall.freebsd.org> References: <201201040720.q047K68h092526@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=_3pn9-jnq6wTsoCnGhFj5meH2UpdJixdAW7_r5-OtwA>