Date: Tue, 26 Mar 2013 17:34:31 -0500 From: Joshua Isom <jrisom@gmail.com> To: freebsd-wireless@freebsd.org Subject: Re: [wip] ar9300 hostap support Message-ID: <51522277.6040107@gmail.com> In-Reply-To: <CAJ-Vmon7-g6DOdCsF05i4twfL_UXjBYUneGYts6dZbiFgH3zww@mail.gmail.com> References: <CAJ-Vmo=4QRuYeG8LmEfntTB2W5OyfsnVDCz5cJ__zWYbXkme3w@mail.gmail.com> <CAJ-VmomtQFjiGZRR0ME3HvGaJjHfXq%2BRT6a699UUDqGnJM1zjw@mail.gmail.com> <CAJ-Vmon7-g6DOdCsF05i4twfL_UXjBYUneGYts6dZbiFgH3zww@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I know it'll sound bad, but I've had two hours of uptime without a panic and while keeping network. It seems you'ved fixed the network connectivity problem, which could have been because of a weak signal, and the panics. My dmesg is getting occasional "ath0: ath_edma_recv_proc_queue: handled npkts 0" but not nearly as often as before. On 3/26/2013 3:10 PM, Adrian Chadd wrote: > .. and it's all now in -HEAD. > > Please update to -HEAD before you test out the AR9380 support. > > Joshua - I've also put in a work around to stop things crashing on an > empty tx queue. It'll just log a warning. > > I'm going to add some further debugging code to ensure that frames > going into a TXQ actually _have_ the right queue ID set in the > descriptor. It's quite possible that I've screwed this up somewhere. > > Thanks, > > > Adrian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51522277.6040107>