Date: Tue, 23 Apr 2013 13:01:55 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Petko Bordjukov <bordjukov@gmail.com> Cc: lev@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic Message-ID: <CAJ-VmokFWWBiF3z2suEKaYz4%2BUvEyZddZ1=hMExCx1YEpQJDBA@mail.gmail.com> In-Reply-To: <CAAgmp6uCGEEDh6cS8qWsf4x4M7V3JQhvhhEiGsiMgGmqxmiPtg@mail.gmail.com> References: <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAAgmp6uCGEEDh6cS8qWsf4x4M7V3JQhvhhEiGsiMgGmqxmiPtg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 April 2013 12:57, Petko Bordjukov <bordjukov@gmail.com> wrote: > Falling back to a ht:20- channel did considerably lower the number of stuck > beacon messages on my AR9220. It still periodically hangs though (is this > why ``baseband hangs?'' is listed in the wiki?). Well, partially. I'm seeing stuck beacons in my testing with my modified AP power save code running, so it's also possible that there's something odd going on with the hardware programming that's locking things up. Luckily I can easy reproduce it, so I'm going to dig into it a bit more and see what I find. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokFWWBiF3z2suEKaYz4%2BUvEyZddZ1=hMExCx1YEpQJDBA>