Bug 286493 - iwlwifi takes 2+ minutes to associate with 5g ssid
Summary: iwlwifi takes 2+ minutes to associate with 5g ssid
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Bjoern A. Zeeb
URL:
Keywords:
Depends on:
Blocks: iwlwifi
  Show dependency tree / graph
 
Reported: 2025-05-01 06:24 UTC by Pat Maddox
Modified: 2025-06-09 20:53 UTC (History)
2 users (show)

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 Pat Maddox 2025-05-01 06:24:38 UTC 
I have an ax210 on a Thinkpad T14 Gen 2 AMD. iwlwifi connects to my 2.4g ssid no problem. It takes 2+ minutes to connect to a 5g ssid. The longest I've seen it take is 9 minutes. CURRENT April stabilization week d4763484f911

/var/log/message output after running `service netif start wlan0` is below. I'm happy to do any troubleshooting if you can provide me with some guidance.

ifconfig_wlan0="mode 11a ssid padillac_admin WPA DHCP"

Apr 30 22:59:51 gulliver kernel: iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
Apr 30 22:59:51 gulliver kernel: iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Apr 30 22:59:51 gulliver kernel: iwlwifi0: WFPM_AUTH_KEY_0: 0x90
Apr 30 22:59:51 gulliver kernel: iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
Apr 30 22:59:51 gulliver wpa_supplicant[3209]: Successfully initialized wpa_supplicant
Apr 30 22:59:51 gulliver wpa_supplicant[3209]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
Apr 30 22:59:51 gulliver syslogd: last message repeated 1 times
Apr 30 22:59:52 gulliver kernel: wlan0: Ethernet address: bc:38:98:a8:42:a1
Apr 30 23:02:06 gulliver wpa_supplicant[3210]: wlan0: Trying to associate with 4a:22:54:36:bb:0b (SSID='padillac_admin' freq=5745 MHz)
Apr 30 23:02:06 gulliver wpa_supplicant[3210]: wlan0: Associated with 4a:22:54:36:bb:0b
Apr 30 23:02:06 gulliver wpa_supplicant[3210]: wlan0: WPA: Key negotiation completed with 4a:22:54:36:bb:0b [PTK=CCMP GTK=CCMP]
Apr 30 23:02:06 gulliver wpa_supplicant[3210]: wlan0: CTRL-EVENT-CONNECTED - Connection to 4a:22:54:36:bb:0b completed [id=0 id_str=]
Apr 30 23:02:06 gulliver kernel: wlan0: link state changed to UP
Apr 30 23:02:08 gulliver dhclient[3389]: New IP Address (wlan0): 172.21.1.129
Apr 30 23:02:08 gulliver dhclient[3393]: New Subnet Mask (wlan0): 255.255.255.0
Apr 30 23:02:08 gulliver dhclient[3397]: New Broadcast Address (wlan0): 172.21.1.255
Apr 30 23:02:08 gulliver dhclient[3401]: New Routers (wlan0): 172.21.1.1
Comment 1 Pat Maddox 2025-05-01 07:44:29 UTC 
Here's one that took nearly 20 minutes:

May  1 00:05:48 gulliver wpa_supplicant[5800]: Successfully initialized wpa_supplicant
May  1 00:05:48 gulliver wpa_supplicant[5800]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
May  1 00:05:48 gulliver syslogd: last message repeated 1 times
May  1 00:05:48 gulliver kernel: iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
May  1 00:05:48 gulliver kernel: iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
May  1 00:05:48 gulliver kernel: iwlwifi0: WFPM_AUTH_KEY_0: 0x90
May  1 00:05:48 gulliver kernel: iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
May  1 00:05:48 gulliver kernel: wlan0: Ethernet address: bc:38:98:a8:42:a1
May  1 00:24:50 gulliver wpa_supplicant[5801]: wlan0: Trying to associate with 4a:22:54:36:bb:0b (SSID='padillac_admin' freq=5745 MHz)
May  1 00:24:50 gulliver wpa_supplicant[5801]: wlan0: Associated with 4a:22:54:36:bb:0b
May  1 00:24:50 gulliver kernel: wlan0: link state changed to UP
May  1 00:24:50 gulliver wpa_supplicant[5801]: wlan0: WPA: Key negotiation completed with 4a:22:54:36:bb:0b [PTK=CCMP GTK=CCMP]
May  1 00:24:50 gulliver wpa_supplicant[5801]: wlan0: CTRL-EVENT-CONNECTED - Connection to 4a:22:54:36:bb:0b completed [id=0 id_str=]
May  1 00:24:51 gulliver dhclient[6626]: New IP Address (wlan0): 172.21.1.129
May  1 00:24:51 gulliver dhclient[6630]: New Subnet Mask (wlan0): 255.255.255.0
May  1 00:24:51 gulliver dhclient[6634]: New Broadcast Address (wlan0): 172.21.1.255
May  1 00:24:51 gulliver dhclient[6638]: New Routers (wlan0): 172.21.1.1
Comment 2 Bjoern A. Zeeb freebsd_committer freebsd_triage 2025-05-01 20:05:45 UTC 
I have reports from 3 more people who are having trouble to get onto 5Ghz but 2.4 works fine.

You just provided another clue that it may take time.

I assume in your examples below wpa_supplicant.conf is told not to connect to 2.4 but only to a dedicated 5Ghz SSID?

Can you crank up the debug level for wpa_supplicant and if this is a debug kernel turn on wlandebug +scan   (also possible from rc.conf).
It'll log a bit more but we need to figure out (a) if the 5Ghz SSID is in the scan results, if wpa_supplicant tries to assoc to it but fails, and/or why it fails or does not try to assoc to it.

I'll likely send you another set of questions by direct email.
Comment 3 Pat Maddox 2025-05-01 22:42:18 UTC 
(In reply to Bjoern A. Zeeb from comment #2)

> I assume in your examples below wpa_supplicant.conf is told not to connect to 2.4 but only to a dedicated 5Ghz SSID?

Correct

> It'll log a bit more but we need to figure out (a) if the 5Ghz SSID is in the scan results, if wpa_supplicant tries to assoc to it but fails, and/or why it fails or does not try to assoc to it.

When it wasn't working (see below), `ifconfig wlan0` would typically not show my 5g network, although it would show plenty of others nearby. It would be pretty sporadic. Maybe an indicator that it was my access point rather than iwlwifi to blame.

---

Here's something interesting... I rearranged my networking hardware today, which meant powering off the access point.

Now iwlwifi is reliably associating with the access point and getting an IP within a few seconds.

I will keep an eye on this and see if reliability degrades, and if restarting the access point is a fix.

Here's the current log:

May  1 15:36:50 gulliver kernel: iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
May  1 15:36:50 gulliver kernel: iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
May  1 15:36:50 gulliver kernel: iwlwifi0: WFPM_AUTH_KEY_0: 0x90
May  1 15:36:50 gulliver kernel: iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
May  1 15:36:51 gulliver wpa_supplicant[3737]: Successfully initialized wpa_supplicant
May  1 15:36:51 gulliver wpa_supplicant[3737]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument
May  1 15:36:51 gulliver syslogd: last message repeated 1 times
May  1 15:36:51 gulliver kernel: wlan0: Ethernet address: bc:38:98:a8:42:a1
May  1 15:36:54 gulliver wpa_supplicant[3738]: wlan0: Trying to associate with 4a:22:54:36:bb:0b (SSID='padillac_admin' freq=5805 MHz)
May  1 15:36:54 gulliver wpa_supplicant[3738]: wlan0: Associated with 4a:22:54:36:bb:0b
May  1 15:36:54 gulliver wpa_supplicant[3738]: wlan0: WPA: Key negotiation completed with 4a:22:54:36:bb:0b [PTK=CCMP GTK=CCMP]
May  1 15:36:54 gulliver wpa_supplicant[3738]: wlan0: CTRL-EVENT-CONNECTED - Connection to 4a:22:54:36:bb:0b completed [id=0 id_str=]
May  1 15:36:54 gulliver dhclient[3868]: New IP Address (wlan0): 172.21.1.129
May  1 15:36:54 gulliver dhclient[3872]: New Subnet Mask (wlan0): 255.255.255.0
May  1 15:36:54 gulliver dhclient[3876]: New Broadcast Address (wlan0): 172.21.1.255
May  1 15:36:54 gulliver dhclient[3880]: New Routers (wlan0): 172.21.1.1
May  1 15:36:54 gulliver kernel: wlan0: link state changed to UP
Comment 4 Pavel Timofeev 2025-05-18 02:54:20 UTC 
Hello
I experience the same problem on Framework Laptop Intel 12th gen.
My AP is a home router with OpenWRT installed. Router restart doesn't help in my case. It still takes ages to connect.