From owner-freebsd-current@freebsd.org Sun Jan 17 15:18:13 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD0884EC904 for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DJdpY427Gz3LFW for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: by mailman.nyi.freebsd.org (Postfix) id 8A5064EC903; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8A1934EC902 for ; Sun, 17 Jan 2021 15:18:13 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (noc.quadranet.com [66.63.164.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "sigill.theweb.org.ua", Issuer "sigill.theweb.org.ua" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJdpX5qJ9z3L2G for ; Sun, 17 Jan 2021 15:18:12 +0000 (UTC) (envelope-from oleg@theweb.org.ua) Received: from sigill.theweb.org.ua (localhost [127.0.0.1]) by sigill.theweb.org.ua (8.16.1/8.16.1) with ESMTPS id 10HFI21m043416 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Sun, 17 Jan 2021 17:18:02 +0200 (EET) (envelope-from oleg@theweb.org.ua) Received: (from oleg@localhost) by sigill.theweb.org.ua (8.16.1/8.16.1/Submit) id 10HFI1Rt043413 for current@freebsd.org; Sun, 17 Jan 2021 17:18:01 +0200 (EET) (envelope-from oleg@theweb.org.ua) X-Authentication-Warning: sigill.theweb.org.ua: oleg set sender to oleg@theweb.org.ua using -f From: "Oleg V. Nauman" To: current@freebsd.org Subject: run(4) fails to associate Re: wlan0 (iwn(4)) needed encouragement to associate Date: Sun, 17 Jan 2021 17:18:01 +0200 Message-ID: <3745430.kAAoriTUSa@sigill.theweb.org.ua> Organization: Private persom In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 4DJdpX5qJ9z3L2G X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jan 2021 15:18:13 -0000 On 2021 M01 17, Sun 15:19:56 EET David Wolfskill wrote: > After this morning's update of head from: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #124 > main-c256006-g8ca9ff4f28d2-dirty: Sat Jan 16 05:47:48 PST 2021 > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > amd64 1300135 1300135 > > > to: > > FreeBSD g1-55.catwhisker.org 13.0-ALPHA1 FreeBSD 13.0-ALPHA1 #125 > main-c256026-gb7ab6832cd98-dirty: Sun Jan 17 04:49:26 PST 2021 > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > amd64 1300135 1300135 > > on my laptop, the wireless link failed to associate by the time the > xdm login screen came up. But when I logged in (on vty1) and issued: > > service netif restart wlan0 > > it associated right away. (There was no issue with the corresponding > update for stable/12, so I have no reason to believe that there is an > issue with the access point or the laptop -- with respect to associating > properly, at least). And whether in head or stable/12, the woreless > link has (for the past several months of daily tracking both head and > stable/12) almost always associated by the time the xdm login screen > comes up. > > I tried it 3 times; each time, it failed to associate. (I only tried > the "service netif restart wlan0" the last 2 times -- the first time, > vty1 wasn't usable because I had experimented with a /boot/loader.conf > setting, which (as far as I know) is not relevant to this issue.) I can confirm that run(4) fails to associate on FreeBSD 13.0-ALPHA1 #38 main- c256026-gb7ab6832cd98-dirty Jan 17 kernel: ugen0.3: at usbus0 kernel: run0 on uhub0 kernel: run0: on usbus0 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:26:5a:0a:cb:fa kernel: run0: [HT] Enabling 802.11n webcamd[5382]: webcamd: Cannot find USB device kernel: wlan0: Ethernet address: 00:26:5a:0a:cb:fa root[6113]: /etc/rc.d/dhclient: WARNING: failed to start dhclient while it works with with one week old kernel FreeBSD 13.0-CURRENT #37 main-c255825-g2a4b22514635-dirty Jan 10 kernel: run0 on uhub0 kernel: run0: on usbus0 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:26:5a:0a:cb:fa kernel run0: [HT] Enabling 802.11n kernel run0: firmware RT2870 ver. 0.33 loaded kernel: wlan0: link state changed to UP > > Peace, > david