Network very slow to wakeup

Support Network
1

Since about two months the wifi connection is reluctant waking up after the system resumes from sleep. Sometimes it takes 2-5 seconds but also up to 15 seconds. Sometimes no reconnect at all, and then after unplug/plug the usb wifi receiver, it does.
This is on a desktop running kernel 6.6. since at least a year.

❯ inxi -n
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  IF: eno1 state: down mac: xyx
  Device-2: TP-Link Archer T3U [Realtek RTL8812BU] driver: rtw_8822bu
    type: USB
  IF: wlp0s20f0u11 state: up mac: xdf

My question is: what is going on, the system log does not give me a clue, what is normal, what not, what should I do?

Thanks
excerpt from a recent system log:

18.12.2024 15:39:49:872	systemd-sleep	Performing sleep operation 'suspend'...
18.12.2024 15:39:49:873	kernel	PM: suspend entry (deep)
18.12.2024 16:20:29:065	kernel	Filesystems sync: 0.013 seconds
18.12.2024 16:20:29:065	kernel	Freezing user space processes
18.12.2024 16:20:29:065	kernel	Freezing user space processes completed (elapsed 0.007 seconds)
18.12.2024 16:20:29:065	kernel	OOM killer disabled.
18.12.2024 16:20:29:065	kernel	Freezing remaining freezable tasks
18.12.2024 16:20:29:065	kernel	Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
18.12.2024 16:20:29:065	kernel	printk: Suspending console(s) (use no_console_suspend to debug)
18.12.2024 16:20:29:075	kernel	e1000e: EEE TX LPI TIMER: 00000011
18.12.2024 16:20:29:075	kernel	sd 4:0:0:0: [sda] Synchronizing SCSI cache
18.12.2024 16:20:29:075	kernel	ata5.00: Entering standby power mode
18.12.2024 16:20:29:075	kernel	usb 1-11: reset high-speed USB device number 9 using xhci_hcd
18.12.2024 16:20:29:076	kernel	ACPI: PM: Preparing to enter system sleep state S3
18.12.2024 16:20:29:076	kernel	ACPI: PM: Saving platform NVS memory
18.12.2024 16:20:29:076	kernel	Disabling non-boot CPUs ...
18.12.2024 16:20:29:076	kernel	smpboot: CPU 1 is now offline
18.12.2024 16:20:29:076	kernel	smpboot: CPU 2 is now offline
18.12.2024 16:20:29:076	kernel	smpboot: CPU 3 is now offline
18.12.2024 16:20:29:076	kernel	smpboot: CPU 4 is now offline
18.12.2024 16:20:29:076	kernel	smpboot: CPU 5 is now offline
18.12.2024 16:20:29:076	kernel	ACPI: PM: Low-level resume complete
18.12.2024 16:20:29:076	kernel	ACPI: PM: Restoring platform NVS memory
18.12.2024 16:20:29:076	kernel	Enabling non-boot CPUs ...
18.12.2024 16:20:29:076	kernel	smpboot: Booting Node 0 Processor 1 APIC 0x2
18.12.2024 16:20:29:076	kernel	CPU1 is up
18.12.2024 16:20:29:076	kernel	smpboot: Booting Node 0 Processor 2 APIC 0x4
18.12.2024 16:20:29:076	kernel	CPU2 is up
18.12.2024 16:20:29:076	kernel	smpboot: Booting Node 0 Processor 3 APIC 0x6
18.12.2024 16:20:29:076	kernel	CPU3 is up
18.12.2024 16:20:29:076	kernel	smpboot: Booting Node 0 Processor 4 APIC 0x8
18.12.2024 16:20:29:076	kernel	CPU4 is up
18.12.2024 16:20:29:076	kernel	smpboot: Booting Node 0 Processor 5 APIC 0xa
18.12.2024 16:20:29:076	kernel	CPU5 is up
18.12.2024 16:20:29:076	kernel	ACPI: PM: Waking up from system sleep state S3
18.12.2024 16:20:29:076	kernel	i915 0000:00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
18.12.2024 16:20:29:076	kernel	i915 0000:00:02.0: [drm] [ENCODER:111:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
18.12.2024 16:20:29:076	kernel	i915 0000:00:02.0: [drm] [ENCODER:121:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it
18.12.2024 16:20:29:076	kernel	i915 0000:00:02.0: [drm] [ENCODER:125:DDI E/PHY E] is disabled/in DSI mode with an ungated DDI clock, gate it
18.12.2024 16:20:29:076	kernel	nvme nvme0: Shutdown timeout set to 8 seconds
18.12.2024 16:20:29:077	kernel	nvme nvme0: 6/0/0 default/read/poll queues
18.12.2024 16:20:29:081	kernel	nvme nvme1: 6/0/0 default/read/poll queues
18.12.2024 16:20:29:081	kernel	ata4: SATA link down (SStatus 0 SControl 300)
18.12.2024 16:20:29:081	kernel	ata3: SATA link down (SStatus 0 SControl 300)
18.12.2024 16:20:29:081	kernel	ata2: SATA link down (SStatus 4 SControl 300)
18.12.2024 16:20:29:081	kernel	ata6: SATA link down (SStatus 4 SControl 300)
18.12.2024 16:20:29:081	kernel	pci_bus 0000:04: Allocating resources
18.12.2024 16:20:29:081	kernel	pci 0000:03:00.0: bridge window [io  0x1000-0x0fff] to [bus 04] add_size 1000
18.12.2024 16:20:29:081	kernel	pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 04] add_size 200000 add_align 100000
18.12.2024 16:20:29:082	kernel	pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 04] add_size 200000 add_align 100000
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
18.12.2024 16:20:29:083	kernel	pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
18.12.2024 16:20:29:084	kernel	pci 0000:03:00.0: PCI bridge to [bus 04]
18.12.2024 16:20:29:084	kernel	mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
18.12.2024 16:20:29:084	kernel	OOM killer enabled.
18.12.2024 16:20:29:084	kernel	Restarting tasks ... done.
18.12.2024 16:20:29:085	kernel	random: crng reseeded on system resumption
18.12.2024 16:20:29:085	kernel	PM: suspend exit
18.12.2024 16:20:29:085	systemd-sleep	System returned from sleep operation 'suspend'.
18.12.2024 16:20:29:094	kernel	rtw_8822bu 1-11:1.0: Firmware version 27.2.0, H2C version 13
18.12.2024 16:20:29:407	kernel	e1000e 0000:00:1f.6 eno1: NIC Link is Down
18.12.2024 16:20:29:408	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-DSCP-POLICY clear_all
18.12.2024 16:20:29:408	systemd	Starting Load/Save RF Kill Switch Status...
18.12.2024 16:20:29:408	wpa_supplicant	nl80211: deinit ifname=wlp0s20f0u11 disabled_11b_rates=0
18.12.2024 16:20:29:409	NetworkManager	<info>  [1734535229.0724] radio killswitch /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/ieee80211/phy7/rfkill7 disappeared
18.12.2024 16:20:29:409	kwin_wayland	kwin_libinput: Libinput: event3  - Apple Inc. Apple Keyboard: client bug: event processing lagging behind by 952ms, your system is too slow
18.12.2024 16:20:29:414	systemd-sleep	Successfully thawed unit 'user.slice'.
18.12.2024 16:20:29:423	kernel	rtw_8822bu 1-11:1.0 wlp0s20f0u11: renamed from wlan0
18.12.2024 16:20:29:423	systemd	systemd-suspend.service: Deactivated successfully.
18.12.2024 16:20:29:423	systemd	Finished System Suspend.
18.12.2024 16:20:29:423	systemd	Started Load/Save RF Kill Switch Status.
18.12.2024 16:20:29:423	systemd	Stopped target Sleep.
18.12.2024 16:20:29:423	systemd	Reached target Suspend.
18.12.2024 16:20:29:423	systemd-logind	Operation 'suspend' finished.
18.12.2024 16:20:29:424	systemd	Stopped target Suspend.
18.12.2024 16:20:29:424	NetworkManager	<info>  [1734535229.1201] manager: sleep: wake requested (sleeping: yes  enabled: yes)
18.12.2024 16:20:29:424	NetworkManager	<info>  [1734535229.1202] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
18.12.2024 16:20:29:424	systemd	Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
18.12.2024 16:20:29:424	kdeconnectd	2024-12-18T16:20:29 kdeconnect.core: No local bluetooth adapter found
18.12.2024 16:20:29:426	kdeconnectd	2024-12-18T16:20:29 default: Error sending UDP packet: QAbstractSocket::NetworkError
18.12.2024 16:20:29:426	kdeconnectd	2024-12-18T16:20:29 kdeconnect.core: Failed to open any MDNS client sockets
18.12.2024 16:20:29:426	kdeconnectd	2024-12-18T16:20:29 kdeconnect.core: Failed to open any MDNS server sockets
18.12.2024 16:20:29:426	NetworkManager	<info>  [1734535229.2040] device (eno1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
18.12.2024 16:20:29:426	NetworkManager	<info>  [1734535229.4084] manager: NetworkManager state is now DISCONNECTED
18.12.2024 16:20:29:426	NetworkManager	<info>  [1734535229.4089] device (wlan0): driver supports Access Point (AP) mode
18.12.2024 16:20:29:426	NetworkManager	<info>  [1734535229.4104] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/11)
18.12.2024 16:20:29:426	NetworkManager	<info>  [1734535229.4151] rfkill8: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/ieee80211/phy8/rfkill8) (driver rtw_8822bu)
18.12.2024 16:20:29:440	NetworkManager	<info>  [1734535229.4408] device (wlan0): interface index 11 renamed iface from 'wlan0' to 'wlp0s20f0u11'
18.12.2024 16:20:29:448	NetworkManager	<info>  [1734535229.4484] device (wlp0s20f0u11): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
18.12.2024 16:20:30:099	wpa_supplicant	dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
18.12.2024 16:20:30:099	NetworkManager	<info>  [1734535230.0997] device (wlp0s20f0u11): supplicant interface state: internal-starting -> disconnected
18.12.2024 16:20:30:107	NetworkManager	<info>  [1734535230.0998] device (wlp0s20f0u11): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
18.12.2024 16:20:30:474	rtkit-daemon	Supervising 1 threads of 1 processes of 1 users.
18.12.2024 16:20:30:474	rtkit-daemon	Supervising 1 threads of 1 processes of 1 users.
18.12.2024 16:20:30:884	kernel	ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
18.12.2024 16:20:30:884	kernel	ata5.00: Entering active power mode
18.12.2024 16:20:30:971	kernel	sd 4:0:0:0: [sda] Starting disk
18.12.2024 16:20:31:021	kernel	ata5.00: configured for UDMA/133
18.12.2024 16:20:32:048	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
18.12.2024 16:20:32:048	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5200 max_tx_power=2000 no_ir=1
18.12.2024 16:20:32:048	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5200 max_tx_power=2000
18.12.2024 16:20:34:041	wpa_supplicant	wlp0s20f0u11: Reject scan trigger since one is already pending
18.12.2024 16:20:34:426	systemd	systemd-rfkill.service: Deactivated successfully.
18.12.2024 16:20:38:103	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
18.12.2024 16:21:00:628	NetworkManager	<info>  [1734535260.6285] policy: auto-activating connection 'Arjan' (9771e9f6-5329-4090-854c-0fac47a116d5)
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6288] device (wlp0s20f0u11): Activation: starting connection 'Arjan' (9771e9f6-5329-4090-854c-0fac47a116d5)
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6288] device (wlp0s20f0u11): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6289] manager: NetworkManager state is now CONNECTING
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6290] device (wlp0s20f0u11): state change: prepare -> config (reason 'none', managed-type: 'full')
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6292] device (wlp0s20f0u11): Activation: (wifi) access point 'Arjan' has security, but secrets are required.
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6292] device (wlp0s20f0u11): state change: config -> need-auth (reason 'none', managed-type: 'full')
18.12.2024 16:21:00:629	NetworkManager	<info>  [1734535260.6292] sup-iface[053b3bd0ea54b444,8,wlp0s20f0u11]: wps: type pbc start...
18.12.2024 16:21:00:630	wpa_supplicant	wlp0s20f0u11: WPS-PBC-ACTIVE
18.12.2024 16:21:00:642	kded6	kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
18.12.2024 16:21:00:642	plasmashell	kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
18.12.2024 16:21:00:642	NetworkManager	<info>  [1734535260.6425] device (wlp0s20f0u11): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6427] device (wlp0s20f0u11): state change: prepare -> config (reason 'none', managed-type: 'full')
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] device (wlp0s20f0u11): Activation: (wifi) connection 'Arjan' has security, and secrets exist.  No new secrets needed.
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] Config: added 'ssid' value 'Arjan'
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] Config: added 'scan_ssid' value '1'
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] Config: added 'freq_list' value '5035 5040 5045 5055 5060 5080 5170 5180 5190 5200 5210 5220 5230 5240 5250 5260 5280 5290 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5745 5760 5765 5785 5800 5805 5825 4915 4920 4925 4935 4945 4960 4980'
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] Config: added 'bgscan' value 'simple:30:-65:300'
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6429] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
18.12.2024 16:21:00:643	NetworkManager	<info>  [1734535260.6430] Config: added 'psk' value '<hidden>'
18.12.2024 16:21:01:258	wpa_supplicant	wlp0s20f0u11: WPS-CANCEL
18.12.2024 16:21:01:259	NetworkManager	<info>  [1734535261.2592] device (wlp0s20f0u11): supplicant interface state: disconnected -> scanning
18.12.2024 16:21:01:293	wpa_supplicant	wlp0s20f0u11: SME: Trying to authenticate with c8:d1:2a:15:75:a0 (SSID='Arjan' freq=5500 MHz)
18.12.2024 16:21:01:294	kernel	wlp0s20f0u11: authenticate with c8:d1:2a:15:75:a0
18.12.2024 16:21:02:012	NetworkManager	<info>  [1734535262.0123] device (wlp0s20f0u11): supplicant interface state: scanning -> authenticating
18.12.2024 16:21:02:012	wpa_supplicant	wlp0s20f0u11: Trying to associate with c8:d1:2a:15:75:a0 (SSID='Arjan' freq=5500 MHz)
18.12.2024 16:21:02:013	NetworkManager	<info>  [1734535262.0131] device (wlp0s20f0u11): supplicant interface state: authenticating -> associating
18.12.2024 16:21:02:014	kernel	wlp0s20f0u11: send auth to c8:d1:2a:15:75:a0 (try 1/3)
18.12.2024 16:21:02:014	kernel	wlp0s20f0u11: authenticated
18.12.2024 16:21:02:014	kernel	wlp0s20f0u11: associate with c8:d1:2a:15:75:a0 (try 1/3)
18.12.2024 16:21:02:017	kernel	wlp0s20f0u11: RX AssocResp from c8:d1:2a:15:75:a0 (capab=0x1911 status=0 aid=1)
18.12.2024 16:21:02:020	wpa_supplicant	wlp0s20f0u11: Associated with c8:d1:2a:15:75:a0
18.12.2024 16:21:02:020	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
18.12.2024 16:21:02:021	kernel	wlp0s20f0u11: associated
18.12.2024 16:21:02:025	NetworkManager	<info>  [1734535262.0258] device (wlp0s20f0u11): supplicant interface state: associating -> associated
18.12.2024 16:21:02:605	NetworkManager	<info>  [1734535262.6051] device (wlp0s20f0u11): supplicant interface state: associated -> 4way_handshake
18.12.2024 16:21:03:665	wpa_supplicant	wlp0s20f0u11: WPA: Key negotiation completed with c8:d1:2a:15:75:a0 [PTK=CCMP GTK=CCMP]
18.12.2024 16:21:03:665	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-CONNECTED - Connection to c8:d1:2a:15:75:a0 completed [id=0 id_str=]
18.12.2024 16:21:03:666	NetworkManager	<info>  [1734535263.6663] device (wlp0s20f0u11): supplicant interface state: 4way_handshake -> completed
18.12.2024 16:21:03:674	NetworkManager	<info>  [1734535263.6663] device (wlp0s20f0u11): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Arjan"
18.12.2024 16:21:03:674	avahi-daemon	Joining mDNS multicast group on interface wlp0s20f0u11.IPv6 with address fe80::d3af:6074:d3e:49c9.
18.12.2024 16:21:03:674	NetworkManager	<info>  [1734535263.6665] device (wlp0s20f0u11): state change: config -> ip-config (reason 'none', managed-type: 'full')
18.12.2024 16:21:03:674	avahi-daemon	New relevant interface wlp0s20f0u11.IPv6 for mDNS.
18.12.2024 16:21:03:674	NetworkManager	<info>  [1734535263.6667] dhcp4 (wlp0s20f0u11): activation: beginning transaction (timeout in 45 seconds)
18.12.2024 16:21:03:675	avahi-daemon	Registering new address record for fe80::d3af:6074:d3e:49c9 on wlp0s20f0u11.*.
18.12.2024 16:21:03:688	NetworkManager	<info>  [1734535263.6882] dhcp4 (wlp0s20f0u11): state changed new lease, address=192.168.2.143, acd pending
18.12.2024 16:21:03:711	wpa_supplicant	wlp0s20f0u11: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=780000
18.12.2024 16:21:03:838	NetworkManager	<info>  [1734535263.8379] dhcp4 (wlp0s20f0u11): state changed new lease, address=192.168.2.143
18.12.2024 16:21:03:838	NetworkManager	<info>  [1734535263.8382] policy: set 'Arjan' (wlp0s20f0u11) as default for IPv4 routing and DNS
18.12.2024 16:21:03:850	avahi-daemon	Joining mDNS multicast group on interface wlp0s20f0u11.IPv4 with address 192.168.2.143.
18.12.2024 16:21:03:851	avahi-daemon	New relevant interface wlp0s20f0u11.IPv4 for mDNS.
18.12.2024 16:21:03:851	avahi-daemon	Registering new address record for 192.168.2.143 on wlp0s20f0u11.IPv4.
18.12.2024 16:21:03:855	NetworkManager	<info>  [1734535263.8549] device (wlp0s20f0u11): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
18.12.2024 16:21:03:859	systemd	Starting Network Manager Script Dispatcher Service...
18.12.2024 16:21:03:885	systemd	Started Network Manager Script Dispatcher Service.
18.12.2024 16:21:03:886	NetworkManager	<info>  [1734535263.8868] device (wlp0s20f0u11): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
18.12.2024 16:21:03:887	NetworkManager	<info>  [1734535263.8870] device (wlp0s20f0u11): state change: secondaries -> activated (reason 'none', managed-type: 'full')
18.12.2024 16:21:03:887	NetworkManager	<info>  [1734535263.8873] manager: NetworkManager state is now CONNECTED_SITE
18.12.2024 16:21:03:887	NetworkManager	<info>  [1734535263.8877] device (wlp0s20f0u11): Activation: successful, device activated.
18.12.2024 16:21:04:945	NetworkManager	<info>  [1734535264.9458] manager: NetworkManager state is now CONNECTED_GLOBAL
18.12.2024 16:21:04:947	kdeconnectd	2024-12-18T16:21:04 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address
18.12.2024 16:21:09:240	NetworkManager	<info>  [1734535269.2409] dhcp6 (wlp0s20f0u11): activation: beginning transaction (timeout in 45 seconds)
18.12.2024 16:21:09:241	NetworkManager	<info>  [1734535269.2414] policy: set 'Arjan' (wlp0s20f0u11) as default for IPv6 routing and DNS
18.12.2024 16:21:09:253	avahi-daemon	Leaving mDNS multicast group on interface wlp0s20f0u11.IPv6 with address fe80::d3af:6074:d3e:49c9.
18.12.2024 16:21:09:254	avahi-daemon	Joining mDNS multicast group on interface wlp0s20f0u11.IPv6 with address 2a02:a443:c74f:0:cdb5:145e:571a:17c9.
18.12.2024 16:21:09:254	avahi-daemon	Registering new address record for 2a02:a443:c74f:0:cdb5:145e:571a:17c9 on wlp0s20f0u11.*.
18.12.2024 16:21:09:254	avahi-daemon	Withdrawing address record for fe80::d3af:6074:d3e:49c9 on wlp0s20f0u11.
18.12.2024 16:21:09:254	avahi-daemon	Registering new address record for fd4c:4b32:3230:0:4377:2cc6:d0db:b8f8 on wlp0s20f0u11.*.
18.12.2024 16:21:09:347	NetworkManager	<info>  [1734535269.3478] dhcp6 (wlp0s20f0u11): state changed new lease
18.12.2024 16:21:10:653	plasmashell	:3:../common/rclinit.cpp:411::Recoll 1.40.3 + Xapian 1.4.25 [/home/hans/.recoll]
18.12.2024 16:21:10:656	plasmashell	RecollRunner::match: recoll query: m
18.12.2024 16:21:10:960	plasmashell	RecollRunner::match: recoll query: mo
18.12.2024 16:21:11:370	plasmashell	RecollRunner::match: recoll query: mon
2

Hi @hans,

I don’t know if these two should run together. Completely unsure. Try dissabling one and seeing if it fixes things or not.

To disable wpa_supplicant:

sudo systemctl disable --now wpa_supplicant.service

To disable NetworkManager:

sudo systemctl disable --now NetworkManager.service

To enable them use:

sudo systemctl enable --now wpa_supplicant.service

and

sudo systemctl enable --now NetworkManager.service

…respectively.

3

Thanks. It is my understanding that Networkmanager invokes wpa_supplicant as needed. from here: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant / Newbie Corner / Arch Linux Forums
And I did not install wpa_supplicant or its .service, it “came with” Manjaro. So I am a little reluctant to disable / enable services, maybe that wrecks something somewhere else.

I came across udev-rules related to USB devices. I had created some in the past. I have removed those rules and also restarted the router which supplies the wifi. I will report back here. (If the post is not automatically closed)

4

This is accurate.
Likely wpa_supplicant.service is already disabled.
(But still started by the chain)

Have we tried unloading, reloading the module?
Maybe unload before suspend, reload after?
Or maybe a simple unload and reload after suspend?
And maybe restart NetworkManager after if needed?

sudo rmmod rtw_8822bu 
sudo modprobe rtw_8822bu

systemctl restart NetworkManager

This can also be automated through the use of systemd.

Test first and if it works then a ssytemd unit workaround can be implemented.

I might also try other kernels. 6.12 is the next LTS.

PS.

This is both an incomplete inxi and does not make use of common obfuscations.
Hence we can see your mac addresses, but we cannot see things like whether or not you have the latest firmware.

Always include -z with inxi to hide personal information.

For a full inxi use inxi -Farz.

2 Likes
5

Thanks. I have included full inxi below. If you see anything funny please let me know

❯ inxi -Farz
System:
  Kernel: 6.6.65-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=adcda0b2-d3e3-4d08-a9bd-802191d2faf3 ro nowatchdog quiet
    apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-C v: Rev X.0x
    serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
    UEFI: American Megatrends v: 3202 date: 07/10/2021
CPU:
  Info: model: Intel Core i5-9500 bits: 64 type: MCP arch: Coffee Lake
    gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF8
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 smt: <unsupported> cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4400 scaling: driver: intel_pstate
    governor: performance cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
    bogomips: 36012
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: DP-2 res: 1920x1080 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.1-arch1.3
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) device-ID: 8086:3e92 memory: 7.35 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.303 layers: 4 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 630 (CFL GT2) driver: N/A device-ID: 8086:3e92
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: Van Ooijen Technische Informatica Teensyduino MIDI
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-4:6 chip-ID: 16c0:0485 class-ID: 0300
  Device-2: BEHRINGER GmbH UMC202HD 192k driver: snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:7 chip-ID: 1397:0507
    class-ID: fe01
  Device-3: WinChipHead USB-MIDI driver: snd-usb-audio type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:8 chip-ID: 4348:552d
    class-ID: 0103
  API: ALSA v: k6.6.65-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: TP-Link Archer T3U [Realtek RTL8812BU] driver: rtw_8822bu
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:9
    chip-ID: 2357:012d class-ID: 0000 serial: <filter>
  IF: wlp0s20f0u11 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Drives:<cut>
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 29.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1892 libs: 492 tools: octopi,pamac,yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
<cut>
    122: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
Info:
  Memory: total: 16 GiB note: est. available: 15.06 GiB used: 6.47 GiB (42.9%)
  Processes: 261 Power: uptime: 14h 37m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 4 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 6.01 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 256
    default: graphical tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.36
6

Not much jumping out.

Except SWAP does seem inactive.

Have you tried unloading/loading this module?

7

Thanks. No, not yet. Thanks to the replies to my post and further investigation, my line of thinking is now: Since the number of seconds it takes to reconnect after resume from suspend, varies a lot (2 - 20 seconds), maybe it is caused by the wifi -access point. That time seems to grow gradually and a reset seems to also reset that time to 2-3 seconds (which is totally acceptable for me).

So I will further test cq. wait-and-see, before changing things. (In the past I changed for example the added-in driver (via dkms) to the in-kernel driver and v.v. which did not make a difference; so now using the in-kernel driver)

Thanks again!

8

That does, indeed, sound liked a router problem.

See if you can find or borrow one to test with…