Date: Fri, 11 Jan 2013 16:00:36 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Andrew <andrew@ugh.net.au> Cc: freebsd-wireless@freebsd.org Subject: Re: Debugging Stalls with ath(4) Message-ID: <CAJ-Vmo=oLk2wOtnyr8urOek8evBQ99GdkNyhO%2BRwLK1UdBKQSw@mail.gmail.com> In-Reply-To: <BC00ED06-760E-44AB-AB35-E2011765EA5C@ugh.net.au> References: <BC00ED06-760E-44AB-AB35-E2011765EA5C@ugh.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
.. ok, so reading about this a bit more. Going in and out of power save state could be it. Having it wait for a second is possible when you're in power save, because it's quite possible that the device is _in_ power save state for that long. Enable power state debugging in net80211 and see what's happening. You'll see it come in and out of power save, as well as it queuing up frames (and if the node power save queue overflows.) It'll also log whether it receives ps-poll frames (which I know handling of is broken in various ways in -HEAD and will be for a few more weeks) or whether it's just coming in and out of power save frames. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=oLk2wOtnyr8urOek8evBQ99GdkNyhO%2BRwLK1UdBKQSw>