You are not logged in.
- Topics: Active | Unanswered
#1 2025-03-30 22:18:54
- NaboriRuta
- Member
- Registered: 2025-02-09
- Posts: 13
[SOLVED] Computer keeps turning on after attempted suspend
This is not something unique to my current installation, as the same problem has been happening after multiple installs.
Every time I try to suspend my computer (whether that's through the Budgie power menu or by the terminal) my computer turns off for a second and turns back on again. It's not a full system reboot, it just fails to suspend to RAM. Suspending in Windows still works as intended, so I think that means Windows Suspend is enabled somewhere in UEFI/BIOS.
Current suspend method: deep (it's even worse with s2idle) (Hardware isn't offering shallow)
Desktop: Budgie
Display Manager: LightDM (GTK Greeter)
Hardware:
CPU: Ryzen 5 5600GT
Motherboard: Gigabyte A520-I AC
BIOS Version: f21g
RAM: 32GB DDR4
Graphics: Radeon RX 6600
Places I've tried going to for help:
This Help Page
The Wiki
This Troubleshooting Wiki Page
Result of journalctl -b starting from suspend initialization:
Mar 30 16:47:22 archlinux systemd-logind[709]: The system will suspend now!
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.2203] manager: sleep: sleep requested (sleeping: no enabled: yes)
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.2204] device (enp7s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Mar 30 16:47:22 archlinux sudo[6804]: pam_unix(sudo:session): session closed for user root
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.2263] manager: NetworkManager state is now ASLEEP
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.2265] device (wlp6s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Mar 30 16:47:22 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 30 16:47:22 archlinux discord.desktop[1344]: 16:47:22.232 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:22 archlinux discord.desktop[1344]: 16:47:22.232 › [GatewaySocket] [WS CLOSED] (false, 1006, ) retrying in 2.30 seconds.
Mar 30 16:47:22 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 30 16:47:22 archlinux kernel: wlp6s0: deauthenticating from e4:5e:1b:db:c6:d7 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 30 16:47:22 archlinux discord.desktop[1344]: 16:47:22.255 › [GatewaySocket] Expedited heartbeat requested, but, connection state is WILL_RECONNECT and reconnectImmediately was not requested reason: network detected offline.
Mar 30 16:47:22 archlinux wpa_supplicant[794]: nl80211: send_event_marker failed: Source based routing not supported
Mar 30 16:47:22 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=e4:5e:1b:db:c6:d7 reason=3 locally_generated=1
Mar 30 16:47:22 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 30 16:47:22 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3690] device (wlp6s0): supplicant interface state: completed -> disconnected
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3691] device (wlp6s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Mar 30 16:47:22 archlinux avahi-daemon[706]: Withdrawing address record for fdc0:849c:81aa:41d9:ac7d:acca:25f:52a2 on wlp6s0.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fdc0:849c:81aa:41d9:ac7d:acca:25f:52a2.
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3693] dhcp4 (wlp6s0): canceled DHCP transaction
Mar 30 16:47:22 archlinux avahi-daemon[706]: Joining mDNS multicast group on interface wlp6s0.IPv6 with address fe80::5f7f:e967:b6:10fe.
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3693] dhcp4 (wlp6s0): activation: beginning transaction (timeout in 45 seconds)
Mar 30 16:47:22 archlinux avahi-daemon[706]: Registering new address record for fe80::5f7f:e967:b6:10fe on wlp6s0.*.
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3693] dhcp4 (wlp6s0): state changed no lease
Mar 30 16:47:22 archlinux avahi-daemon[706]: Withdrawing address record for fe80::5f7f:e967:b6:10fe on wlp6s0.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::5f7f:e967:b6:10fe.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Interface wlp6s0.IPv6 no longer relevant for mDNS.
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.3870] device (wlp6s0): set-hw-addr: set MAC address to 22:06:92:B2:B7:71 (scanning)
Mar 30 16:47:22 archlinux avahi-daemon[706]: Interface wlp6s0.IPv4 no longer relevant for mDNS.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.86.59.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Withdrawing address record for 192.168.86.59 on wlp6s0.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Joining mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.86.59.
Mar 30 16:47:22 archlinux avahi-daemon[706]: New relevant interface wlp6s0.IPv4 for mDNS.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Registering new address record for 192.168.86.59 on wlp6s0.IPv4.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Withdrawing address record for 192.168.86.59 on wlp6s0.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.86.59.
Mar 30 16:47:22 archlinux avahi-daemon[706]: Interface wlp6s0.IPv4 no longer relevant for mDNS.
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.8581] device (wlp6s0): supplicant interface state: disconnected -> interface_disabled
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.8581] device (wlp6s0): supplicant interface state: interface_disabled -> disconnected
Mar 30 16:47:22 archlinux NetworkManager[705]: <info> [1743374842.8583] device (wlp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Mar 30 16:47:23 archlinux NetworkManager[705]: <info> [1743374843.3035] device (wlp6s0): set-hw-addr: reset MAC address to CC:47:40:4C:57:53 (unmanage)
Mar 30 16:47:23 archlinux systemd[1]: Reached target Sleep.
Mar 30 16:47:23 archlinux systemd[1]: Starting System Suspend...
Mar 30 16:47:23 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 30 16:47:23 archlinux systemd[1]: user@1000.service: Unit now frozen-by-parent.
Mar 30 16:47:23 archlinux systemd[1]: session-2.scope: Unit now frozen-by-parent.
Mar 30 16:47:23 archlinux systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Mar 30 16:47:23 archlinux systemd[1]: user.slice: Unit now frozen.
Mar 30 16:47:23 archlinux systemd-sleep[6835]: Successfully froze unit 'user.slice'.
Mar 30 16:47:23 archlinux systemd-sleep[6835]: Performing sleep operation 'suspend'...
Mar 30 16:47:23 archlinux kernel: PM: suspend entry (deep)
Mar 30 16:47:23 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 30 16:47:23 archlinux wpa_supplicant[794]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Mar 30 16:47:23 archlinux kernel: Filesystems sync: 0.003 seconds
Mar 30 16:47:38 archlinux kernel: Freezing user space processes
Mar 30 16:47:38 archlinux kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Mar 30 16:47:38 archlinux kernel: OOM killer disabled.
Mar 30 16:47:38 archlinux kernel: Freezing remaining freezable tasks
Mar 30 16:47:38 archlinux kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Mar 30 16:47:38 archlinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: leds 0003:057E:2009.0007:blue:player-5: Setting an LED's brightness failed (-110)
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: leds 0003:057E:2009.0007:green:player-4: Setting an LED's brightness failed (-110)
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: leds 0003:057E:2009.0007:green:player-3: Setting an LED's brightness failed (-110)
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: leds 0003:057E:2009.0007:green:player-2: Setting an LED's brightness failed (-110)
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:38 archlinux kernel: leds 0003:057E:2009.0007:green:player-1: Setting an LED's brightness failed (-110)
Mar 30 16:47:38 archlinux kernel: serial 00:04: disabled
Mar 30 16:47:38 archlinux kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
Mar 30 16:47:38 archlinux kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Mar 30 16:47:38 archlinux kernel: ata1.00: Entering standby power mode
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Mar 30 16:47:38 archlinux kernel: ACPI: PM: Preparing to enter system sleep state S3
Mar 30 16:47:38 archlinux kernel: ACPI: PM: Saving platform NVS memory
Mar 30 16:47:38 archlinux kernel: Disabling non-boot CPUs ...
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 11 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 10 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 9 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 8 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 7 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 6 is now offline
Mar 30 16:47:38 archlinux kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 5 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 4 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 3 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 2 is now offline
Mar 30 16:47:38 archlinux kernel: smpboot: CPU 1 is now offline
Mar 30 16:47:38 archlinux kernel: ACPI: PM: Low-level resume complete
Mar 30 16:47:38 archlinux kernel: ACPI: PM: Restoring platform NVS memory
Mar 30 16:47:38 archlinux kernel: AMD-Vi: Virtual APIC enabled
Mar 30 16:47:38 archlinux kernel: AMD-Vi: Virtual APIC enabled
Mar 30 16:47:38 archlinux kernel: LVT offset 0 assigned for vector 0x400
Mar 30 16:47:38 archlinux kernel: Enabling non-boot CPUs ...
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Mar 30 16:47:38 archlinux kernel: CPU1 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Mar 30 16:47:38 archlinux kernel: CPU2 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Mar 30 16:47:38 archlinux kernel: CPU3 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Mar 30 16:47:38 archlinux kernel: CPU4 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Mar 30 16:47:38 archlinux kernel: CPU5 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Mar 30 16:47:38 archlinux kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Mar 30 16:47:38 archlinux kernel: CPU6 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Mar 30 16:47:38 archlinux kernel: CPU7 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Mar 30 16:47:38 archlinux kernel: CPU8 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Mar 30 16:47:38 archlinux kernel: CPU9 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Mar 30 16:47:38 archlinux kernel: CPU10 is up
Mar 30 16:47:38 archlinux kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Mar 30 16:47:38 archlinux kernel: CPU11 is up
Mar 30 16:47:38 archlinux kernel: ACPI: PM: Waking up from system sleep state S3
Mar 30 16:47:38 archlinux kernel: xhci_hcd 0000:04:00.0: xHC error in resume, USBSTS 0x401, Reinit
Mar 30 16:47:38 archlinux kernel: usb usb1: root hub lost power or was reset
Mar 30 16:47:38 archlinux kernel: usb usb2: root hub lost power or was reset
Mar 30 16:47:38 archlinux kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
Mar 30 16:47:38 archlinux kernel: serial 00:04: activated
Mar 30 16:47:38 archlinux kernel: nvme nvme0: 12/0/0 default/read/poll queues
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0xa00000 from 0x81fd000000 for PSP TMR
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3100 (59.49.0)
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
Mar 30 16:47:38 archlinux kernel: usb 1-7: WARN: invalid context state for evaluate context command.
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Mar 30 16:47:38 archlinux kernel: [drm] kiq ring mec 2 pipe 1 q 0
Mar 30 16:47:38 archlinux kernel: [drm] DMUB hardware initialized: version=0x02020020
Mar 30 16:47:38 archlinux kernel: ata2: SATA link down (SStatus 0 SControl 300)
Mar 30 16:47:38 archlinux kernel: ata6: SATA link down (SStatus 0 SControl 330)
Mar 30 16:47:38 archlinux kernel: usb 1-7: reset full-speed USB device number 3 using xhci_hcd
Mar 30 16:47:38 archlinux kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 30 16:47:38 archlinux kernel: ata1.00: LPM support broken, forcing max_power
Mar 30 16:47:38 archlinux kernel: sd 0:0:0:0: [sda] Starting disk
Mar 30 16:47:38 archlinux kernel: ata1.00: LPM support broken, forcing max_power
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Mar 30 16:47:38 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Mar 30 16:47:38 archlinux kernel: ata1.00: configured for UDMA/133
Mar 30 16:47:38 archlinux kernel: ahci 0000:04:00.1: port does not support device sleep
Mar 30 16:47:38 archlinux kernel: usb 1-8: WARN: invalid context state for evaluate context command.
Mar 30 16:47:38 archlinux kernel: usb 1-8: reset full-speed USB device number 4 using xhci_hcd
Mar 30 16:47:38 archlinux kernel: usb 1-2: WARN: invalid context state for evaluate context command.
Mar 30 16:47:38 archlinux kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Mar 30 16:47:38 archlinux kernel: OOM killer enabled.
Mar 30 16:47:38 archlinux kernel: Restarting tasks ... done.
Mar 30 16:47:38 archlinux kernel: random: crng reseeded on system resumption
Mar 30 16:47:38 archlinux kernel: PM: suspend exit
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
Mar 30 16:47:38 archlinux systemd-sleep[6835]: System returned from sleep operation 'suspend'.
Mar 30 16:47:38 archlinux joycond[796]: epoll_pwait failure
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.613 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.613 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 30 16:47:38 archlinux dbus-broker[704]: A security policy denied :1.5 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.51.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 30 16:47:38 archlinux systemd[1]: user.slice: Unit now thawed.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
Mar 30 16:47:38 archlinux systemd[1]: user-1000.slice: Unit now thawed.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
Mar 30 16:47:38 archlinux systemd-sleep[6835]: Successfully thawed unit 'user.slice'.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
Mar 30 16:47:38 archlinux systemd[1]: session-2.scope: Unit now thawed.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
Mar 30 16:47:38 archlinux systemd[1]: user@1000.service: Unit now thawed.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
Mar 30 16:47:38 archlinux systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
Mar 30 16:47:38 archlinux systemd[1]: Finished System Suspend.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
Mar 30 16:47:38 archlinux systemd[1]: systemd-suspend.service: Consumed 4.031s CPU time, 1.6M memory peak.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
Mar 30 16:47:38 archlinux systemd[1]: Stopped target Sleep.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 30 16:47:38 archlinux systemd[1]: Reached target Suspend.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 30 16:47:38 archlinux systemd-logind[709]: Operation 'suspend' finished.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.6162] manager: sleep: wake requested (sleeping: yes enabled: yes)
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.6163] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
Mar 30 16:47:38 archlinux systemd[1]: Starting Load/Save RF Kill Switch Status...
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 30 16:47:38 archlinux systemd[1]: Stopped target Suspend.
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 30 16:47:38 archlinux bluetoothd[707]: Battery Provider Manager destroyed
Mar 30 16:47:38 archlinux systemd[1]: Stopped target Bluetooth Support.
Mar 30 16:47:38 archlinux systemd[925]: Stopped target Bluetooth.
Mar 30 16:47:38 archlinux systemd[925]: Reached target Bluetooth.
Mar 30 16:47:38 archlinux systemd[1]: Reached target Bluetooth Support.
Mar 30 16:47:38 archlinux kernel: Generic FE-GE Realtek PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
Mar 30 16:47:38 archlinux systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 30 16:47:38 archlinux bluetoothd[707]: Battery Provider Manager created
Mar 30 16:47:38 archlinux kernel: Bluetooth: MGMT ver 1.23
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 30 16:47:38 archlinux bluetoothd[707]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.7929] device (wlp6s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.7934] manager: NetworkManager state is now DISCONNECTED
Mar 30 16:47:38 archlinux kernel: r8169 0000:07:00.0 enp7s0: Link is Down
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] Connection has reset backoff for reason: power monitor resumed
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] [WS CLOSED] (true, 0, power monitor resumed) retrying immediately.
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] Connection has reset backoff for reason: power monitor resumed
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.800 › [GatewaySocket] [WS CLOSED] (true, 0, power monitor resumed) retrying immediately.
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.801 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.801 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.802 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:38 archlinux discord.desktop[1344]: 16:47:38.802 › [GatewaySocket] [WS CLOSED] (false, 0, An error with the websocket occurred) retrying in 1.34 seconds.
Mar 30 16:47:38 archlinux wpa_supplicant[794]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.8072] device (wlp6s0): supplicant interface state: internal-starting -> disconnected
Mar 30 16:47:38 archlinux NetworkManager[705]: <info> [1743374858.8073] device (wlp6s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Mar 30 16:47:38 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:39 archlinux kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 30 16:47:39 archlinux kernel: sd 4:0:0:0: [sdb] Starting disk
Mar 30 16:47:39 archlinux kernel: ata5.00: configured for UDMA/133
Mar 30 16:47:39 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:39 archlinux kernel: leds 0003:057E:2009.0007:green:player-1: Setting an LED's brightness failed (-110)
Mar 30 16:47:39 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:40 archlinux discord.desktop[1344]: 16:47:40.146 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:40 archlinux discord.desktop[1344]: 16:47:40.146 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:40 archlinux discord.desktop[1344]: 16:47:40.149 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:40 archlinux discord.desktop[1344]: 16:47:40.149 › [GatewaySocket] [WS CLOSED] (false, 0, An error with the websocket occurred) retrying in 3.79 seconds.
Mar 30 16:47:40 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:40 archlinux kernel: leds 0003:057E:2009.0007:green:player-2: Setting an LED's brightness failed (-110)
Mar 30 16:47:40 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:41 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:41 archlinux kernel: leds 0003:057E:2009.0007:green:player-3: Setting an LED's brightness failed (-110)
Mar 30 16:47:41 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:42 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:42 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Mar 30 16:47:42 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5745 max_tx_power=2000 no_ir=1
Mar 30 16:47:42 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5745 max_tx_power=2000
Mar 30 16:47:42 archlinux kernel: leds 0003:057E:2009.0007:green:player-4: Setting an LED's brightness failed (-110)
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0216] policy: auto-activating connection 'Google' (a3e8cb9b-e19b-4f44-a70e-568c82ff80f9)
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0218] device (wlp6s0): Activation: starting connection 'Google' (a3e8cb9b-e19b-4f44-a70e-568c82ff80f9)
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0218] device (wlp6s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0219] manager: NetworkManager state is now CONNECTING
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0220] device (wlp6s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0221] device (wlp6s0): Activation: (wifi) access point 'Google' has security, but secrets are required.
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0222] device (wlp6s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0225] device (wlp6s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0226] device (wlp6s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0226] device (wlp6s0): Activation: (wifi) connection 'Google' has security, and secrets exist. No new secrets needed.
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'ssid' value 'Google'
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'scan_ssid' value '1'
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'bgscan' value 'simple:30:-70:86400'
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'auth_alg' value 'OPEN'
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.0227] Config: added 'psk' value '<hidden>'
Mar 30 16:47:43 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: SME: Trying to authenticate with e4:5e:1b:db:c6:d7 (SSID='Google' freq=5745 MHz)
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux kernel: wlp6s0: authenticate with e4:5e:1b:db:c6:d7 (local address=cc:47:40:4c:57:53)
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5041] device (wlp6s0): supplicant interface state: disconnected -> authenticating
Mar 30 16:47:43 archlinux kernel: wlp6s0: send auth to e4:5e:1b:db:c6:d7 (try 1/3)
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: Trying to associate with e4:5e:1b:db:c6:d7 (SSID='Google' freq=5745 MHz)
Mar 30 16:47:43 archlinux kernel: wlp6s0: authenticated
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5137] device (wlp6s0): supplicant interface state: authenticating -> associating
Mar 30 16:47:43 archlinux kernel: wlp6s0: associate with e4:5e:1b:db:c6:d7 (try 1/3)
Mar 30 16:47:43 archlinux kernel: wlp6s0: RX AssocResp from e4:5e:1b:db:c6:d7 (capab=0x1011 status=0 aid=7)
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: Associated with e4:5e:1b:db:c6:d7
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 30 16:47:43 archlinux kernel: wlp6s0: associated
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5333] device (wlp6s0): supplicant interface state: associating -> associated
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5385] device (wlp6s0): supplicant interface state: associated -> 4way_handshake
Mar 30 16:47:43 archlinux kernel: nintendo 0003:057E:2009.0007: timeout waiting for input report
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: WPA: Key negotiation completed with e4:5e:1b:db:c6:d7 [PTK=CCMP GTK=CCMP]
Mar 30 16:47:43 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-CONNECTED - Connection to e4:5e:1b:db:c6:d7 completed [id=0 id_str=]
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5580] device (wlp6s0): supplicant interface state: 4way_handshake -> completed
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5580] device (wlp6s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Google"
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5581] device (wlp6s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5583] dhcp4 (wlp6s0): activation: beginning transaction (timeout in 45 seconds)
Mar 30 16:47:43 archlinux avahi-daemon[706]: Joining mDNS multicast group on interface wlp6s0.IPv6 with address fe80::5f7f:e967:b6:10fe.
Mar 30 16:47:43 archlinux avahi-daemon[706]: New relevant interface wlp6s0.IPv6 for mDNS.
Mar 30 16:47:43 archlinux avahi-daemon[706]: Registering new address record for fe80::5f7f:e967:b6:10fe on wlp6s0.*.
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.5778] dhcp4 (wlp6s0): state changed new lease, address=192.168.86.59, acd pending
Mar 30 16:47:43 archlinux systemd[1]: systemd-rfkill.service: Deactivated successfully.
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7166] dhcp4 (wlp6s0): state changed new lease, address=192.168.86.59
Mar 30 16:47:43 archlinux avahi-daemon[706]: Joining mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.86.59.
Mar 30 16:47:43 archlinux avahi-daemon[706]: New relevant interface wlp6s0.IPv4 for mDNS.
Mar 30 16:47:43 archlinux avahi-daemon[706]: Registering new address record for 192.168.86.59 on wlp6s0.IPv4.
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7173] policy: set 'Google' (wlp6s0) as default for IPv4 routing and DNS
Mar 30 16:47:43 archlinux discord.desktop[1344]: 16:47:43.717 › [GatewaySocket] Connection has reset backoff for reason: network detected online.
Mar 30 16:47:43 archlinux discord.desktop[1344]: 16:47:43.718 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:43 archlinux discord.desktop[1344]: 16:47:43.718 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:43 archlinux discord.desktop[1344]: 16:47:43.720 › [GatewaySocket] Setting connection state to WILL_RECONNECT
Mar 30 16:47:43 archlinux discord.desktop[1344]: 16:47:43.720 › [GatewaySocket] [WS CLOSED] (false, 0, An error with the websocket occurred) retrying in 2.58 seconds.
Mar 30 16:47:43 archlinux kernel: wlp6s0: Limiting TX power to 30 (30 - 0) dBm as advertised by e4:5e:1b:db:c6:d7
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7844] device (wlp6s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7853] device (wlp6s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7853] device (wlp6s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7855] manager: NetworkManager state is now CONNECTED_SITE
Mar 30 16:47:43 archlinux NetworkManager[705]: <info> [1743374863.7857] device (wlp6s0): Activation: successful, device activated.
Mar 30 16:47:43 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 30 16:47:43 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux budgie-panel[1246]: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
Mar 30 16:47:43 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 30 16:47:43 archlinux kernel: leds 0003:057E:2009.0007:blue:player-5: Setting an LED's brightness failed (-110)
Mar 30 16:47:44 archlinux wpa_supplicant[794]: wlp6s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-48 noise=9999 txrate=292500
Mar 30 16:47:44 archlinux NetworkManager[705]: <info> [1743374864.1560] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 30 16:47:45 archlinux avahi-daemon[706]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::5f7f:e967:b6:10fe.
Mar 30 16:47:45 archlinux avahi-daemon[706]: Joining mDNS multicast group on interface wlp6s0.IPv6 with address fdc0:849c:81aa:41d9:ac7d:acca:25f:52a2.
Mar 30 16:47:45 archlinux avahi-daemon[706]: Registering new address record for fdc0:849c:81aa:41d9:ac7d:acca:25f:52a2 on wlp6s0.*.
Mar 30 16:47:45 archlinux avahi-daemon[706]: Withdrawing address record for fe80::5f7f:e967:b6:10fe on wlp6s0.
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.300 › [GatewaySocket] Setting connection state to CONNECTING
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.301 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.545 › [GatewaySocket] [CONNECTED] wss://gateway.discord.gg/?encoding=etf&v=9&compress=zstd-stream in 244 ms
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.545 › [GatewaySocket] Setting connection state to RESUMING
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.545 › [GatewaySocket] [RESUME] resuming session 410ab5960401cd15bb332a278d9cbca6, seq: 444
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.545 › [GatewaySocket] [HELLO] via
Mar 30 16:47:46 archlinux discord.desktop[1344]: gateway-prd-us-east1-c-k12k: 0, heartbeat interval: 41250, took 245 ms
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.627 › [GatewaySocket]
Mar 30 16:47:46 archlinux discord.desktop[1344]: gateway-prd-us-east1-c-k12k: 6.183
Mar 30 16:47:46 archlinux discord.desktop[1344]: | id_created: 0
Mar 30 16:47:46 archlinux discord.desktop[1344]: | session_lookup_time: 0.322
Mar 30 16:47:46 archlinux discord.desktop[1344]: | session_lookup_finished: 0.023
Mar 30 16:47:46 archlinux discord.desktop[1344]: | discord-sessions-prd-1-295: 0.045
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.627 › [GatewaySocket] Setting connection state to SESSION_ESTABLISHED
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.670 › [Flux] Dispatching CONNECTION_RESUMED
Mar 30 16:47:46 archlinux discord.desktop[1344]: 16:47:46.675 › [GatewaySocket] [RESUMED] took 374ms, replayed 0 events, new seq: 447
Mar 30 16:47:48 archlinux budgie-screensaver-dialog[6931]: gkr-pam: unlocked login keyring
Mar 30 16:47:48 archlinux budgie-screensaver-dialog[6966]: pam_unix(budgie-screensaver:account): setuid failed: Operation not permitted
Mar 30 16:47:49 archlinux discord.desktop[1344]: 16:47:49.685 › [discord_protos.discord_users.v1.FrecencyUserSettings] Scheduling save from markDirty
Mar 30 16:47:49 archlinux discord.desktop[1344]: 16:47:49.685 › [discord_protos.discord_users.v1.FrecencyUserSettings] Persisting proto
Mar 30 16:47:53 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 30 16:48:05 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:48:05 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:48:05 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:48:22 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:48:34 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:48:43 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:49:08 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:49:16 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interrupt
Mar 30 16:49:18 archlinux kernel: rtw_8821ce 0000:06:00.0: unhandled firmware c2h interruptAny and all help is appreciated!
Last edited by NaboriRuta (2025-03-31 22:58:30)
Offline
#2 2025-03-31 06:56:08
- espresso
- Member
- From: Pale Blue Dot, US
- Registered: 2023-05-15
- Posts: 67
Re: [SOLVED] Computer keeps turning on after attempted suspend
Digging around on 'unhandled firmware c2h interrupt', I find the commit https://lore.kernel.org/linux-wireless/ … altek.com/ which might suggest the firmware crashed?
There seems a similar issue with various workarounds including power management.
https://github.com/lwfinger/rtw88/issues/61
Let us know how it goes..
Capitalism's power seems inescapable, but then so did the divine right of kings. ― Ursula LeGuin
Offline
#3 2025-03-31 16:58:43
- NaboriRuta
- Member
- Registered: 2025-02-09
- Posts: 13
Re: [SOLVED] Computer keeps turning on after attempted suspend
Since only 8822c firmware supports this feature, the interrupt will only be triggered when 8822c chipset is loaded.
So it looks like I need to:
check if I have the 8822c chipset, and
disable the chipset if I have it.
According to the wiki, it seems like I need to echo 8822c to /proc/acpi/wakeup as a sort of "band-aid" solution. If it works, I need to figure out how to add it as a systemctl service (or try to disable it directly in BIOS).
I won't be able to do this for a while, but I'll update once I do.
Last edited by NaboriRuta (2025-03-31 20:19:02)
Offline
#4 2025-03-31 21:36:48
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 74,307
Re: [SOLVED] Computer keeps turning on after attempted suspend
Yes you have and you can "rtw88_pci.disable_msi=Y" to likely prevent hat interrupt warning, but I doubt that's the cause
Mar 30 16:47:38 archlinux kernel: ahci 0000:04:00.1: port does not support device sleep
Mar 30 16:47:38 archlinux kernel: usb 1-8: WARN: invalid context state for evaluate context command.
Mar 30 16:47:38 archlinux kernel: usb 1-8: reset full-speed USB device number 4 using xhci_hcd
Mar 30 16:47:38 archlinux kernel: usb 1-2: WARN: invalid context state for evaluate context command.
Mar 30 16:47:38 archlinux kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcdlsusb -tv
cat /proc/acpi/wakeupAlso what's the nintendo device? Some gamepad?
Offline
#5 2025-03-31 21:46:17
- NaboriRuta
- Member
- Registered: 2025-02-09
- Posts: 13
Re: [SOLVED] Computer keeps turning on after attempted suspend
seth wrote:
Also what's the nintendo device? Some gamepad?
The Nintendo device is a switch pro controller. It could also be the joycond-autopair-git driver I use. (I was actually on the forums for troubles with it a while back lol)
Offline
#6 2025-03-31 22:22:40
- NaboriRuta
- Member
- Registered: 2025-02-09
- Posts: 13
Re: [SOLVED] Computer keeps turning on after attempted suspend
Result of lsusb -tv:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 007: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 048d:5702 Integrated Technology Express, Inc. RGB LED Controller
|__ Port 008: Dev 003, If 0, Class=Wireless, Driver=btusb, 12M
ID 13d3:3533 IMC Networks
|__ Port 008: Dev 003, If 1, Class=Wireless, Driver=btusb, 12M
ID 13d3:3533 IMC Networks
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
|__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
|__ Port 001: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
|__ Port 001: Dev 002, If 3, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
|__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 3554:fa09
|__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 3554:fa09
/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hubResult of cat /proc/acpi/wakeup:
Device S-state Status Sysfs node
GP17 S4 *enabled pci:0000:00:08.1
XHC0 S4 *enabled pci:0000:09:00.3
XHC1 S4 *enabled pci:0000:09:00.4
PS2K S3 *disabled
GPP0 S4 *enabled pci:0000:00:01.1
SWUS S4 *enabled pci:0000:01:00.0
SWDS S4 *enabled pci:0000:02:00.0
PTXH S4 *enabled pci:0000:04:00.0
PT20 S4 *disabled
PT21 S4 *disabled
PT22 S4 *enabled pci:0000:05:02.0
PT23 S4 *enabled pci:0000:05:03.0
PT24 S4 *disabled
PT26 S4 *disabled
PT27 S4 *disabled
PT28 S4 *disabled
PT29 S4 *disabledI was not able to find the 8822c chipset in /proc/acpi/wakeup so I don't know how I would go with disabling that...
Last edited by NaboriRuta (2025-03-31 22:27:02)
Offline
#7 2025-03-31 22:45:40
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 74,307
Re: [SOLVED] Computer keeps turning on after attempted suspend
lspci -nnbut again: I don#t even think it's the wifi chip.
Remove the switch controller, the logitech bolt receiver and disable XHC0/1 and PTXH - can you now sleep
Offline
#8 2025-03-31 22:58:09
- NaboriRuta
- Member
- Registered: 2025-02-09
- Posts: 13
Re: [SOLVED] Computer keeps turning on after attempted suspend
welp, I figured out the issue... it was my wireless mouse's reciever...
To any other Arch users stumbling across this thread, DO NOT USE THE WIRELESS RECIEVER ON A LOGITECH M650L COMPUTER MOUSE. The bluetooth setting works fine, though.
Thank you guys so much for the help with this problem I definitely could've figured out on my own. Post marked as solved.
Offline