Date: Fri, 29 Jul 2016 22:30:01 +0200 From: Andrew Stevenson <andrew@ugh.net.au> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Cc: Willem@offermans.rompen.nl, Adrian Chadd <adrian.chadd@gmail.com> Subject: Re: bf_next not NULL! Message-ID: <762054A0-B628-4CD8-9F59-6B52CEB78481@ugh.net.au> In-Reply-To: <A0ED3F72-21EF-4B97-BF4B-AA0AEA336958@ugh.net.au> References: <2DEF8DBE-1444-435C-B48C-FEAB71CA60E5@ugh.net.au> <20160716105843.GA5832@vpn.offrom.nl> <CAJ-VmomwtRwk8aNcCn3pKzbLspPHN0UKPC4J%2BdS0ebOvHom73g@mail.gmail.com> <A0ED3F72-21EF-4B97-BF4B-AA0AEA336958@ugh.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Well after a week of running 11 (BETA1 r303134) I think sadly its worse = than 10. No more bf_next errors. Still lots of "ath0: stuck beacon; = resetting (bmiss count 4)=94. The main thing though is the the clients = drop of the network and can=92t reattach. Sometimes restarting hostapd is all that is needed, though occasionally = I have to =93restart" the interface (/etc/rc.d/netif restart wlan0). Happens usually once or twice a day. Is there anything I can do to help = debug? I tried to attach to hostapd with gdb last time but gdb had an = internal error and killed the process. Thanks, Andrew=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?762054A0-B628-4CD8-9F59-6B52CEB78481>