Arch Linux

freebench

Member

Registered: 2020-06-14

Posts: 41

Non responsive after suspend

Hi

Lenovo ThinkPad T14s Gen 3

Sometimes I find a laptop non responsive. It does not happen when it's in use, but rather when I leave it for some time, then get back and find it non responsive. It's state - monitor turned off; all the led lights turned on; it does not respond to any input except force turn off with the power button press and hold.

I've fetched the journal log - see below. I assume some hardware fails on suspend.
The suspend works when I do it manually.

lshw -C network

  *-network
       description: Wireless interface
       product: QCNFA765 Wireless Network Adapter
       vendor: Qualcomm Technologies, Inc
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlan2
       version: 01
       serial: 04:7b:cb:b7:ca:88
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath11k_pci driverversion=6.13.5-arch1-1 firmware=N/A ip=192.168.1.147 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:92 memory:98000000-981fffff
  *-network
       description: Ethernet interface
       product: Lenovo Mini Dock
       physical id: d
       bus info: usb@10:1.1
       logical name: enp52s0f4u1u1
       serial: 60:7d:09:6a:09:e0
       size: 100Mbit/s
       capacity: 1Gbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.12.13 duplex=full firmware=rtl8153b-2 v2 04/27/23 ip=192.168.1.109 link=yes multicast=yes port=MII speed=100Mbit/s

journalctl --since="2025-03-14"

Mar 15 00:15:48 arch gsd-power[3035]: gsd_power_backlight_percentage_to_abs: assertion 'value <= 100' failed
Mar 15 00:15:50 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:16:50 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:17:36 arch warp-svc[1487]: 2025-03-14T22:17:36.845Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:17:36 arch warp-svc[1487]: 2025-03-14T22:17:36.846Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:17:50 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:18:42 arch warp-svc[1487]: 2025-03-14T22:18:42.062Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/dex_results, DexUploadEndpoint { ac>
Mar 15 00:18:50 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:19:36 arch warp-svc[1487]: 2025-03-14T22:19:36.845Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:19:36 arch warp-svc[1487]: 2025-03-14T22:19:36.846Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:19:50 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:20:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:21:36 arch warp-svc[1487]: 2025-03-14T22:21:36.846Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:21:36 arch warp-svc[1487]: 2025-03-14T22:21:36.846Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:21:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:22:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:23:36 arch warp-svc[1487]: 2025-03-14T22:23:36.847Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:23:36 arch warp-svc[1487]: 2025-03-14T22:23:36.847Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:23:41 arch warp-svc[1487]: 2025-03-14T22:23:41.886Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/dex_results, DexUploadEndpoint { ac>
Mar 15 00:23:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:24:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:25:36 arch warp-svc[1487]: 2025-03-14T22:25:36.846Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:25:36 arch warp-svc[1487]: 2025-03-14T22:25:36.846Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:25:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:26:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:27:36 arch warp-svc[1487]: 2025-03-14T22:27:36.846Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:27:36 arch warp-svc[1487]: 2025-03-14T22:27:36.855Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:27:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:28:41 arch warp-svc[1487]: 2025-03-14T22:28:41.882Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/dex_results, DexUploadEndpoint { ac>
Mar 15 00:28:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:29:36 arch warp-svc[1487]: 2025-03-14T22:29:36.846Z DEBUG main_loop: warp_settings::raw_settings: gateway_id=13d37a7873b9ac730b0f82e042dc5257 Using gateway ID
Mar 15 00:29:36 arch warp-svc[1487]: 2025-03-14T22:29:36.846Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/devicestate, CombinedDeviceSettings>
Mar 15 00:29:51 arch bluetoothd[1495]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 15 00:30:48 arch systemd-logind[1483]: The system will suspend now!
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2373] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2377] manager: NetworkManager state is now ASLEEP
Mar 15 00:30:48 arch chromium.desktop[85937]: [85937:85959:0315/003048.238423:ERROR:connection_factory_impl.cc(483)] ConnectionHandler failed with net error: -2
Mar 15 00:30:48 arch systemd[1]: Reached target Sleep.
Mar 15 00:30:48 arch systemd[1]: Starting System Suspend...
Mar 15 00:30:48 arch systemd[1]: session-3.scope: Unit now frozen-by-parent.
Mar 15 00:30:48 arch systemd[1]: user@1000.service: Unit now frozen-by-parent.
Mar 15 00:30:48 arch systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Mar 15 00:30:48 arch systemd[1]: user.slice: Unit now frozen.
Mar 15 00:30:48 arch systemd-sleep[145060]: Successfully froze unit 'user.slice'.
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2919] caught SIGTERM, shutting down normally.
Mar 15 00:30:48 arch systemd[1]: Stopping Network Manager...
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2932] dhcp4 (enp52s0f4u1u1): canceled DHCP transaction
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2932] dhcp4 (enp52s0f4u1u1): activation: beginning transaction (timeout in 45 seconds)
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.2933] dhcp4 (enp52s0f4u1u1): state changed no lease
Mar 15 00:30:48 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 15 00:30:48 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 15 00:30:48 arch NetworkManager[130262]: <info>  [1741991448.3329] exiting (success)
Mar 15 00:30:48 arch systemd[1]: NetworkManager.service: Deactivated successfully.
Mar 15 00:30:48 arch systemd[1]: Stopped Network Manager.
Mar 15 00:30:48 arch systemd-sleep[145060]: Performing sleep operation 'suspend'...
-- Boot c7bb5725dd9e44799fddadb666598491 --
Mar 15 09:59:48 arch kernel: Linux version 6.13.5-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Thu, 27 Feb 2025 18:09:44 +0000

Last edited by freebench (2025-03-22 17:30:16)

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

Mar 15 00:30:48 arch systemd-sleep[145060]: Performing sleep operation 'suspend'...
-- Boot c7bb5725dd9e44799fddadb666598491 --
Mar 15 09:59:48 arch kernel: Linux version 6.13.5-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Thu, 27 Feb 2025 18:09:44 +0000

Once you hold the power button for a hard reboot, the journal cannot be preserved.
Try to use https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

At lease post the journal after a successful suspend so we know what the system looks like and what's supposed to happen, eg.

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

for the current boot.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

manual suspend/wakeup, successfull

Mar 16 12:54:02 arch baloo_file_extractor[49775]: kf.idletime: Could not find any system poller plugin
Mar 16 12:54:02 arch baloo_file_extractor[49775]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mar 16 12:54:02 arch baloo_file_extractor[49775]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mar 16 12:54:06 arch systemd-logind[1726]: Power key pressed short.
Mar 16 12:54:06 arch systemd-logind[1726]: The system will suspend now!
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4006] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4012] device (/net/connman/iwd/7): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4015] manager: NetworkManager state is now ASLEEP
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4017] device (enp52s0f4u1u1): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4026] device (wlan7): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Mar 16 12:54:06 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 16 12:54:06 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 16 12:54:06 arch iwd[1722]: event: state, old: connected, new: disconnecting
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4276] device (enp52s0f4u1u1): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.428Z DEBUG warp::warp_service::network_change: Routes changed:
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.251;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.252;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.22;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::2;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::1:3;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::fb;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::1:ffe2:da88;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::16;
Mar 16 12:54:06 arch kernel: wlan7: deauthenticating from 60:e3:27:26:df:4a by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4291] dhcp4 (enp52s0f4u1u1): canceled DHCP transaction
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4292] dhcp4 (enp52s0f4u1u1): activation: beginning transaction (timeout in 45 seconds)
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4292] dhcp4 (enp52s0f4u1u1): state changed no lease
Mar 16 12:54:06 arch systemd-resolved[662]: enp52s0f4u1u1: Bus client set default route setting: no
Mar 16 12:54:06 arch dnsmasq[2066]: reading /etc/resolv.conf
Mar 16 12:54:06 arch dnsmasq[2066]: using nameserver 192.168.1.1#53
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4608] device (enp52s0f4u1u1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Mar 16 12:54:06 arch iwd[1722]: event: state, old: disconnecting, new: disconnected
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.493Z DEBUG warp::warp_service::network_change: Routes changed:
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::2;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::fb;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::1:3;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::1:ffaa:d149;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::16;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 192.168.1.255;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.251;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.252;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 192.168.1.1;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.22;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.22;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::16;
Mar 16 12:54:06 arch systemd-resolved[662]: enp52s0f4u1u1: Bus client reset DNS server list.
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4948] device (wlan7): new IWD device state is disconnecting
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4949] device (wlan7): new IWD device state is disconnected
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4952] device (wlan7): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4954] dhcp4 (wlan7): canceled DHCP transaction
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4955] dhcp4 (wlan7): activation: beginning transaction (timeout in 45 seconds)
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.4955] dhcp4 (wlan7): state changed no lease
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.497Z DEBUG warp::warp_service::network_change: Routes changed:
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: ff02::16;
Mar 16 12:54:06 arch warp-svc[1730]: DelNeighbour; Destination: 224.0.0.22;
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.499Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="network_changed"
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.499Z DEBUG main_loop: warp::warp_service: Network change detected new_info=DNS servers:;   192.168.1.1:53;
Mar 16 12:54:06 arch warp-svc[1730]:  old_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet, wlan7; 192.168.1.147; WiFi: wify]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.499Z DEBUG main_loop: warp::warp_service: Reconnecting on network change
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z  INFO firewall: Firewall stopped
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=DNS servers:;   192.168.1.1:53;
Mar 16 12:54:06 arch warp-svc[1730]:  power_state=Some(Wakeup) disconnect_reason=None
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="status_change"
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z  INFO main_loop: warp::warp_service: WARP status: Unable(NoNetwork)
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Unable(NoNetwork)
Mar 16 12:54:06 arch warp-svc[1730]: 2025-03-16T10:54:06.500Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Unable(NoNetwork)
Mar 16 12:54:06 arch systemd-resolved[662]: wlan7: Bus client set default route setting: no
Mar 16 12:54:06 arch systemd-resolved[662]: wlan7: Bus client reset DNS server list.
Mar 16 12:54:06 arch dnsmasq[2066]: no servers found in /etc/resolv.conf, will retry
Mar 16 12:54:06 arch NetworkManager[49142]: <info>  [1742122446.5412] device (wlan7): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Mar 16 12:54:06 arch xpad[3413]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Mar 16 12:54:06 arch redshift-gtk[3445]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Mar 16 12:54:07 arch systemd[1]: Reached target Sleep.
Mar 16 12:54:07 arch systemd[1]: Starting System Suspend...
Mar 16 12:54:07 arch systemd[1]: session-3.scope: Unit now frozen-by-parent.
Mar 16 12:54:07 arch systemd[1]: user@1000.service: Unit now frozen-by-parent.
Mar 16 12:54:07 arch systemd[1]: user.slice: Unit now frozen.
Mar 16 12:54:07 arch systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Mar 16 12:54:07 arch systemd-sleep[49817]: Successfully froze unit 'user.slice'.
Mar 16 12:54:07 arch NetworkManager[49142]: <info>  [1742122447.3454] caught SIGTERM, shutting down normally.
Mar 16 12:54:07 arch systemd[1]: Stopping Network Manager...
Mar 16 12:54:07 arch NetworkManager[49142]: <info>  [1742122447.3953] exiting (success)
Mar 16 12:54:07 arch systemd[1]: NetworkManager.service: Deactivated successfully.
Mar 16 12:54:07 arch systemd[1]: Stopped Network Manager.
Mar 16 12:54:07 arch iwd[1722]: Removing scan context for wdev 700000002
Mar 16 12:54:07 arch iwd[1722]: Removing scan context for wdev 700000003
Mar 16 12:54:07 arch systemd[1]: Starting Load/Save RF Kill Switch Status...
Mar 16 12:54:07 arch warp-svc[1730]: 2025-03-16T10:54:07.541Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="network_changed"
Mar 16 12:54:07 arch warp-svc[1730]: 2025-03-16T10:54:07.541Z DEBUG main_loop: warp::warp_service: Network change detected new_info=
Mar 16 12:54:07 arch warp-svc[1730]:  old_info=DNS servers:;   192.168.1.1:53;
Mar 16 12:54:07 arch systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 16 12:54:07 arch systemd-sleep[49817]: Performing sleep operation 'suspend'...
Mar 16 12:54:07 arch kernel: PM: suspend entry (s2idle)
Mar 16 12:54:07 arch kernel: Filesystems sync: 0.024 seconds
Mar 16 12:54:15 arch kernel: Freezing user space processes
Mar 16 12:54:15 arch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Mar 16 12:54:15 arch kernel: OOM killer disabled.
Mar 16 12:54:15 arch kernel: Freezing remaining freezable tasks
Mar 16 12:54:15 arch kernel: usb 1-3-port2: attempt power cycle
Mar 16 12:54:15 arch kernel: usb 1-3-port2: unable to enumerate USB device
Mar 16 12:54:15 arch kernel: Freezing remaining freezable tasks completed (elapsed 3.636 seconds)
Mar 16 12:54:15 arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 16 12:54:15 arch kernel: ACPI: EC: interrupt blocked
Mar 16 12:54:15 arch kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP5], AE_NOT_FOUND (20240827/psargs-332)
Mar 16 12:54:15 arch kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mar 16 12:54:15 arch kernel: ACPI: EC: interrupt unblocked
Mar 16 12:54:15 arch kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F43FC00000).
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: SMU is resuming...
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: SMU is resumed successfully!
Mar 16 12:54:15 arch kernel: nvme nvme0: D3 entry latency set to 10 seconds
Mar 16 12:54:15 arch kernel: nvme nvme0: 16/0/0 default/read/poll queues
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Mar 16 12:54:15 arch kernel: amdgpu 0000:33:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Mar 16 12:54:15 arch kernel: OOM killer enabled.
Mar 16 12:54:15 arch kernel: Restarting tasks ... done.
Mar 16 12:54:15 arch kernel: random: crng reseeded on system resumption
Mar 16 12:54:15 arch rtkit-daemon[2094]: The canary thread is apparently starving. Taking action.
Mar 16 12:54:15 arch systemd-resolved[662]: Clock change detected. Flushing caches.
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.057Z  WARN watchdog: warp::watchdog: Watchdog reports hung daemon watchdog_name="main loop" hang_count=7 hang_tick=1
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.058Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="sleep_monitor"
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.058Z DEBUG main_loop: warp::warp_service: Power status: Wakeup
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.058Z DEBUG main_loop: warp::warp_service: Restarting posture schedule tasks on power event
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.058Z  INFO dex: Restarting dex tests on power notification
Mar 16 12:54:15 arch rtkit-daemon[2094]: Demoting known real-time threads.
Mar 16 12:54:15 arch rtkit-daemon[2094]: Demoted 0 threads.
Mar 16 12:54:15 arch systemd-sleep[49817]: System returned from sleep operation 'suspend'.
Mar 16 12:54:15 arch bluetoothd[1720]: Controller resume with wake event 0x0
Mar 16 12:54:15 arch kernel: PM: suspend exit
Mar 16 12:54:15 arch systemd-sleep[49999]: enabled
Mar 16 12:54:15 arch systemd[1]: Starting Network Manager...
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1176] NetworkManager (version 1.52.0-1) is starting... (after a restart, boot:c7bb5725-dd9e-4479-9fdd-adb666598491)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1177] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/20-connectivity.conf, /etc/NetworkManager/conf.d/wifi_backend.conf, /var/lib/NetworkManager/NetworkManager-intern.conf
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1225] manager[0x61ce13546d00]: monitoring kernel firmware directory '/lib/firmware'.
Mar 16 12:54:15 arch systemd[1]: Starting Hostname Service...
Mar 16 12:54:15 arch systemd[1]: Started Hostname Service.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1990] hostname: hostname: using hostnamed
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1991] hostname: static hostname changed from (none) to "arch"
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.1994] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2013] manager[0x61ce13546d00]: rfkill: Wi-Fi hardware radio set enabled
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2013] manager[0x61ce13546d00]: rfkill: WWAN hardware radio set enabled
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2028] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-ovs.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2104] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-team.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2107] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-wifi.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2118] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-wwan.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2120] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-adsl.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2122] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.52.0-1/libnm-device-plugin-bluetooth.so)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2124] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2125] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2125] manager: Networking is enabled by state file
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2127] settings: Loaded settings plugin: keyfile (internal)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2187] dhcp: init: Using DHCP client 'internal'
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2189] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2191] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2194] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2198] device (lo): Activation: starting connection 'lo' (da1eae1d-ead8-4be2-99a9-cb7ab45f768b)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2202] manager: (br-f105d2eb7215): new Bridge device (/org/freedesktop/NetworkManager/Devices/2)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2210] device (br-f105d2eb7215): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2213] device (br-f105d2eb7215): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2217] device (br-f105d2eb7215): Activation: starting connection 'br-f105d2eb7215' (66a691b8-be35-46bb-9efe-86af632c386c)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2221] manager: (br-f494eab2b81c): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2229] device (br-f494eab2b81c): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2232] device (br-f494eab2b81c): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2235] device (br-f494eab2b81c): Activation: starting connection 'br-f494eab2b81c' (dcc5b893-68bb-447a-a5d4-0d79e1a760d7)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2239] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2247] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2250] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2254] device (docker0): Activation: starting connection 'docker0' (f280edd1-2711-4246-aff7-1bf27db527ec)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2265] manager: (enp52s0f4u1u1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2268] device (enp52s0f4u1u1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Mar 16 12:54:15 arch warp-svc[1730]: 2025-03-16T10:54:15.227Z DEBUG warp::warp_service::network_change: Routes changed:
Mar 16 12:54:15 arch warp-svc[1730]: DelNeighbour; Destination: ff02::16;
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2317] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/6)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2325] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2328] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2331] device (virbr0): Activation: starting connection 'virbr0' (6ccc5d21-ff90-490d-87f9-f471114bf650)
Mar 16 12:54:15 arch systemd[1]: Started Network Manager.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2337] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2345] ovsdb: disconnected from ovsdb
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2346] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch systemd-sleep[50124]: /usr/lib/systemd/system-sleep/ath11k_pci: line 14: start_systemd_network: command not found
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2349] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2350] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2351] device (br-f105d2eb7215): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2352] device (br-f105d2eb7215): state change: prepare -> config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2353] device (br-f105d2eb7215): state change: config -> ip-config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2354] device (br-f494eab2b81c): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2355] device (br-f494eab2b81c): state change: prepare -> config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2356] device (br-f494eab2b81c): state change: config -> ip-config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2357] device (docker0): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2358] device (docker0): state change: prepare -> config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2359] device (docker0): state change: config -> ip-config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2361] device (virbr0): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2362] device (virbr0): state change: prepare -> config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2363] device (virbr0): state change: config -> ip-config (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <warn>  [1742122455.2364] power-monitor-sd: inhibit: failed (GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2366] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2369] device (br-f105d2eb7215): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2372] device (br-f494eab2b81c): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2375] device (docker0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2380] device (virbr0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2388] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2389] device (br-f105d2eb7215): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2390] device (br-f494eab2b81c): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2391] device (docker0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2393] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2396] device (lo): Activation: successful, device activated.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2399] device (br-f105d2eb7215): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2401] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2402] device (br-f105d2eb7215): Activation: successful, device activated.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2406] device (br-f494eab2b81c): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2409] device (br-f494eab2b81c): Activation: successful, device activated.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2411] device (docker0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2413] device (docker0): Activation: successful, device activated.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2416] device (virbr0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2419] device (virbr0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.2421] device (virbr0): Activation: successful, device activated.
Mar 16 12:54:15 arch kernel: ath11k_pci 0000:01:00.0: BAR 0 [mem 0x98000000-0x981fffff 64bit]: assigned
Mar 16 12:54:16 arch kernel: ath11k_pci 0000:01:00.0: MSI vectors: 32
Mar 16 12:54:16 arch kernel: ath11k_pci 0000:01:00.0: wcn6855 hw2.1
Mar 16 12:54:16 arch kernel: r8152 10-1.1:1.0 enp52s0f4u1u1: carrier on
Mar 16 12:54:16 arch kernel: mhi mhi0: Requested to power ON
Mar 16 12:54:16 arch kernel: mhi mhi0: Power on setup success
Mar 16 12:54:16 arch kernel: mhi mhi0: Wait for device to enter SBL or Mission mode
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.781Z DEBUG warp::warp_service::network_change: Routes changed:
Mar 16 12:54:16 arch warp-svc[1730]: NewNeighbour; Destination: 192.168.1.1;
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="network_changed"
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service: Network change detected new_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:16 arch warp-svc[1730]:  old_info=
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service: Reconnecting on network change
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z  INFO firewall: Firewall stopped
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:16 arch warp-svc[1730]:  power_state=Some(Wakeup) disconnect_reason=None
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="status_change"
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z  INFO main_loop: warp::warp_service: WARP status: Disconnected(Manual)
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Disconnected(Manual)
Mar 16 12:54:16 arch warp-svc[1730]: 2025-03-16T10:54:15.786Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Disconnected(Manual)
Mar 16 12:54:15 arch dnsmasq[2066]: reading /etc/resolv.conf
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3747] device (enp52s0f4u1u1): carrier: link connected
Mar 16 12:54:15 arch dnsmasq[2066]: using nameserver 192.168.1.1#53
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3758] device (enp52s0f4u1u1): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3766] policy: auto-activating connection 'Wired connection 1' (ab975232-19ec-3016-bb35-c469b6c67c35)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3770] device (enp52s0f4u1u1): Activation: starting connection 'Wired connection 1' (ab975232-19ec-3016-bb35-c469b6c67c35)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3771] device (enp52s0f4u1u1): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3773] manager: NetworkManager state is now CONNECTING
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3773] device (enp52s0f4u1u1): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3778] device (enp52s0f4u1u1): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.3781] dhcp4 (enp52s0f4u1u1): activation: beginning transaction (timeout in 45 seconds)
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.4409] dhcp4 (enp52s0f4u1u1): state changed new lease, address=192.168.1.109, acd pending
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.6352] dhcp4 (enp52s0f4u1u1): state changed new lease, address=192.168.1.109
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.6366] policy: set 'Wired connection 1' (enp52s0f4u1u1) as default for IPv4 routing and DNS
Mar 16 12:54:15 arch systemd-resolved[662]: enp52s0f4u1u1: Bus client set default route setting: yes
Mar 16 12:54:15 arch systemd-resolved[662]: enp52s0f4u1u1: Bus client set DNS server list to: 192.168.1.1
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7093] device (enp52s0f4u1u1): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7113] device (enp52s0f4u1u1): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7114] device (enp52s0f4u1u1): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7117] manager: NetworkManager state is now CONNECTED_SITE
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7118] device (enp52s0f4u1u1): Activation: successful, device activated.
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7121] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 16 12:54:15 arch NetworkManager[50004]: <info>  [1742122455.7123] manager: startup complete
Mar 16 12:54:16 arch boltd[1721]: probing: started [1000]
Mar 16 12:54:16 arch systemd[1]: user.slice: Unit now thawed.
Mar 16 12:54:16 arch systemd[1]: user-1000.slice: Unit now thawed.
Mar 16 12:54:16 arch systemd[1]: user@1000.service: Unit now thawed.
Mar 16 12:54:16 arch systemd[1]: session-3.scope: Unit now thawed.
Mar 16 12:54:16 arch systemd-sleep[49817]: Successfully thawed unit 'user.slice'.
Mar 16 12:54:16 arch systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 16 12:54:16 arch systemd[1]: Finished System Suspend.
Mar 16 12:54:16 arch systemd[1]: systemd-suspend.service: Consumed 1.176s CPU time, 9.2M memory peak.
Mar 16 12:54:16 arch systemd[1]: Stopped target Sleep.
Mar 16 12:54:16 arch systemd[1]: Reached target Suspend.
Mar 16 12:54:16 arch systemd-logind[1726]: Operation 'suspend' finished.
Mar 16 12:54:16 arch systemd[1]: Stopped target Suspend.
Mar 16 12:54:16 arch systemd-resolved[662]: Closing all remaining TCP connections.
Mar 16 12:54:16 arch systemd-resolved[662]: Resetting learnt feature levels on all servers.
Mar 16 12:54:16 arch kernel: ath11k_pci 0000:01:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211
Mar 16 12:54:16 arch kernel: ath11k_pci 0000:01:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
Mar 16 12:54:16 arch bluetoothd[1720]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for DC:CC:E6:35:91:2F: Protocol not available
Mar 16 12:54:16 arch xdg-desktop-por[3742]: Monitor 'Built-in display' has no configuration which is-current!
Mar 16 12:54:16 arch xdg-desktop-por[3742]: Monitor 'Built-in display' has no configuration which is-current!
Mar 16 12:54:16 arch xdg-desktop-por[3742]: Monitor 'Built-in display' has no configuration which is-current!
Mar 16 12:54:16 arch xdg-desktop-por[3742]: Monitor 'Built-in display' has no configuration which is-current!
Mar 16 12:54:16 arch iwd[1722]: Wiphy: 8, Name: phy8
Mar 16 12:54:16 arch iwd[1722]:         Permanent Address: 04:7b:cb:b7:ca:88
Mar 16 12:54:16 arch iwd[1722]:         2.4GHz Band:
Mar 16 12:54:16 arch iwd[1722]:                 Bitrates (non-HT):
Mar 16 12:54:16 arch iwd[1722]:                          1.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          2.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          5.5 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         11.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          6.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          9.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         12.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         18.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         24.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         36.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         48.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         54.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                 HT Capabilities:
Mar 16 12:54:16 arch iwd[1722]:                         HT40
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 20Mhz
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 40Mhz
Mar 16 12:54:16 arch iwd[1722]:                 HT RX MCS indexes:
Mar 16 12:54:16 arch iwd[1722]:                         0-15
Mar 16 12:54:16 arch iwd[1722]:                 HE Capabilities
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types:
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: ap
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: station
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:         5GHz Band:
Mar 16 12:54:16 arch iwd[1722]:                 Bitrates (non-HT):
Mar 16 12:54:16 arch iwd[1722]:                          6.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          9.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         12.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         18.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         24.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         36.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         48.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         54.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                 HT Capabilities:
Mar 16 12:54:16 arch iwd[1722]:                         HT40
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 20Mhz
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 40Mhz
Mar 16 12:54:16 arch iwd[1722]:                 HT RX MCS indexes:
Mar 16 12:54:16 arch iwd[1722]:                         0-15
Mar 16 12:54:16 arch iwd[1722]:                 VHT Capabilities:
Mar 16 12:54:16 arch iwd[1722]:                         160 Mhz operation
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 80Mhz
Mar 16 12:54:16 arch iwd[1722]:                         Short GI for 160 and 80 + 80 Mhz
Mar 16 12:54:16 arch iwd[1722]:                         Max RX MCS: 0-9 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max TX MCS: 0-9 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                 HE Capabilities
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types:
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: ap
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: station
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:         6GHz Band:
Mar 16 12:54:16 arch iwd[1722]:                 Bitrates (non-HT):
Mar 16 12:54:16 arch iwd[1722]:                          6.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                          9.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         12.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         18.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         24.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         36.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         48.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                         54.0 Mbps
Mar 16 12:54:16 arch iwd[1722]:                 HE Capabilities
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types:
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: ap
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Interface Types: station
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Mar 16 12:54:16 arch iwd[1722]:         Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256
Mar 16 12:54:16 arch iwd[1722]:                  GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
Mar 16 12:54:16 arch iwd[1722]:                  TKIP
Mar 16 12:54:16 arch iwd[1722]:         Supported iftypes: station ap p2p-client p2p-go p2p-device
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5269] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/7)
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5282] rfkill11: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:01:00.0/ieee80211/phy8/rfkill11) (driver ath11k_pci)
Mar 16 12:54:16 arch iwd[1722]: udev interface=wlan0 ifindex=23
Mar 16 12:54:16 arch iwd[1722]: event: state, old: disconnected, new: autoconnect_quick
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5863] Wi-Fi P2P device added on phy8
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5865] manager: (/net/connman/iwd/8): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/8)
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5866] device (/net/connman/iwd/8): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Mar 16 12:54:16 arch iwd[1722]: udev interface=wlan8 ifindex=24
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5947] manager: (wlan8): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/9)
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5957] device (wlan8): new IWD device state is disconnected
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5959] device (wlan8): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.5967] device (wlan8): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Mar 16 12:54:16 arch NetworkManager[50004]: <info>  [1742122456.6554] device (/net/connman/iwd/8): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Mar 16 12:54:16 arch kernel: usb 1-3-port2: attempt power cycle
Mar 16 12:54:17 arch iwd[1722]: invalid HE capabilities for d4:01:c3:12:51:2a
Mar 16 12:54:17 arch iwd[1722]: event: connect-info, ssid: wify, bss: 60:e3:27:26:df:4a, signal: -48, load: 0/255
Mar 16 12:54:17 arch iwd[1722]: event: state, old: autoconnect_quick, new: connecting (auto)
Mar 16 12:54:17 arch kernel: wlan8: authenticate with 60:e3:27:26:df:4a (local address=04:7b:cb:b7:ca:88)
Mar 16 12:54:17 arch kernel: wlan8: send auth to 60:e3:27:26:df:4a (try 1/3)
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.2470] device (wlan8): new IWD device state is connecting
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.2475] device (wlan8): Activation: starting connection 'wify' (81a9dd41-bffe-49c2-bb74-a94d9d741559)
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.2476] device (wlan8): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.2479] device (wlan8): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch kernel: wlan8: authenticated
Mar 16 12:54:17 arch kernel: wlan8: associate with 60:e3:27:26:df:4a (try 1/3)
Mar 16 12:54:17 arch kernel: wlan8: RX AssocResp from 60:e3:27:26:df:4a (capab=0x411 status=0 aid=4)
Mar 16 12:54:17 arch kernel: wlan8: associated
Mar 16 12:54:17 arch iwd[1722]: event: state, old: connecting (auto), new: connected
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.3296] device (wlan8): new IWD device state is connected
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.3298] device (wlan8): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.3309] dhcp4 (wlan8): activation: beginning transaction (timeout in 45 seconds)
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.3971] dhcp4 (wlan8): state changed new lease, address=192.168.1.147, acd pending
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.5147] dhcp4 (wlan8): state changed new lease, address=192.168.1.147
Mar 16 12:54:17 arch systemd-resolved[662]: wlan8: Bus client set default route setting: yes
Mar 16 12:54:17 arch systemd-resolved[662]: wlan8: Bus client set DNS server list to: 192.168.1.1
Mar 16 12:54:17 arch dnsmasq[2066]: reading /etc/resolv.conf
Mar 16 12:54:17 arch dnsmasq[2066]: using nameserver 192.168.1.1#53
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.5960] device (wlan8): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.5972] device (wlan8): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.5973] device (wlan8): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Mar 16 12:54:17 arch NetworkManager[50004]: <info>  [1742122457.5976] device (wlan8): Activation: successful, device activated.
Mar 16 12:54:18 arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.548Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="network_changed"
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.548Z DEBUG main_loop: warp::warp_service: Network change detected new_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet, wlan8; 192.168.1.147; WiFi: wify]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:18 arch warp-svc[1730]:  old_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.549Z DEBUG main_loop: warp::warp_service: Reconnecting on network change
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.549Z  INFO firewall: Firewall stopped
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.549Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [enp52s0f4u1u1; 192.168.1.109; Ethernet, wlan8; 192.168.1.147; WiFi: wify]; DNS servers:;   192.168.1.1:53;
Mar 16 12:54:18 arch warp-svc[1730]:  power_state=Some(Wakeup) disconnect_reason=None
Mar 16 12:54:18 arch warp-svc[1730]: 2025-03-16T10:54:18.549Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
Mar 16 12:54:18 arch kernel: usb 1-3-port2: unable to enumerate USB device
Mar 16 12:54:19 arch boltd[1721]: probing: timeout, done: [2546109] (2000000)
Mar 16 12:54:21 arch gdm-password][50241]: gkr-pam: unlocked login keyring
Mar 16 12:54:21 arch NetworkManager[50004]: <info>  [1742122461.3354] agent-manager: agent[9f083aa345afe9b4,:1.73/org.gnome.Shell.NetworkAgent/1000]: agent registered
Mar 16 12:54:21 arch appindicatorsupport@rgcjonas.gmail.com[3147]: Using Brute-force mode for StatusNotifierItem :1.377@/org/blueman/sni
Mar 16 12:54:21 arch systemd[1]: systemd-rfkill.service: Deactivated successfully.
Mar 16 12:54:30 arch warp-svc[1730]: 2025-03-16T10:54:30.059Z  INFO dex: Launching DEX tasks task_list=[DexTestDefinition { test_id: 982fc0c5-5f8b-4af4-9227-5592cb8d63f6, name: "Cloudflare Status", interval: 300, enabled: true, data: Http { method: GET, host: https://www.cloudflarestatus.com/ }, updated: 2024-09-09 23:39:56.0 +00:00:00, created: 2024-03-11 13:45:59.0 +00:00:00 }]
Mar 16 12:54:30 arch warp-svc[1730]: 2025-03-16T10:54:30.059Z  INFO dex: Spawning DEX task test_parameters=DexTestParameters { interval: 300, offset: 0 } task_id=982fc0c5-5f8b-4af4-9227-5592cb8d63f6
Mar 16 12:54:33 arch warp-svc[1730]: 2025-03-16T10:54:33.712Z DEBUG warp_api::api_client: Method: Post, Path: v0/accounts/13d37a7873b9ac730b0f82e042dc5257/reg/79780bac-74d1-11ee-af08-822ae15d94a9/dex_results, DexUploadEndpoint { account_id: AccountId(13d37a78-73b9-ac73-0b0f-82e042dc5257), reg_id: TeamsRegistrationId(79780bac-74d1-11ee-af08-822ae15d94a9), tests: [DexTest { test_id: 982fc0c5-5f8b-4af4-9227-5592cb8d63f6, data: Http(HttpGet { request: HttpGetRequest { url: https://www.cloudflarestatus.com/, method: "GET", client_ip: Some(192.168.1.109) }, response: Response { client_ip: Some(192.168.1.109), status_code: 200, server_ip: 65.9.95.52, header_bytes: 2419, body_bytes: 475316, domain_lookup_start: ElapsedMillis(0ns), domain_lookup_end: ElapsedMillis(2ms), connect_start: ElapsedMillis(2ms), connect_end: ElapsedMillis(25ms), secure_connection_start: ElapsedMillis(25ms), request_start: ElapsedMillis(91ms), response_start: ElapsedMillis(152ms), response_end: ElapsedMillis(244ms) }, time_start: 2025-03-16 10:54:33.463636528 +00:00:00, time_end: 2025-03-16 10:54:33.708162679 +00:00:00 }), tunnel: false }] }
Mar 16 12:54:45 arch systemd[1]: systemd-hostnamed.service: Deactivated successfully.

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

AMD, nvme & systemd freezes the session, fyi:
https://wiki.archlinux.org/title/Solid_ … leshooting
https://bbs.archlinux.org/viewtopic.php?id=296954

Sidebar: Why are you running resolved and dnsmasq at the same time?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

Applied the override fix for systemd for now as the thread proposes.
This started a while ago, probably the same time as the thread started > 6 month ago. I simply switched to hibernation 

Could not find the relevant journal records for nvme causing the suspend problem as per the wiki sample ...

$ systemctl status dnsmasq
○ dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:dnsmasq(8)

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

The problem w/ any journal traces is the thing w/ the power button, but I was also only floating ideas of potential causes (since we've no data to go by)
Let's see whether it's systemd…

---
dnsmasq is running in your journal segment - regardless of how it's started

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

atwalter

Member

Registered: 2020-05-01

Posts: 5

Re: Non responsive after suspend

I've also been running into this problem, for what is probably 6mo-1yr at this point. For what it's worth it seems to be worse under Wayland, but I have very little confidence that the display server is actually relevant.

I have a Thinkpad T14 Gen 3 AMD.

Output of  lshw -C network:

  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: enp1s0f0
       version: 0e
       serial: 9c:2d:cd:62:30:df
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.13.7-arch1-1 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:67 ioport:2000(size=256) memory:80a04000-80a04fff memory:80a00000-80a03fff
  *-network
       description: Wireless interface
       product: QCNFA765 Wireless Network Adapter
       vendor: Qualcomm Technologies, Inc
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlan0
       version: 01
       serial: 04:7b:cb:b4:5e:ca
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath11k_pci driverversion=6.13.7-arch1-1 firmware=N/A ip=192.168.0.178 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:72 memory:80000000-801fffff

I have tried two different approaches for mitigating the issue (in terms of turning off Wi-Fi prior to sleep). The first is through systemd sleep hooks that rmmod/modprobe ath11k_pci upon suspend/resume (this is described on the wiki). This doesn't seem to work well, and I consistently get hangs after resuming from a long sleep when using it. The second involves adding a pre-down hook to NetworkManager that runs rfkill block wifi prior to sleep, and then uses the appropriate systemd sleep hook to reenable on resume. This is described on the longsleep/t14g3amd-linux GitHub repo. Using the longsleep approach seems more effective at mitigating the issue, but it does still occur.

I do (very rarely) see identical freezes outside of sleep/resume. I am suspicious of the NVMe issue that seth linked earlier. I previously had similar freezing issues when I swapped out my NVMe drive for another of the same model (Samsung 980 1TB) but it seemed to improve when I swapped back to the original one. I will attempt the APST fix that seth linked earlier in this thread and see if that helps.

I'll also try to use SysRq magic to glean more information from the system while it is hanging, but given I can't switch to a virtual console during a hang (to see kernel messages) I think the best I can hope for is to sync and see if anything more is retained in the journal.

Last edited by atwalter (2025-03-24 14:13:03)

atwalter

Member

Registered: 2020-05-01

Posts: 5

Re: Non responsive after suspend

I experienced a freeze again when I resumed my laptop from suspend this morning. I wasn't able to do anything with SysRq magic - even REISUB didn't restart the machine. I know that SysRq magic is enabled, as I can see the output of commands in the journal when I run them during regular operation.

I have now added the following to my kernel parameters, and will see if that changes anything:

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

atwalter

Member

Registered: 2020-05-01

Posts: 5

Re: Non responsive after suspend

The kernel parameters from my last post did not resolve the issue, and I consistently experience it after an extended suspend.

I still can't get SysRq magic to do anything during a freeze, so I suspect the kernel is totally locked up. This is supported by the fact that the fans spin up during a freeze, just as they do when the system is under a period of increased CPU utilization.

A simple test that I could do to confirm that the wireless adapter is the problem is to totally disable it, use a USB wireless adapter, and see if the problem persists. I will do that next and report back. Otherwise I'm not sure what kernel debug options are available - I'll try setting up kdump, but it seems like it might be complicated by the fact that I use disk encryption via luks.

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

It seems I've missed the wiki sleep fix. I'll check how it works. If not, I'll get back to hibernation only

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

Proposed fixed do not fix the sleep option. Although hibernation works fine.

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

Pattern remains consistent?
You can manually sleep the system (for an arbiitrarily long time) and wake it successfully, but if you leave it alone and let it auto-suspend for inactivity, it results in

monitor turned off; all the led lights turned on; it does not respond to any input

You're saying "back to hibernation only" would you otherwise enter a hybrid sleep (ie. sleep/autowake/hibernate)?
Does a manually initiated hybrid sleep work?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

the hibernation works as expected. a manually triggered or on idle timeout it goes to hibernation on it's own. A restore from hibernation does not hang. The only minus in this solution is a longer time required to go in/restore. Plus in my case enter pass each time(luks)

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

Ok, but

The suspend works when I do it manually.

and

Mar 16 12:54:06 arch systemd-logind[1726]: The system will suspend now!
Mar 16 12:54:07 arch systemd[1]: Starting System Suspend...
Mar 16 12:54:07 arch systemd-sleep[49817]: Performing sleep operation 'suspend'...
Mar 16 12:54:07 arch kernel: PM: suspend entry (s2idle)
Mar 16 12:54:15 arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 16 12:54:15 arch systemd-sleep[49817]: System returned from sleep operation 'suspend'.
Mar 16 12:54:15 arch kernel: PM: suspend exit
Mar 16 12:54:16 arch systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 16 12:54:16 arch systemd[1]: Finished System Suspend.
Mar 16 12:54:16 arch systemd[1]: systemd-suspend.service: Consumed 1.176s CPU time, 9.2M memory peak.
Mar 16 12:54:16 arch systemd[1]: Reached target Suspend.
Mar 16 12:54:16 arch systemd-logind[1726]: Operation 'suspend' finished.
Mar 16 12:54:16 arch systemd[1]: Stopped target Suspend.

So there's gonna be another factor reg. the autosuspend, eg.
* those uncontrolled sleeps last much longer and you've only tested the behavior short-term
* screensaver
* the sleep-on-idle condition actually results in a hybrid sleep where the system wakes from S2idle to enter S4
* "stuff"

Identifying that difference might be the key to understand what's going wrong and address that.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

freebench

Member

Registered: 2020-06-14

Posts: 41

Re: Non responsive after suspend

an extended suspend

the issue shows when it's on sleep for long time, regardless of how it happened manually or on timeout. which makes it even more annoying to investigate.

seth

Member

Registered: 2012-09-03

Posts: 62,927

Re: Non responsive after suspend

Assuming you've not configured the system for suspend-then-hibernate, something else would trigger the spurious wakeup resulting in a frozen state.

1. Is there a parallel windows installation?
2. Did you enable WOL?
3. cat /proc/acpi/wakeup; lspci # for the pot triggers and the matching bus IDs

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc