From owner-freebsd-current@freebsd.org Sun Jan 17 13:50:03 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 2813E4EA2D3 for ; Sun, 17 Jan 2021 13:50:03 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJbrn5kWwz3DVm for ; Sun, 17 Jan 2021 13:50:01 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l18RG-000Bp1-8v for freebsd-current@freebsd.org; Sun, 17 Jan 2021 14:49:54 +0100 Received: from [192.168.67.33] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1l18RF-0006WI-O3 for freebsd-current@freebsd.org; Sun, 17 Jan 2021 14:49:53 +0100 Subject: Re: wlan0 (iwn(4)) needed encouragement to associate To: freebsd-current@freebsd.org References: From: Jakob Alvermark Message-ID: <6b319f64-f457-47dc-bdcf-fd160b1ba90f@alvermark.net> Date: Sun, 17 Jan 2021 14:49:53 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4DJbrn5kWwz3DVm X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[alvermark.net:+]; NEURAL_HAM_SHORT(-0.99)[-0.987]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] 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 13:50:03 -0000 On 1/17/21 2:19 PM, 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.) > > Peace, > david +1 I have the same issue. This is on an Intel Centrino Advanced 6235 I also noticed that wpa_supplicant is using 100% CPU on one core. Jakob