From nobody Mon Sep 6 05:50:21 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EE090179CF09 for ; Mon, 6 Sep 2021 05:50:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H2yDK5yH2z3qQH for ; Mon, 6 Sep 2021 05:50:25 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id N0YMmrmvGps7PN7WTmnXzP; Mon, 06 Sep 2021 05:50:25 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id N7WRmKCGHU9pxN7WSmJSJw; Mon, 06 Sep 2021 05:50:25 +0000 X-Authority-Analysis: v=2.4 cv=Bbi7bph2 c=1 sm=1 tr=0 ts=6135ac21 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=QCccru2TAAAA:8 a=JAf30KXuAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=iYvezse-Q5tlZEVPOWAA:9 a=CjuIK1q_8ugA:10 a=rCjsK_HQOcgUb9vb-KUg:22 a=GEL62FyrTCmHtEug2d3R:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 950CCB8; Sun, 5 Sep 2021 22:50:23 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 1865oLlJ013110; Sun, 5 Sep 2021 22:50:23 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109060550.1865oLlJ013110@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Oleg V. Nauman" cc: current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> Comments: In-reply-to "Oleg V. Nauman" message dated "Sun, 05 Sep 2021 19:43:52 +0300." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Sep 2021 22:50:21 -0700 X-CMAE-Envelope: MS4xfNDU3LEq8fbuiBVvfbjSfhxV7BfsHTiOa8rPNuDh8x1ozUCmhz9tSNwAOxka86UwQT9IS7R1u8uSHET+Jvr8d7LsWC6TB/ziEM2hKcDqVMASnV8D8ofL b/tjPG6G5zHZ/SpvWw1uS/3OFtK+hk79P+Lwd9F/CP+/3YWuza7TaZsBvd5TRc7lXaJxX54qJ8wIu4L0OkpnrhkfM3FQ+AqXka2fTzC+49uX9PUBagc5Pj6N X-Rspamd-Queue-Id: 4H2yDK5yH2z3qQH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > Sorry I hadn't noticed this yesterday (so I could have repported it > > then), but after updating the "head" slice of my laptopp from: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > to: > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > amd64 1400032 1400032 > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does not: > > the WLAN LED doesn't light up. > > I am also experiencing issues with wlan after my current update to > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > demonstrating the same behavior - wlan can not associate. > You can mitigate it by using security/wpa_supplicant from ports as replacemen > t > of wpa_supplicant in base. > > ..... > > > > I note that exactly the same hardware works OK in stable/12 and stable/13. > > > > Peace, > > david > Can you grep wpa_supplicant in /var/log/messages? This will give us a clue. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. > >