Date: Sat, 10 Mar 2012 17:58:22 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Vincent Hoffman <vince@unsane.co.uk> Cc: freebsd-wireless@freebsd.org Subject: Re: ath0 timeout was "Re: (more) bugs fixed in -HEAD, AP mode is now mostly (again) stable!" Message-ID: <CAJ-Vmo=HpBYR6ci-dyJWJK9_OkUVC2J_bj7YknNvKwR8to0q8w@mail.gmail.com> In-Reply-To: <4F5C0302.8090403@unsane.co.uk> References: <CAJ-VmokYNFnNrWxk=Sg%2BhRuOhkGj5%2Bi7TGB3ni_YBT9=pjs8AQ@mail.gmail.com> <4F59DD98.8080905@unsane.co.uk> <CAJ-Vmokurdn-FGfdFuuN84a9==fdoYjAPBOd4icT-eBJ2BuGpg@mail.gmail.com> <4F5AA149.8000904@unsane.co.uk> <CAJ-VmommaSh3Y=huxpfHRbVb0j3HGXTfDNi_OHJ5Tz8_AHqCSQ@mail.gmail.com> <4F5BDF3C.8070605@unsane.co.uk> <CAJ-VmomFfAXncDp48LYQvRTL5-HG4GpnDkkAy71ReTAFRyK41A@mail.gmail.com> <4F5C0302.8090403@unsane.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hiya, Next time it happens, do the sysctl before the scan. The sysctl will tell me how deep each hardware TX queue is. I should likely add some further debugging to tell me how deep the per-TID software queues are; that'd be helpful here. What you're seeing there is something weird which is causing the TX frames to be queued in software/hardware and not be transmitted, to the point of buffer exhaustion. See "total TX buffers: 0" ? That means the frames can't go out for some reason. There's nothing in the hardware queue, so that also has me slightly concerned. I wonder if this is a problem with aggregation and buffer exhaustion. Hm, can you do "wlandebug +11n" and see if it's trying to exchange ADDBA frames (and failing) ? There's a known bug where Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=HpBYR6ci-dyJWJK9_OkUVC2J_bj7YknNvKwR8to0q8w>