Re: wlan0 (iwn(4)) needed encouragement to associate

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_at_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_at_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