From owner-freebsd-net@freebsd.org Wed Aug 24 20:23:40 2016 Return-Path: Delivered-To: freebsd-net@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 2973CBC515C for ; Wed, 24 Aug 2016 20:23:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0EE9F11E2 for ; Wed, 24 Aug 2016 20:23:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0DB3CBC515B; Wed, 24 Aug 2016 20:23:40 +0000 (UTC) Delivered-To: net@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 0D55EBC515A for ; Wed, 24 Aug 2016 20:23:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E556E11E1; Wed, 24 Aug 2016 20:23:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 881621E36; Wed, 24 Aug 2016 20:23:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 24 Aug 2016 20:23:38 +0000 From: Glen Barber To: Kevin Oberman Cc: FreeBSD Net , Adrian Chadd , Andriy Voskoboinyk , =?iso-8859-1?Q?Vin=EDcius?= Zavam Subject: Re: iwn(4) association issues in 11-Stable (and maybe RC) Message-ID: <20160824202338.GO19112@FreeBSD.org> References: <20160824190352.GK19112@FreeBSD.org> <20160824194557.GM19112@FreeBSD.org> <20160824201921.GN19112@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B3NBd8mrXZtPJEYR" Content-Disposition: inline In-Reply-To: <20160824201921.GN19112@FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2016 20:23:40 -0000 --B3NBd8mrXZtPJEYR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 24, 2016 at 08:19:21PM +0000, Glen Barber wrote: > On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: > > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: > >=20 > > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > > > > > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wro= te: > > > > > > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > > > > Not working right. I do see 802.11 messages but nothing from iw= n. > > > > > > Rebuilt with: > > > > > > options IEEE80211_DEBUG > > > > > > options IWN_DEBUG > > > > > > > > > > > > [...] > > > > > > > > > > > > Any idea what is going on? > > > > > > > > > > Your original email mentions 11.0-BETA4. Are you still running > > > > > stable/11? If so, could you please update to r304715? If running > > > > > releng/11.0, the matching commit is r304719. > > > > > > > > > > > > > Since my initial post I have updated to r304734 (running 11-STABLE)= =2E I > > > did > > > > that before rebuilding my kernel with the DEBUG options as it was a= lready > > > > three weeks old. So this does not seem to have fixed the issue. > > > > > > Dumb question, but with reason. > > > > > > Does ifconfig(8) actually show wlan0 'UP'? > > > > > > I'm asking this because I'm seeing something strange locally on one > > > machine. > > > > >=20 > > I have been unable to catch it, so I don't know. I know the UP/DOWN > > sequences in the first log showed many per second and all in the same > > second. In this case it was UP for 13 seconds, so something was differe= nt. > >=20 > > I will try to test some more later, but I have to go out for a couple = of > > hours right now. > >=20 >=20 > Ok, thanks. This is different than the issue I'm seeing, part of which > turned out to be a config issue on one of two machines, but completely > odd on the other. >=20 Sigh. On my side, it was a config issue on both machines. Sorry for the noise, but I'm sure you understand my concern and panic this late in 11.0. Glen --B3NBd8mrXZtPJEYR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXvgJEAAoJEAMUWKVHj+KTATIQAKFMFz8d26EtKo2wrcjOb2mp 6DZYUZBsaE98n5z0LoH4GssK6rxUGpj3vm5Zi3sEGkxnfnRDNOpLX50dPBGBQq+o YTYNnFzMk5Ox4dnhNO/R4oW1T/FQ7dreWsF+QWc+CJzoY7MKLahr5ZcBtZaZttFX oSWIimd9pSMUyL2zwwDPDVolr9ewnPS8XQauoGojOlcmb3I9C37Zum7iGYzws3Lj RyaJS8rYKHBnwSdEtIMD+N1ul3HDCHMRsmIk7vaLtbiRrsT4lvctj8LcGSXwli0Z aihrP/WEzPUDcmdr0vUdq6Wz0mWgiyE+fbMltIylf0SucraW0pwLBGh7C4ZR4tCZ CpYwml7PIVOiOHEe5ACIYCPutPPkSpxZBj2juRPyDShUCXAxci3bUB8hAky0BFsR mc0ngyhXyFZsvmcvXnFvxttRCTkHQGH50u/qFIwkTFfmviNXyPGQQaGIyZijHDUI bVoDBqHZZOs0LOy6cxjcYAcSkfjXdxN9Cn55lep8a+0nbh8iobWn0yDr810dH9Gq fFj+RVo/Vcx3xtvARVVomGqOh9OOOSDZgNmsbnaCF8vA6/bJk19qHiX1GWFX6ggG LHvseFp2bwCY5q6K7+MTVhAJ2ieMZlGrKG6jer4bjfyL409RWaxQdzfUb0JZ9ZoP Yyj1ZbjjcI0lJd8AWotX =+7ZD -----END PGP SIGNATURE----- --B3NBd8mrXZtPJEYR--