Bug 249444 - iwm 9250 not starting properly after boot
Summary: iwm 9250 not starting properly after boot
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 12.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-19 08:27 UTC by Manuel Stühn
Modified: 2021-06-15 19:44 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Stühn 2020-09-19 08:27:03 UTC 
On my Lenovo TP T460 the iwm interface (Intel 8260) does not work properly after booting.
My settings are:
FreeBSD 12.1p10 + FreeBSD 12.2-BETA1

/boot/loader.conf:
if_iwm_load="YES"
iwm8000Cfw_load="YES"

/etc/rc.conf
ifconfig_em0="up"
wlans_iwm0="wlan0"
ifconfig_wlan0="WPA powersave"
create_args_wlan0=" country DE"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP"

during boot, i get a lot of 
wlan0: link state changed to UP
lagg0: link state changed to UP
wlan0: link state changed to DOWN
lagg0: link state changed to DOWN
iwm0: device timeout
iwm0: dumping device error log
iwm0: errlog not found, skipping
wlan0: link state changed to UP
lagg0: link state changed to UP

In most cases there is no connection at the point when the system has booted to login-prompt. But a "service netif restart" connects the wlan reliably!

I've tried also to load the iwm-modules via kld_list in rc.conf, or let FreeBSD autodetect the iwm but it does not work also. However,  restarting netif does work in all those loading scenarios and brings up iwm+lagg.
Comment 1 Manuel Stühn 2021-06-15 19:44:18 UTC 
Left FreeBSD on the desktop.