You are not logged in.
I've updated the system today and noticed that after waking up from suspend my laptop cannot connect to any wifi network. It seems to be caused by kernel update.
sudo journalctl -f
gives this output when I try to connect to a known network that worked just before suspending the machine:
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7864] device (wlan0): Activation: starting connection 'Pixel_9615' (2addaef9-92f6-4c9f-8c13-8dbfd0ad725f)
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7865] audit: op="connection-activate" uuid="2addaef9-92f6-4c9f-8c13-8dbfd0ad725f" name="Pixel_9615" pid=1934 uid=1000 result="success"
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7867] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7870] manager: NetworkManager state is now CONNECTING
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7874] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 27 18:43:33 carbon10 iwd[1194]: event: connect-info, ssid: Pixel_9615, bss: 52:e3:c6:2e:f6:91, signal: -33, load: 0/255
Oct 27 18:43:33 carbon10 iwd[1194]: event: state, old: autoconnect_full, new: connecting
Oct 27 18:43:33 carbon10 NetworkManager[1110]: <info> [1730051013.7889] device (wlan0): new IWD device state is connecting
Oct 27 18:43:34 carbon10 iwd[1194]: invalid HE capabilities for 52:e3:c6:2e:f6:91
Oct 27 18:43:34 carbon10 kernel: wlan0: authenticate with 52:e3:c6:2e:f6:91 (local address=70:a8:d3:e0:91:0b)
Oct 27 18:43:34 carbon10 kernel: wlan0: send auth to 52:e3:c6:2e:f6:91 (try 1/3)
Oct 27 18:43:34 carbon10 kernel: iwlwifi 0000:00:14.3: Not associated and the session protection is over already...
Oct 27 18:43:34 carbon10 kernel: wlan0: Connection to AP 52:e3:c6:2e:f6:91 lost
Oct 27 18:43:35 carbon10 kernel: wlan0: send auth to 52:e3:c6:2e:f6:91 (try 2/3)
Oct 27 18:43:36 carbon10 kernel: iwlwifi 0000:00:14.3: Not associated and the session protection is over already...
Oct 27 18:43:36 carbon10 kernel: wlan0: Connection to AP 52:e3:c6:2e:f6:91 lost
Oct 27 18:43:36 carbon10 kernel: wlan0: send auth to 52:e3:c6:2e:f6:91 (try 3/3)
Oct 27 18:43:36 carbon10 kernel: iwlwifi 0000:00:14.3: Not associated and the session protection is over already...
Oct 27 18:43:36 carbon10 kernel: wlan0: Connection to AP 52:e3:c6:2e:f6:91 lost
Oct 27 18:43:37 carbon10 kernel: wlan0: authentication with 52:e3:c6:2e:f6:91 timed out
Oct 27 18:43:37 carbon10 iwd[1194]: event: connect-timeout, reason: 2
Oct 27 18:43:37 carbon10 iwd[1194]: event: connect-failed, status: 1
Oct 27 18:43:37 carbon10 iwd[1194]: event: state, old: connecting, new: disconnected
Oct 27 18:43:37 carbon10 iwd[1194]: event: state, old: disconnected, new: autoconnect_quick
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <error> [1730051017.1069] device (wlan0): Activation: (wifi) Network.Connect failed: GDBus.Error:net.connman.iwd.Failed: Operation failed
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <info> [1730051017.1075] device (wlan0): state change: config -> failed (reason 'no-secrets', managed-type: 'full')
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <info> [1730051017.1081] manager: NetworkManager state is now DISCONNECTED
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <warn> [1730051017.1085] device (wlan0): Activation: failed for connection 'Pixel_9615'
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <info> [1730051017.1087] device (wlan0): new IWD device state is disconnected
Oct 27 18:43:37 carbon10 NetworkManager[1110]: <info> [1730051017.1095] device (wlan0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
I'm using iwd as the supplicant (EDIT: I've tried switching to wpa_supplicant but the issue still persists)
My network controller is
Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01)
Disabling and re-enabling wifi radio does not solve the problem. Neither does restarting the NetworkManager service. Rebooting the entire machine is the only "fix" that I've found
UPDATE:
Switching from kernel v6.11.5 to v6.6 (lts) makes the problem go away. It seems to be a kernel issue, then?
Last edited by kuba-orlik (2024-10-27 18:26:31)
Offline
I'm facing the same issue, and many others are experiencing it too, but I don't think anyone has reported it to Kernel Bugzilla.
Offline
Offline
I am getting the same issue too today...did you guys find any temporary or permanent solution to this issue
Offline
My current workaround is switching to kernel 6.6.61 and hoping the issues with 6.11 will be fixed soon
Offline