Wifi connection with NetworkManager timing out randomly

LaurentMercier · Yesterday 12:40:17

Hi,

I've been having no issues with NetworkManager on my machine (Lenovo ThinkPad P16s Gen 2) for a while now but ever since a month ago or so I keep timing out on any website on any wifi connection. This is true for different wifi connections, as I tried with 2 different ones in my home and my hotspot. Furthermore, sometimes it just works, as it did yesterday and I was able to watch youtube without problem. But most of the times, like today, I try to reach any website and it just times out or takes a super long time. Changing wifi sometimes helps, but after 2 minutes it goes back to the way it was. Also when I'm at school for some reason I never had this problem, but this might be a coincidence.

Here are the last 300 lines of dmesg:

https://0x0.st/PXxY.txt

Here are the last 300 lines of journalctl -u NetworkManager:

https://0x0.st/PXx3.txt

Maybe it has something to do with the wifi card drivers? I really don't understand what is causing that and why sometimes it just works. I hope you can help me and have a good day.

Last edited by LaurentMercier (Yesterday 23:03:19)

seth · Yesterday 14:55:55

Here are the last 300 lines of

something
Please post your complete system journal for the boot:

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

You're moving between 3 different APs

Jan 12 13:07:30 LaptopLM NetworkManager[681]: <info>  [1768219650.6871] device (wlp2s0): Activation: starting connection 'PlanetCampus - Prive 006606' (dabda581-80ca-4139-b688-6e1532dd6131)
Jan 12 13:08:13 LaptopLM NetworkManager[681]: <info>  [1768219693.2257] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:10:19 LaptopLM NetworkManager[681]: <info>  [1768219819.4076] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:12:23 LaptopLM NetworkManager[681]: <info>  [1768219943.8781] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:12:27 LaptopLM NetworkManager[681]: <info>  [1768219947.3894] device (wlp2s0): Activation: starting connection 'Cell Laurent' (eebab661-bfda-4bd4-ad0f-cdf2d48e0722)

so could just be a roaming issue?

Whether the

[260954.351540] ath11k_pci 0000:02:00.0: Received with invalid mcs in HE mode 13

WiFi6 problems are related to this at all remains to be seen.

LaurentMercier · Yesterday 15:05:28

seth wrote:

Here are the last 300 lines of

something
Please post your complete system journal for the boot:

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

You're moving between 3 different APs

Jan 12 13:07:30 LaptopLM NetworkManager[681]: <info>  [1768219650.6871] device (wlp2s0): Activation: starting connection 'PlanetCampus - Prive 006606' (dabda581-80ca-4139-b688-6e1532dd6131)
Jan 12 13:08:13 LaptopLM NetworkManager[681]: <info>  [1768219693.2257] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:10:19 LaptopLM NetworkManager[681]: <info>  [1768219819.4076] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:12:23 LaptopLM NetworkManager[681]: <info>  [1768219943.8781] device (wlp2s0): Activation: starting connection 'eduroam' (03eaeed4-59a3-4fcc-a325-94e150d3d098)
Jan 12 13:12:27 LaptopLM NetworkManager[681]: <info>  [1768219947.3894] device (wlp2s0): Activation: starting connection 'Cell Laurent' (eebab661-bfda-4bd4-ad0f-cdf2d48e0722)

so could just be a roaming issue?

Whether the

[260954.351540] ath11k_pci 0000:02:00.0: Received with invalid mcs in HE mode 13

WiFi6 problems are related to this at all remains to be seen.

Sorry about that, I posted the last 300 lines because the full journal boot is really long (I usually let my laptop sleep so its been the same boot for a week maybe) and I had trouble uploading it to 0x0 with curl since my connection was unstable. It's working fine now it seems and I was able to upload the full system journal for the boot:
http://0x0.st/PXYe.txt

As for the 3 different APs, this is me manually changing wifi networks to see if it resolves the issue, but as I said, it didn't solve the problem.

seth · Yesterday 15:25:11

The journal is 89MB …

You connect effortlessly

Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: Trying to associate with ac:5e:14:5f:40:70 (SSID='PlanetCampus - Prive 006606' freq=5180 MHz)
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.1213] device (wlp2s0): supplicant interface state: authenticating -> associating
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.1213] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Jan 09 12:43:11 LaptopLM kernel: wlp2s0: associate with ac:5e:14:5f:40:70 (try 1/3)
Jan 09 12:43:11 LaptopLM kernel: wlp2s0: RX AssocResp from ac:5e:14:5f:40:70 (capab=0x1511 status=0 aid=3)
Jan 09 12:43:11 LaptopLM kernel: wlp2s0: associated
Jan 09 12:43:11 LaptopLM systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 09 12:43:11 LaptopLM kernel: wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by ac:5e:14:5f:40:70
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: Associated with ac:5e:14:5f:40:70
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.2685] device (wlp2s0): supplicant interface state: associating -> 4way_handshake
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.2686] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> 4way_handshake
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: WPA: Key negotiation completed with ac:5e:14:5f:40:70 [PTK=CCMP GTK=CCMP]
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to ac:5e:14:5f:40:70 completed [id=0 id_str=]
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: RSN: Group rekeying completed with ac:5e:14:5f:40:70 [GTK=CCMP]
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3183] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3184] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "PlanetCampus - Prive 006606"
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3184] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3185] device (wlp2s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3189] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.3865] dhcp4 (wlp2s0): state changed new lease, address=10.192.6.35, acd pending
Jan 09 12:43:11 LaptopLM wpa_supplicant[794]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-44 noise=-96 txrate=6000
Jan 09 12:43:11 LaptopLM NetworkManager[681]: <info>  [1767958991.5466] dhcp4 (wlp2s0): state changed new lease, address=10.192.6.35

and 12s later starts a drumbeat of

Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:ieee80211_rx_list+0xab9/0xd90 [mac80211]
Jan 09 12:43:23 LaptopLM kernel: RIP: 0033:0x7f568b2717d2
Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:ieee80211_rx_list+0xab9/0xd90 [mac80211]
Jan 09 12:43:23 LaptopLM kernel: RIP: 0033:0x7f568b2717d2
Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:ieee80211_rx_list+0xab9/0xd90 [mac80211]
Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x410
Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:ieee80211_rx_list+0xab9/0xd90 [mac80211]
Jan 09 12:43:23 LaptopLM kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x410
Jan 09 12:43:24 LaptopLM kernel: RIP: 0010:ieee80211_rx_list+0xab9/0xd90 [mac80211]

that spams the journal.

Disable docker/containerd, the VPN and virtualbox shows up there as well.
W/o the bridge, veth and tun device: does ath11k still run into a frenzy?

LaurentMercier · Yesterday 15:54:02

Yeah sorry about the journal, as I said the boot is like a couple days old. I have disabled docker and containerd (and killed old containers that seemed to be still running), as well as vbox related services and vpn ones. I had cisco-secure-client installed previously but removed it, but a service seemed to still be there and failing, I have disabled and removed it, maybe this is the problem? Right now I don't seem to have a problem, and when I grepped for mac80211 in dmesg, nothing appeared.

Here is my ip link now:

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether fc:5c:ee:df:98:5b brd ff:ff:ff:ff:ff:ff
    altname enxfc5ceedf985b
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 8c:3b:4a:47:f2:54 brd ff:ff:ff:ff:ff:ff
    altname wlx8c3b4a47f254

Here is the journalctl -b from this boot: http://0x0.st/PXYh.txt.

And here is the dmesg: http://0x0.st/PXYC.txt.

In your opinion, could it have been the lingering cisco-secure-client service that caused this problem? I also have openVPN on this machine but no VPN activated for the moment and tried to disable related services.

seth · Yesterday 16:05:23

No worries about the journal - the comment was a warning to the general public
And also to highlight the main problem.

In your opinion, could it have been the lingering cisco-secure-client service that caused this problem?

Weird traffic or netfilter rules throwing jamming the TCP buffer and/or causing unreasonable access to the NICs?
Maybe.
I guess we'll see if and when this happens again - last time the problems started immediately after the boot.

If it's not the interface mess, try "ath11k.crypto_mode=1" (software encryption), https://wiki.archlinux.org/title/Kernel_parameters

LaurentMercier · Yesterday 16:23:08

Will update if it happens again and we'll see from there. For now I think I'll mark this as solved, thank you for your time and your help!

LaurentMercier · Yesterday 23:07:11

I just opened my laptop from sleep and it redid the same problem. However changing to another wifi seems to have fixed it for the time being. I think there is the same ath11k frenzy.

journalctl -b:
https://0x0.st/PXU0.txt

dmesg:
https://0x0.st/PXUG.txt

Arch Linux

#1 Yesterday 12:40:17

Wifi connection with NetworkManager timing out randomly

#2 Yesterday 14:55:55

Re: Wifi connection with NetworkManager timing out randomly

#3 Yesterday 15:05:28

Re: Wifi connection with NetworkManager timing out randomly

#4 Yesterday 15:25:11

Re: Wifi connection with NetworkManager timing out randomly

#5 Yesterday 15:54:02

Re: Wifi connection with NetworkManager timing out randomly

#6 Yesterday 16:05:23

Re: Wifi connection with NetworkManager timing out randomly

#7 Yesterday 16:23:08

Re: Wifi connection with NetworkManager timing out randomly

#8 Yesterday 23:07:11

Re: Wifi connection with NetworkManager timing out randomly

Board footer