WiFi no longer works after resume

Lockheed · 2023-09-19 10:31:18

Since an update few days back, I no longer get WiFi on my laptop (T480, WiFi AX210/AX211/AX411). The same symptom exists on kernels linux, linux-lts and linux-zen.

When laptop is connected by cable, connection works, but it just won't show any wifis:

https://i.imgur.com/h0nSWDU.png

Restarting NetworkManager service does nothing

# systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Tue 2023-09-19 12:20:40 CEST; 47s ago
       Docs: man:NetworkManager(8)
   Main PID: 37164 (NetworkManager)
      Tasks: 4 (limit: 47803)
     Memory: 6.8M
        CPU: 626ms
     CGroup: /system.slice/NetworkManager.service
             └─37164 /usr/bin/NetworkManager --no-daemon

Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5509] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5521] manager: NetworkManager state is now CONNECTING
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5532] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5554] device (wlan0): Activation: (wifi) access point 'Harce i Swawole' has security, but secrets are required.
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5566] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 19 12:20:52 panzor NetworkManager[37164]: <warn>  [1695118852.5586] device (wlan0): no secrets: No agents were available for this request.
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5598] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5609] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 19 12:20:52 panzor NetworkManager[37164]: <warn>  [1695118852.5626] device (wlan0): Activation: failed for connection 'Harce i Swawole'
Sep 19 12:20:52 panzor NetworkManager[37164]: <info>  [1695118852.5640] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2023-09-23 17:16:40)

seth · 2023-09-19 12:03:08

Please post your complete system journal after the wifi loss:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Lockheed · 2023-09-19 12:25:19

curl: (6) Could not resolve host: 0x0.st

seth · 2023-09-19 12:34:27

Yeah, you'll have to do that w/ the working ethernet connection.
If that's not possible, redirect the output into a file instead and upload that after the reboot.

Lockheed · 2023-09-19 19:46:42

Got it on ethernet connection: http://0x0.st/HOJy.txt

seth · 2023-09-19 20:02:12

Sep 19 21:43:21 panzor systemd[1]: Stopped target Sleep.
Sep 19 21:43:21 panzor systemd[1]: Reached target Suspend.
…
Sep 19 21:43:21 panzor systemd[1]: Stopped Network Manager Wait Online.
Sep 19 21:43:21 panzor systemd[1]: nmrestart.service: Deactivated successfully.
Sep 19 21:43:21 panzor NetworkManager[55228]: <info>  [1695152601.8264] caught SIGTERM, shutting down normally.
Sep 19 21:43:21 panzor systemd[1]: Stopping Network Manager...
…
Sep 19 21:43:22 panzor kernel: r8152 6-2.1.2:1.0 eth1: v1.12.13
Sep 19 21:43:22 panzor kernel: usbcore: registered new interface driver cdc_ether
…
Sep 19 21:43:28 panzor wpa_supplicant[2269]: wlan0: Trying to associate with 08:60:6e:cb:9d:4e (SSID='-=Fast lane=-' freq=5300 MHz)
Sep 19 21:43:28 panzor kernel: wlan0: authenticated
Sep 19 21:43:28 panzor kernel: wlan0: VHT capa missing/short, disabling VHT/HE/EHT
Sep 19 21:43:28 panzor kernel: wlan0: associate with 08:60:6e:cb:9d:4e (try 1/3)
Sep 19 21:43:28 panzor NetworkManager[55462]: <info>  [1695152608.3192] device (wlan0): supplicant interface state: authenticating -> associating
Sep 19 21:43:28 panzor NetworkManager[55462]: <info>  [1695152608.3192] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Sep 19 21:43:28 panzor kernel: wlan0: RX AssocResp from 08:60:6e:cb:9d:4e (capab=0x11 status=0 aid=1)
Sep 19 21:43:28 panzor kernel: wlan0: associated
…
Sep 19 21:43:29 panzor wpa_supplicant[2269]: wlan0: CTRL-EVENT-CONNECTED - Connection to 08:60:6e:cb:9d:4e completed [id=0 id_str=]
Sep 19 21:43:29 panzor wpa_supplicant[2269]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=1000
…
Sep 19 21:43:29 panzor NetworkManager[55462]: <info>  [1695152609.4530] manager: NetworkManager state is now CONNECTED_SITE
…
Sep 19 21:43:29 panzor NetworkManager[55462]: <info>  [1695152609.8346] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 19 21:43:29 panzor NetworkManager[55462]: <info>  [1695152609.9652] dhcp4 (eth1): state changed new lease, address=192.168.7.77

You resume, restart NM, add an ethernet dongle (next to the present e1000e) wifi re-connects then you get a new lease over the dongle.

I don't think there's a problem w/ your network, looks more like a tailscale issue to me.
Can you reproduce the problem w/o the VPN?

Lockheed · 2023-09-19 21:14:39

There is no internet dongle. There's a Thunderbolt dock to witch ethernet is connected.
NM is being restarted, because when it wasn't it took it several minutes to un-freeze and connect to anything.
Not sure what tailscale has to do with anything here. It is a separate virtual interface, and if it was the cause, why would it mess up wifi, but not eth?

Also, the log shows WiFi tries to connect with a detected wifi network, but laptop behaves as if there wasn't even a wifi card.

Last edited by Lockheed (2023-09-19 21:30:52)

seth · 2023-09-19 21:29:36

Also, the log shows WiFi tries to connect with a detected wifi network, but laptop behaves as if there wasn't even a wifi card.

How can the laptop "behave as if there wasn't even a wifi card" when "the log shows WiFi tries to connect with a detected wifi network", iow, what's your metric to determine the malfunction.

Try to reproduce this w/o the VPN.

---
OT: "thunderbolt" and that's techincally the same as a dongle.

Edit:

Sep 19 21:43:20 panzor NetworkManager[2033]: <info>  [1695152600.9485] caught SIGTERM, shutting down normally.
                                                                        Intermediate: QSize(2560, 1440) 
…
Sep 19 21:43:21 panzor systemd[1]: Stopped target Sleep.
…
Sep 19 21:43:21 panzor systemd[1]: NetworkManager-wait-online.service: Main process exited, code=killed, status=15/TERM
Sep 19 21:43:21 panzor NetworkManager[55228]: <info>  [1695152601.8264] caught SIGTERM, shutting down normally.

Unless the timestamps are massively off, NM wasn't frozen around the sleep before you killed it?
Or do you mean you're currently killing it out of precaution?

Last edited by seth (2023-09-19 21:34:12)

Lockheed · 2023-09-23 16:36:22

I mean for a few months every time I resumed form sleep, NetworkManager would not see any WiFi networks. It would finally "wake up" after 1-3 minutes, but to make things quicker, I created a script that restarts it 2 seconds after resume.

I was looking at the logs and I can't see which one would suggest something wrong from Tailscale. Can you clarify?

seth · 2023-09-23 17:05:59

I created a script that restarts it 2 seconds after resume.

What also obfuscates the problem…

The VPN is the natural contender for "network went wrong but there's absolutely no issue w/ the actual lease", however that might be skewed by your workaround script.
Remove that script, undock the device to get the secondary ethernet out of the way, don't plug an rj45 - ie. force the wifi behavior.
Suspend, resume, let NM freak out, then dump the journal, connect to the network by whatever means and post the gathered journal.

Lockheed · Today 13:00:11

I don't have access to ethernet currently, but I disable tailscale.
I also removed the NM restart script.
The problem remains.

seth · Today 13:01:37

Once you have, please post a clean log (w/o tailscale and esp. the restart script) so we can see what's actually goign on.

Arch Linux

#1 2023-09-19 10:31:18

WiFi no longer works after resume

#2 2023-09-19 12:03:08

Re: WiFi no longer works after resume

#3 2023-09-19 12:25:19

Re: WiFi no longer works after resume

#4 2023-09-19 12:34:27

Re: WiFi no longer works after resume

#5 2023-09-19 19:46:42

Re: WiFi no longer works after resume

#6 2023-09-19 20:02:12

Re: WiFi no longer works after resume

#7 2023-09-19 21:14:39

Re: WiFi no longer works after resume

#8 2023-09-19 21:29:36

Re: WiFi no longer works after resume

#9 2023-09-23 16:36:22

Re: WiFi no longer works after resume

#10 2023-09-23 17:05:59

Re: WiFi no longer works after resume

#11 Today 13:00:11

Re: WiFi no longer works after resume

#12 Today 13:01:37

Re: WiFi no longer works after resume

Board footer