From owner-freebsd-net@freebsd.org Wed Aug 24 21:02:50 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 503AEBC5D26 for ; Wed, 24 Aug 2016 21:02:50 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 35FE01948 for ; Wed, 24 Aug 2016 21:02:50 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 31B2BBC5D25; Wed, 24 Aug 2016 21:02:50 +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 315DABC5D24 for ; Wed, 24 Aug 2016 21:02:50 +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 1C87B1947; Wed, 24 Aug 2016 21:02:50 +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 B388116FD; Wed, 24 Aug 2016 21:02:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 24 Aug 2016 21:02:47 +0000 From: Glen Barber To: Adrian Chadd Cc: Kevin Oberman , FreeBSD Net , Andriy Voskoboinyk , =?iso-8859-1?Q?Vin=EDcius?= Zavam Subject: Re: iwn(4) association issues in 11-Stable (and maybe RC) Message-ID: <20160824210247.GP19112@FreeBSD.org> References: <20160824190352.GK19112@FreeBSD.org> <20160824194557.GM19112@FreeBSD.org> <20160824201921.GN19112@FreeBSD.org> <20160824202338.GO19112@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fjEAjMKpll6GDq3U" Content-Disposition: inline In-Reply-To: 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 21:02:50 -0000 --fjEAjMKpll6GDq3U Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 24, 2016 at 01:51:47PM -0700, Adrian Chadd wrote: > On 24 August 2016 at 13:23, Glen Barber wrote: > > 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: > >> > > >> > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > >> > > > > >> > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber = wrote: > >> > > > > >> > > > > 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= iwn. > >> > > > > > 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 run= ning > >> > > > > releng/11.0, the matching commit is r304719. > >> > > > > > >> > > > > >> > > > Since my initial post I have updated to r304734 (running 11-STAB= LE). I > >> > > did > >> > > > that before rebuilding my kernel with the DEBUG options as it wa= s already > >> > > > 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. > >> > > > >> > > >> > 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 diff= erent. > >> > > >> > I will try to test some more later, but I have to go out for a coup= le of > >> > hours right now. > >> > > >> > >> 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. > >> > > > > 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 > > >=20 > Would /someone/ pretty please fix this "run wpa_supplicant multiple > times at interface start" problem? >=20 > I'm sure it's screwing things up in a bad way, and trying to grovel > around and fix the way we do rc scripts is not my favourite thing in > the world. >=20 This does not interfere in my case, it was a configuration issue. However, I was never able to effectively (as in, reliably) reproduce wpa_supplicant starting more than once. When it *did*, everything still worked as expected. Glen --fjEAjMKpll6GDq3U Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXvgt3AAoJEAMUWKVHj+KT1yQP/2IAOpx/8Pn37xX/4rOTViDx 5KZr6OR3F6EUytZcoHr1fq86RPyqIVjk+/KH+KrFaFMRSrwxyK2AVR21RHw70+By jW5HSmeEnah4LZ74SgwEHKb2HvcIkwkDOifwstwZe5cdsXHE9ZV4jiPA2WHUVXcn syoIKd2uP28Sh3tNMIwXYs8Ut8ZdlaztDpMcp0BwoY2dOci6iA2WlDX5pcMRFUZ9 yQu/ZETkaEJ7y2zOlkcUqbBckcQhOMAvzPpn+O9j+skNVA1Ty4zSAbNN+eGH6/tW QfrcImp2/RAJ1RHes2fkfvH/UZYZN41cb+45hLjMWROMB46xq6b5XQodHZH5CyZq 1ReQd1+6GIxbaGYetoY/SesXm8zkvphVBSMNWB2hapJaaIosKRlxZmVsiGSLNW6W FE8MCz60gTVLw66US8xPacbbVswSUuOTPi/b78nb1/4YxwVIBmB+HvLQ2tD/W0/L JbRdaA5a7NHb+r4cGkM3F+gSnTz6kKC7pHRxB+CkQBIdDSjfzHcyrOGBW2g2wLE5 FKzhSGA6dwC3jNaqEoM9NFbv1wEhHsmJe6wmpAXK8tWES1908A0MCa1EHAAoKSzx qaKcRgopx0hGA8YYJvKZ4hkum2I4f7f/BV9qDwBv4NFwKkLqWYlsRAeB6FsQebJs VO9X1yAnkP00myzxs6/M =w3wA -----END PGP SIGNATURE----- --fjEAjMKpll6GDq3U--