You are not logged in.
Pages: 1
I'm having issues with wifi lagging out for at least a month now and I can't figure out why. I've not changed my setting and I've been keeping everything up to date.
It can run fine for a while and then get very laggy or just completely stop working as seen with the pings
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=183 ttl=114 time=38.7 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=184 ttl=114 time=43.9 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=185 ttl=114 time=38.8 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=186 ttl=114 time=36.7 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=187 ttl=114 time=42.2 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=188 ttl=114 time=35.6 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=189 ttl=114 time=39.0 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=190 ttl=114 time=35.5 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=191 ttl=114 time=35.7 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=192 ttl=114 time=33.5 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=193 ttl=114 time=41.2 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=194 ttl=114 time=38.9 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=195 ttl=114 time=32.1 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=196 ttl=114 time=35.5 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=197 ttl=114 time=33.1 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=198 ttl=114 time=4438 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=199 ttl=114 time=4252 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=200 ttl=114 time=3240 ms
64 bytes from lhr25s25-in-f14.1e100.net (216.58.213.14): icmp_seq=201 ttl=114 time=2332 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=202 ttl=114 time=4084 ms
From Spymaster (192.168.1.66) icmp_seq=236 Destination Port Unreachable
ping: sendmsg: Operation not permitted
From Spymaster (192.168.1.66) icmp_seq=237 Destination Port Unreachable
ping: sendmsg: Operation not permitted
From Spymaster (192.168.1.66) icmp_seq=238 Destination Port Unreachable
ping: sendmsg: Operation not permitted
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=239 ttl=114 time=31.8 ms
64 bytes from ber01s14-in-f14.1e100.net (216.58.213.14): icmp_seq=240 ttl=114 time=31.4 ms
journalctl -f gives this when some of the wifi issues pop up.
Apr 11 19:47:49 Spymaster kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0xc040071b
Apr 11 19:48:27 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:48:27 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:48:39 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:48:39 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:49:04 Spymaster kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0xc040071b
Apr 11 19:49:15 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:49:15 Spymaster rtkit-daemon[775]: Supervising 9 threads of 5 processes of 1 users.
Apr 11 19:49:49 Spymaster kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0xc040071b
Apr 11 19:49:49 Spymaster kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0xc040071b
lspci info gives this
00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Processor Host Bridge/DRAM Registers [Coffee Lake H] (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:14.3 Network controller: Intel Corporation Cannon Lake PCH CNVi WiFi (rev 10)
00:15.0 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.1 Serial bus controller: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #14 (rev f0)
00:1f.0 ISA bridge: Intel Corporation HM470 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)
02:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
03:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
03:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
03:02.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
3a:00.0 USB controller: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] (rev 02)
3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
Does anybody has any ideas what to check or do? I don't have too much time to mess about with this.
Offline
https://bbs.archlinux.org/viewtopic.php?id=272848
iwd or wpa_supplicant?
Offline
I am using wpa_supplicant and NetworkManager
Offline
Are the services both enabled? They shouldn't be.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
systemctl is-active returns active for both.
Offline
That doesn't necessarily answer the question.
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
Offline
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
returns
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket | sockets.target.wants
display-manager.service | system
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gpg-agent-browser.socket | sockets.target.wants
gpg-agent-extra.socket | sockets.target.wants
gpg-agent.socket | sockets.target.wants
gpg-agent-ssh.socket | sockets.target.wants
mullvad-daemon.service | multi-user.target.wants
mullvad-daemon.service | system
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
ntpd.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire-media-session.service | pipewire.service.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
xdg-user-dirs-update.service | default.target.wants
Offline
wpa_supplicant is invoked by NM, as it should be.
Looking at the output: lose the VPN - still a problem?
The journal snippet you posted points towards roaming - does your AP provide 2.4 and 5GHz and does the problem remain if you disable one of them?
Offline
I've been testing with the VPN connected and disconnected. I've completely disabled the service which I didn't think to do previously. Currently, I haven't had a lag spike, but I'll continue testing and update later.
Offline
Pages: 1