You are not logged in.

Pages: 1 2 3

#51 2024-12-14 17:20:20

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

seth wrote:

Don't grep for random stuff, it's not even clear whether or when a sleep cycle happened there.

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

i was grepping for today and for my one terabyte nvme, anyways here is the link you wanted http://0x0.st/XF_I.txt

Offline

#52 2024-12-14 23:11:10

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

small question:  how do I move a thread as this thread is now a pretty good fit for Kernel & Hardware

Offline

#53 2024-12-15 08:02:15

seth
Member
Registered: 2012-09-03
Posts: 60,378

Re: resuming arch linux from sleep is not working properly

You can report it, however we might be facing multiple issues - your last journal runs into https://bbs.archlinux.org/viewtopic.php … 4#p2214414

Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 13) timeout
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 14 12:18:57 archlinux kernel: wlan0: Driver requested disconnection from AP 00:00:00:00:00:00

Your BT config and/or the fact that you're running multiple installations and pot. windows on the same BT HW might have a bigger impact than anything else here. Maybe it's even the wifi in your case.


module_blacklist=mt7921e

https://wiki.archlinux.org/title/Kernel_parameters
You'll loose wifi and bluetooth, but it might pin the cause if S3/resume then works reliably.

Disabling BT should be for free, afaict there're not actual BT devices?

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

Offline

#54 2024-12-15 16:04:59

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

seth wrote:

You can report it, however we might be facing multiple issues - your last journal runs into https://bbs.archlinux.org/viewtopic.php … 4#p2214414

Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 13) timeout
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 14 12:18:57 archlinux kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 14 12:18:57 archlinux kernel: wlan0: Driver requested disconnection from AP 00:00:00:00:00:00

Your BT config and/or the fact that you're running multiple installations and pot. windows on the same BT HW might have a bigger impact than anything else here. Maybe it's even the wifi in your case.


module_blacklist=mt7921e

https://wiki.archlinux.org/title/Kernel_parameters
You'll loose wifi and bluetooth, but it might pin the cause if S3/resume then works reliably.

Disabling BT should be for free, afaict there're not actual BT devices?

I have those problems on my original install and my 1tb install but the original still works even with those problems on the original install and the 1tb install when using lts but I will try.

Last edited by Omarz2012 (2024-12-15 17:07:20)

Offline

#55 2024-12-15 19:57:08

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

i can confirm that my wifi card failing to suspend has nothing to due with the fact that my new install cant resume as even when blacklisting the module, it does not fix the problem at hand or even have any change to it for that matter

Last edited by Omarz2012 (2024-12-15 19:57:58)

Offline

#56 2024-12-15 20:16:28

seth
Member
Registered: 2012-09-03
Posts: 60,378

Re: resuming arch linux from sleep is not working properly

Updated journal?

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

Offline

#57 2024-12-17 22:05:46

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

i recently have switched to using a different SSD, i has a problem whereit gets stuck on 

Dec 17 16:58:37 omarsarchernitro5 kernel: Filesystems sync: 0.006 seconds
Dec 17 16:58:37 omarsarchernitro5 kernel: PM: suspend entry (deep)

but for some reason the turning off saving memory allocations does not work anymore, this happens every second time i sleep per boot. here is the part which i think are important

Dec 17 16:58:37 omarsarchernitro5 wpa_supplicant[618]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Dec 17 16:58:37 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 17 16:58:37 omarsarchernitro5 kernel: Filesystems sync: 0.006 seconds
Dec 17 16:58:37 omarsarchernitro5 kernel: PM: suspend entry (deep)
Dec 17 16:58:37 omarsarchernitro5 systemd-sleep[837]: Performing sleep operation 'suspend'...
Dec 17 16:58:37 omarsarchernitro5 systemd-sleep[837]: in suspend-then-hibernate operations or setups with encrypted home directories.
Dec 17 16:58:37 omarsarchernitro5 systemd-sleep[837]: This is not recommended, and might result in unexpected behavior, particularly
Dec 17 16:58:37 omarsarchernitro5 systemd-sleep[837]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Dec 17 16:58:37 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 17 16:58:37 omarsarchernitro5 systemd[1]: Starting System Suspend...
Dec 17 16:58:37 omarsarchernitro5 systemd[1]: Reached target Sleep.
Dec 17 16:58:37 omarsarchernitro5 NetworkManager[574]: <info>  [1734472717.0459] device (wlp5s0): set-hw-addr: reset MAC address to 74:4C:A1:7B:B8:3D (unmanage)
Dec 17 16:58:36 omarsarchernitro5 systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 17 16:58:36 omarsarchernitro5 systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.9100] device (wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.9098] device (wlp5s0): supplicant interface state: interface_disabled -> disconnected
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.9098] device (wlp5s0): supplicant interface state: disconnected -> interface_disabled
Dec 17 16:58:36 omarsarchernitro5 kernel: usb 1-4: Failed to suspend device, error -110
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6879] device (wlp5s0): set-hw-addr: set MAC address to FA:98:6A:93:0D:7E (scanning)
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6133] dhcp6 (wlp5s0): state changed no lease
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6133] dhcp6 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6133] dhcp6 (wlp5s0): canceled DHCP transaction
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6132] dhcp4 (wlp5s0): state changed no lease
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6132] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 16:58:36 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6132] dhcp4 (wlp5s0): canceled DHCP transaction
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6064] device (wlp5s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.6063] device (wlp5s0): supplicant interface state: completed -> disconnected
Dec 17 16:58:36 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 17 16:58:36 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=3a:b7:f1:a1:2d:fa reason=3 locally_generated=1
Dec 17 16:58:36 omarsarchernitro5 wpa_supplicant[618]: nl80211: send_event_marker failed: Source based routing not supported
Dec 17 16:58:36 omarsarchernitro5 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 17 16:58:36 omarsarchernitro5 kernel: wlp5s0: deauthenticating from 3a:b7:f1:a1:2d:fa by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.2996] device (wlp5s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.2994] manager: NetworkManager state is now ASLEEP
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.2993] device (p2p-dev-wlp5s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.2914] device (enp4s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 17 16:58:36 omarsarchernitro5 NetworkManager[574]: <info>  [1734472716.2913] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dec 17 16:58:36 omarsarchernitro5 systemd-logind[576]: The system will suspend now!
Dec 17 16:58:36 omarsarchernitro5 sddm[624]: Message received from greeter: Suspend
Dec 17 16:58:35 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=175600
Dec 17 16:58:35 omarsarchernitro5 chronyd[591]: Forward time jump detected!
Dec 17 16:58:32 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=175600
Dec 17 16:58:31 omarsarchernitro5 NetworkManager[574]: <info>  [1734472711.0771] dhcp6 (wlp5s0): state changed new lease, address=2607:fea8:5859:1200::9992
Dec 17 16:58:31 omarsarchernitro5 NetworkManager[574]: <info>  [1734472711.0563] policy: set 'Versil' (wlp5s0) as default for IPv6 routing and DNS
Dec 17 16:58:31 omarsarchernitro5 NetworkManager[574]: <info>  [1734472711.0555] dhcp6 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 16:58:29 omarsarchernitro5 wpa_supplicant[618]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=87800
Dec 17 16:58:28 omarsarchernitro5 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Dec 17 16:58:27 omarsarchernitro5 kernel: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20241106151414
Dec 17 16:58:27 omarsarchernitro5 kernel: Bluetooth: hci0: Failed to write uhw reg(-110)
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.7547] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 17 16:58:26 omarsarchernitro5 systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 17 16:58:26 omarsarchernitro5 systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 17 16:58:26 omarsarchernitro5 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3447] device (wlp5s0): Activation: successful, device activated.
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3445] manager: NetworkManager state is now CONNECTED_SITE
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3443] device (wlp5s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3442] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3430] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3325] policy: set 'Versil' (wlp5s0) as default for IPv4 routing and DNS
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.3319] dhcp4 (wlp5s0): state changed new lease, address=10.0.0.49
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.1148] dhcp4 (wlp5s0): state changed new lease, address=10.0.0.49, acd pending
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.0590] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 16:58:26 omarsarchernitro5 NetworkManager[574]: <info>  [1734472706.0587] device (wlp5s0): state change: config -> ip-config (reason 'none', managed-type: 'full')

Edit: the dual-boot voodo ritual worked and fixed the problem, but i am keeping this up as problems usually occur a week or 2 after install

Last edited by Omarz2012 (2024-12-17 22:11:55)

Offline

#58 2024-12-17 22:14:42

seth
Member
Registered: 2012-09-03
Posts: 60,378

Re: resuming arch linux from sleep is not working properly

Dec 17 16:58:36 omarsarchernitro5 kernel: usb 1-4: Failed to suspend device, error -110
Dec 17 16:58:27 omarsarchernitro5 kernel: Bluetooth: hci0: Failed to write uhw reg(-110)

And what is usb 1-4 ? Looks very much like bluetooth to me?

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

Offline

#59 2024-12-18 22:00:03

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

seth wrote:
Dec 17 16:58:36 omarsarchernitro5 kernel: usb 1-4: Failed to suspend device, error -110
Dec 17 16:58:27 omarsarchernitro5 kernel: Bluetooth: hci0: Failed to write uhw reg(-110)

And what is usb 1-4 ? Looks very much like bluetooth to me?

I don't really know, also for some reason now my computer is having a hit or miss situation. every time  I boot up my computer, the current boot will either only work with resume one time and then fail with the suspend entry being the last message and then 

Dec 18 16:48:04 omarsarchernitro5 wpa_supplicant[614]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Dec 18 16:48:04 omarsarchernitro5 wpa_supplicant[614]: nl80211: deinit ifname=wlp5s0 disabled_11b_rates=0
Dec 18 16:48:04 omarsarchernitro5 wpa_supplicant[614]: wlp5s0: CTRL-EVENT-DSCP-POLICY clear_all

30 seconds later or work flawlessly every single time. there might be a pattern as it seems to alternate but also there is this weird little quirk where if it fails and you force poweroff, turn it back on and then reboot through the OS, it is guaranteed that the boot after this step will work flawlessly, also if you don't do these steps after a fail it will continue until you follow this proccedure

Offline

#60 2024-12-18 22:12:40

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

journalctl with broken boot: http://0x0.st/XCuE.txt
journalctl with non broken boot: http://0x0.st/XCuI.txt
turns out one difference between a broken sleep and a non broken sleep that I found is the usb 1-4 thing failing to sleep so you were right in some way

Offline

#61 2024-12-23 19:25:45

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

how do i allow user sessions to freeze.

Offline

#62 2024-12-23 21:27:10

seth
Member
Registered: 2012-09-03
Posts: 60,378

Re: resuming arch linux from sleep is not working properly

https://gitlab.archlinux.org/archlinux/ … type=heads

usr/lib/systemd/system/systemd-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-homed.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-hybrid-sleep.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend-then-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf

However (sorry for the delay) this won't help if and since

turns out one difference between a broken sleep and a non broken sleep that I found is the usb 1-4 thing failing to sleep so you were right in some way

Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: new high-speed USB device number 2 using xhci_hcd
Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: New USB device found, idVendor=04ca, idProduct=3802, bcdDevice= 1.00
Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: New USB device strings: Mfr=5, Product=6, SerialNumber=7
Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: Product: Wireless_Device
Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: Manufacturer: MediaTek Inc.
Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: SerialNumber: 000000000
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: reset high-speed USB device number 2 using xhci_hcd
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: device firmware changed
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: USB disconnect, device number 2
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: new high-speed USB device number 3 using xhci_hcd
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: New USB device found, idVendor=04ca, idProduct=3802, bcdDevice= 1.00
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: New USB device strings: Mfr=5, Product=6, SerialNumber=7
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: Product: Wireless_Device
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: Manufacturer: MediaTek Inc.
Dec 18 16:47:31 omarsarchernitro5 kernel: usb 1-4: SerialNumber: 000000000
Dec 18 16:47:46 omarsarchernitro5 kernel: usb 1-4: Failed to suspend device, error -110
Dec 18 16:47:58 omarsarchernitro5 kernel: usb 1-4: Failed to suspend device, error -110

So I'm gonna challenge https://bbs.archlinux.org/viewtopic.php … 7#p2214567 as the supposingly "good" boot (which doesn't fail suspending usb 1-4) has

Dec 17 20:40:20 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 10) timeout
Dec 17 20:40:20 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:40:20 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:40:20 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:40:20 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 17 20:41:35 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 6) timeout
Dec 17 20:41:35 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:41:35 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:41:35 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:41:35 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 17 20:41:54 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 9) timeout
Dec 17 20:41:54 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:41:54 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:41:54 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:41:54 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 17 20:44:05 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 8) timeout
Dec 17 20:44:05 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:44:05 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:44:05 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:44:05 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 17 20:44:33 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 2) timeout
Dec 17 20:44:33 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:44:33 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:44:33 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:44:33 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
Dec 17 20:56:02 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: Message 00020007 (seq 2) timeout
Dec 17 20:56:02 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: dpm_run_callback(): pci_pm_resume returns -110
Dec 17 20:56:02 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: PM: failed to resume async: error -110
Dec 17 20:56:02 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
Dec 17 20:56:02 omarsarchernitro5 kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045

Blacklist the module, make sure it doesn't show up in the journal, see whether you still get the system to break on resume, post that journal.

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

Offline

#63 2024-12-23 22:57:35

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

seth wrote:

https://gitlab.archlinux.org/archlinux/ … type=heads

usr/lib/systemd/system/systemd-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-homed.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-hybrid-sleep.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend-then-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf

However (sorry for the delay) this won't help if and since

turns out one difference between a broken sleep and a non broken sleep that I found is the usb 1-4 thing failing to sleep so you were right in some way

Dec 18 16:46:44 omarsarchernitro5 kernel: usb 1-4: new...M Firmware Version: ____010000, Build Time: 20241106151045

Blacklist the module, make sure it doesn't show up in the journal, see whether you still get the system to break on resume, post that journal.

I said ONE difference, it is just something I noticed. also it might be because of the way I installed it as it doesn't happen on my original install? here is how I installed it:

  1. boot into windows and go through the setup so that windows recognizes the new nvme

  2. boot into my archiso USB and partition the new disk into 3 partitions with the first one being just a Microsoft reserved partition, the second one being the efi partition for my new arch install and the third one being the root for my new arch install, I did not have any partition for swap as I didn't think I would need it but now I am having second thoughts

  3. mount the root partition onto /mnt and the efi partition onto /mnt/boot/efi

  4. this might be of interest, for pacstrapping I used the following command 

     pacstrap -K /mnt base linux linux headers linux-firmware sof-firmware efibootmgr grub e2fsprogs amd-ucode sudo networkmanager base-devel vim nano openssh man man-db man-pages texinfo

  5. generated fstab with the -U flag so that it does not break when booting up because of the pseudorandom naming of the disks every time I boot up the computer

  6. then i chroot, install os-prober and set timezone to America/Toronto

  7. I then sync system clock, generate CA,GB and US locales for english (all utf-8) and set the lang to CA

  8. set hostname

  9. set root password

  10. create main user in group wheel,set the visudo stuff to allow wheel to use sudo and set password for main user

  11. enable NetworkManager to start next boot

  12. install and enable chrony to start next boot

  13. edit /etc/grub/default to have recovery mode on, os prober on and remove the quiet from kernel parameters

  14. generate grub config and exit chroot

  15. run umount -a and reboot

  16. testing sleep, it works.

  17. install sddm, plasma, dolphin and git

  18. broken

  19. install nvidia drivers and set kernel parameter to not save video memory allocations.

  20. still broken

Will test blacklisting later. also this only happens when i use a GUI, when using TUI the problem does not happen even though the journalctl literally just stops and as always, LTS works. thought that it was the same problem as https://gitlab.archlinux.org/archlinux/ … /issues/95 but the key difference is that the problem is not solved with 6.11.9 on my side.

Last edited by Omarz2012 (2024-12-23 23:41:10)

Offline

#64 2024-12-25 21:25:57

Omarz2012
Member
From: Oshawa, Canada
Registered: 2024-10-19
Posts: 86
Website

Re: resuming arch linux from sleep is not working properly

i can confirm that it is something wrong with how I installed it as when using an automated script like archinstall, the installation was able to sleep and resume effortlessly

Offline

#65 2024-12-26 23:13:59

seth
Member
Registered: 2012-09-03
Posts: 60,378

Re: resuming arch linux from sleep is not working properly

The mt7921e problems won't hinge on the way you intalled the system - what kernel are you currently running and do you use the wifi and notably bluetooth at all?

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

Offline

Pages: 1 2 3

Board footer

Powered by FluxBB