From owner-freebsd-wireless@freebsd.org Thu Aug 4 07:48:16 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9C07BAE40D for ; Thu, 4 Aug 2016 07:48:16 +0000 (UTC) (envelope-from andrew@ugh.net.au) Received: from kaija.ugh.net.au (kaija.ugh.net.au [IPv6:2a00:1a48:7803:107:65bc:4bde:ff08:1f7f]) by mx1.freebsd.org (Postfix) with ESMTP id 674CD1A51 for ; Thu, 4 Aug 2016 07:48:15 +0000 (UTC) (envelope-from andrew@ugh.net.au) Received: from [IPv6:2a00:c1a0:4886:7a00:5cf9:629b:c8b5:c149] (unknown [IPv6:2a00:c1a0:4886:7a00:5cf9:629b:c8b5:c149]) by kaija.ugh.net.au (Postfix) with ESMTPSA id 35882ADAB; Thu, 4 Aug 2016 07:48:13 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: bf_next not NULL! From: Andrew Stevenson In-Reply-To: Date: Thu, 4 Aug 2016 09:48:11 +0200 Cc: "freebsd-wireless@freebsd.org" , Willem@offermans.rompen.nl Content-Transfer-Encoding: quoted-printable Message-Id: <2E7BBB3B-2398-413B-BA8E-18CFB16AE4E1@ugh.net.au> References: <2DEF8DBE-1444-435C-B48C-FEAB71CA60E5@ugh.net.au> <20160716105843.GA5832@vpn.offrom.nl> <762054A0-B628-4CD8-9F59-6B52CEB78481@ugh.net.au> <09DD4206-6D68-4B03-A3F9-01512C2F866B@ugh.net.au> To: Adrian Chadd X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 07:48:16 -0000 On 04 Aug 2016, at 00:41, Adrian Chadd wrote: > ok. I'll go dig an ar9227 out of storage and set it up to see what's = going on. >=20 > please do this: >=20 > sysctl dev.ath.0.hal.debug=3D0x18 >=20 > then paste me the results from 'dmesg' over some period of time (eg > between good/bad/good times.) OK I enabled this last night and this morning I find that the DHCP = server has stopped serving anything on the WIFI interface. Thats a new = one. It might be a random bugs in the ISC DHCP server but I haven=92t = noticed it before and I have seen that rtadvd sometimes doesn=92t cope = with broken interfaces and requires a restart after they are fixed so = maybe dhcpd is similar. That would mean the sysctl loop had brought = things back by itself. DHCP didn=92t log anything and seemed to be = working over wired ethernet. I restarted DHCP and everything seems normal. Pings are a bit variable = but no IP layer loss (e.g. best 1.6ms, avg 6.9ms, worst 15.3 ms for a = ping from a client to the base station). Nothing logged yet from ath0 other than "ath0: stuck beacon; resetting = (bmiss count 0)=94 (note 0 this time) logged approx every 4 minutes. = Every 5th (approx) has a bmiss of 4). "ath0: device timeout=94 appears = about once every 2 hours. I will keep checking and let you know. Thanks, Andrew=