[SOLVED] Unable to un-sleep computer after putting it to sleep

LowkeyUndergrounder · 2022-07-21 20:30:11

Greetings, when i put my new arch installation (running KDE with Nvidia-Open graphics, tested both Wayland and Xorg) to sleep, it refuses to boot back up from the ram; i am unsure on what logs i should share so i will instead detail it via text here, trying to put the computer back-on and out of sleep seems to work for a second (when a key is pressed on the keyboard), the power light comes on, the Num-Lock and other lock lights start functioning on the keyboard and the monitor either powers on for a second (back-light only) or does not power on at all and after a measly 5-6 seconds, the lock lights stop functioning and the system soft-locks until reboot, trying to switch desktop environments etc. do not yield any result; system fully halts.

Last edited by LowkeyUndergrounder (2022-08-10 10:09:19)

seth · 2022-07-21 21:24:46

https://01.org/node/3721

trying to switch desktop environments etc. do not yield any result

Did you try
- the multi-user.target (not GUI running at all)
- booting w/ "nomodeset" (what implies "no GUI", it'll fail to start w/o KMS)
- the not-open nvidia driver

When this happens, see whether you can reboot the system (maybe before the keyboard stops responding) w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) or even just hitting ctrl+alt+del a lot of times and after the reboot check the journal of the previous boot (sudo journalctl -b -1)

LowkeyUndergrounder · 2022-07-21 22:06:24

seth wrote:

https://01.org/node/3721
trying to switch desktop environments etc. do not yield any result
Did you try
- the multi-user.target (not GUI running at all)
- booting w/ "nomodeset" (what implies "no GUI", it'll fail to start w/o KMS)
- the not-open nvidia driver
When this happens, see whether you can reboot the system (maybe before the keyboard stops responding) w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) or even just hitting ctrl+alt+del a lot of times and after the reboot check the journal of the previous boot (sudo journalctl -b -1)

Actually, i was able to verify that i can switch between desktop environments when the computer is on a half-not working state, i was also able to verify that the computer indeed runs when the screen and num-keys are seemingly not functioning (by pressing the power button and enter, triggering a reboot) i think i must re-phrase what works and what does not when the screen is off; when i do CTRL + ALT + F12, i am able to toggle lock-states but there is no screen, CTRL + ALT + F1/F2 = No screen but able to confirm the pc is functioning, lock keys do not work at all. I did this verification on the proprietary nvidia-dkms package, i will try it on the open source nvidia-open package to verify the consistence of the said states and will update on whether it changes anything or not, i'll also be looking into the website and the troubleshooting methods provided by you.

Edit: Tried the same on the open-source (nvidia-open) drivers and didn't work (the same being switching between DE's and rebooting pc while screen is off) but i think it has to do with the general consistency of the bug, not with the difference between nvidia-open nor nvidia-dkms. Again, back to start, will try the other suggestions of yours.

Edit 2: The pc decided not to shutdown a minute ago, do not know what that was about; it was just stuck on the announced shutdown screen...

Edit 3: Something weird that i think may help on solving what the hell is going on here; i was testing a bit of half-life to validate the stability of my system and the system after a few minutes of playing decided to go all the way to 1 fps (the whole DE) and it would put almost every command of mine on hold for around a minute (lock-commands like num-lock and caps-lock, similar to the one that happens when resuming sleep), kind of like running the whole operating system on a toaster, even worse probably. I have no idea on what causes this but i was and am on X11 right now.

Last edited by LowkeyUndergrounder (2022-07-21 22:52:01)

LowkeyUndergrounder · 2022-07-21 23:27:27

No luck, tried many things and no avail; 99% certain driver problem. Is it possible for anybody to send instructions on how i can provide accurate logs on the matter?

seth · 2022-07-22 06:02:43

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

will upload the journal of the previous boot ("-1") to a pastebin service and if you suspect that the system is still operating after the S3/resume, you can perhaps also ssh into it to inspect it "live"

LowkeyUndergrounder · 2022-07-22 11:48:42

seth wrote:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
will upload the journal of the previous boot ("-1") to a pastebin service and if you suspect that the system is still operating after the S3/resume, you can perhaps also ssh into it to inspect it "live"

Here you go
https://0x0.st/ojbh.txt

JoeyCorleone · 2022-07-22 12:12:32

Does this help?

LowkeyUndergrounder · 2022-07-22 14:16:14

JoeyCorleone wrote:

Does this help?

Either i am doing something wrong or this just plain old does not work, i tried manually adding the lines to grub and using the provided script there and both of them cause the computer to soft-lock in the "loading initial ramdisk" state, i'll try the same with the "quiet" not in there and will see if the system actually locks or well, progresses until a certain stage...

Edit: Nope, it just freezes on "loading initial ramdisk".

Last edited by LowkeyUndergrounder (2022-07-22 14:18:32)

seth · 2022-07-22 15:29:18

What is the output of the DSDT grep and what exactly do you add to the kernel parameters?
The journal uses nvidia-open, since the problem is clearly the nvidia kernel module, please provide a journal for the regular-ass nvidia driver.
Also try the LTS kernel.

LowkeyUndergrounder · 2022-07-22 17:16:04

seth wrote:

What is the output of the DSDT grep and what exactly do you add to the kernel parameters?
The journal uses nvidia-open, since the problem is clearly the nvidia kernel module, please provide a journal for the regular-ass nvidia driver.
Also try the LTS kernel.

Wo-wie, the LTS kernel seems to have fixed the issue but the lts kernel itself will be pretty hard for me to fully switch to and in order to make way for a better future for open-source software, i think i should continue trying to debug why the normal kernel doesn't work, i am unable to get what you mean by "What is the output of the DSDT grep and what exactly do you add to the kernel parameters?" and "please provide a journal for the regular-ass nvidia driver.", can you explain what you mean on them a bit more, please?

Last edited by LowkeyUndergrounder (2022-07-22 17:21:55)

seth · 2022-07-22 20:52:30

what you mean by "What is the output of the DSDT grep and what exactly do you add to the kernel parameters?"

JoeyCorleone linked https://wiki.archlinux.org/title/NVIDIA … om_suspend and you responded

i tried manually adding the lines to grub and using the provided script there and both of them cause the computer to soft-lock

so the question is, how *exactly* did you interpret the wiki advice?

"please provide a journal for the regular-ass nvidia driver.", can you explain what you mean on them

The journal shows you using https://archlinux.org/packages/extra/x8 … idia-open/ and you suggested

I did this verification on the proprietary nvidia-dkms package, i will try it on the open source nvidia-open package

so it would be intersting to see the behavior of the "proprietary nvidia-dkms" (and quite frankly also now w/ the lts driver) in the journals of the relevant boots.

LowkeyUndergrounder · 2022-08-06 15:55:02

Back with the same problem, nvidia-open-dkms package on linux-zen kernel; i think it has to do something with nvidia drivers rather than the kernel... Here are the logs

 Aug 06 18:43:46 archie plasmashell[2284]: src/clientdll/applicationmanager.cpp (8201) : Assertion Failed: BStartUpdateDepotsJob: 1172470 missing required app 0
Aug 06 18:43:46 archie plasmashell[2284]: src/clientdll/applicationmanager.cpp (8201) : Assertion Failed: BStartUpdateDepotsJob: 1172470 missing required app 1826330
Aug 06 18:43:46 archie plasmashell[2284]: src/clientdll/applicationmanager.cpp (8201) : Assertion Failed: BStartUpdateDepotsJob: 1172470 missing required app 1826330
Aug 06 18:43:47 archie plasmashell[2284]: Installing breakpad exception handler for appid(steam)/version(1658944613)
Aug 06 18:43:47 archie plasmashell[2284]: Installing breakpad exception handler for appid(steam)/version(1658944613)
Aug 06 18:43:47 archie plasmashell[2284]: Installing breakpad exception handler for appid(steam)/version(1658944613)
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1288] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1288] manager: NetworkManager state is now ASLEEP
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1289] device (enp16s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Aug 06 18:43:48 archie dbus-daemon[1593]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=1598 comm="/usr/bin/NetworkManager --no-daemon")
Aug 06 18:43:48 archie systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 06 18:43:48 archie kded5[1742]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Aug 06 18:43:48 archie dbus-daemon[1593]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 06 18:43:48 archie systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 06 18:43:48 archie audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1356] device (enp16s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Aug 06 18:43:48 archie kernel: audit: type=1130 audit(1659800628.134:90): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1477] dhcp4 (enp16s0): canceled DHCP transaction
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1477] dhcp4 (enp16s0): activation: beginning transaction (timeout in 45 seconds)
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1477] dhcp4 (enp16s0): state changed no lease
Aug 06 18:43:48 archie NetworkManager[1598]: <info>  [1659800628.1525] device (enp16s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 06 18:43:48 archie kernel: r8169 0000:10:00.0 enp16s0: Link is Down
Aug 06 18:43:48 archie kscreenlocker_greet[3175]: Qt: Session management error: networkIdsList argument is NULL
Aug 06 18:43:48 archie PackageKit[1937]: get-updates transaction /3_eaaacdbc from uid 1000 finished with success after 0ms
Aug 06 18:43:48 archie kscreenlocker_greet[3175]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Aug 06 18:43:48 archie kernel: NVRM rmapiUnmapWithSecInfo: Nv04Unmap: ummap failed; status: Requested object not found [NV_ERR_OBJECT_NOT_FOUND] (0x00000057)
Aug 06 18:43:48 archie kernel: NVRM serverFreeResourceTree: hObject 0xbeee0100 not found for client 0xc1d00055
Aug 06 18:43:48 archie kernel: NVRM rmapiUnmapWithSecInfo: Nv04Unmap: ummap failed; status: Requested object not found [NV_ERR_OBJECT_NOT_FOUND] (0x00000057)
Aug 06 18:43:48 archie kernel: NVRM serverFreeResourceTree: hObject 0xbeef0100 not found for client 0xc1d00055
Aug 06 18:43:48 archie kscreenlocker_greet[3175]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Aug 06 18:43:48 archie openrazer-daemon[1986]: 2022-08-06 18:43:48 | razer.device0                  | INFO     | Suspending RazerDeathAdderEssential
Aug 06 18:43:48 archie systemd[1]: Reached target Sleep.
Aug 06 18:43:48 archie systemd[1]: Starting System Suspend...
Aug 06 18:43:48 archie systemd-sleep[3193]: Entering sleep state 'suspend'...
Aug 06 18:43:48 archie kernel: PM: suspend entry (deep)

(System does not go to sleep, rather just stays on... Unable to un-sleep)

Here are more logs from another session

 Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9093] manager: sleep: sleep requested (sleeping: n>
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9094] manager: NetworkManager state is now ASLEEP
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9096] device (enp16s0): state change: activated ->>
Aug 06 16:30:29 archie kded5[1741]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Aug 06 16:30:29 archie dbus-daemon[1597]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatc>
Aug 06 16:30:29 archie systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 06 16:30:29 archie dbus-daemon[1597]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 06 16:30:29 archie systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 06 16:30:29 archie audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager->
Aug 06 16:30:29 archie kernel: audit: type=1130 audit(1659792629.916:90): pid=1 uid=0 auid=4294967295 ses=429496729>
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9177] device (enp16s0): state change: deactivating>
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9284] dhcp4 (enp16s0): canceled DHCP transaction
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9284] dhcp4 (enp16s0): activation: beginning trans>
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9285] dhcp4 (enp16s0): state changed no lease
Aug 06 16:30:29 archie NetworkManager[1602]: <info>  [1659792629.9312] device (enp16s0): state change: disconnected>
Aug 06 16:30:29 archie kernel: r8169 0000:10:00.0 enp16s0: Link is Down
Aug 06 16:30:29 archie kscreenlocker_greet[2173]: Qt: Session management error: networkIdsList argument is NULL
Aug 06 16:30:30 archie PackageKit[1930]: get-updates transaction /3_ddadaadc from uid 1000 finished with success af>
Aug 06 16:30:30 archie kscreenlocker_greet[2173]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/con>
Aug 06 16:30:30 archie kscreenlocker_greet[2173]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/con>
Aug 06 16:30:30 archie openrazer-daemon[2015]: 2022-08-06 16:30:30 | razer.device0                  | INFO     | Su>
Aug 06 16:30:30 archie systemd[1]: Reached target Sleep.
Aug 06 16:30:30 archie systemd[1]: Starting System Suspend...
Aug 06 16:30:30 archie systemd-sleep[2192]: Entering sleep state 'suspend'...

Edit: This is an entirely new installation, running on BTRFS with LUKS so the file-system cannot for some reason be the culprit behind this...
Edit 2: Everything accept sleeping the computer seems to function on the zen kernel, i'll also try the lts nvidia drivers now. (Well i would but i do not think the lts driver supports anything other than the lts kernel )

Last edited by LowkeyUndergrounder (2022-08-06 16:08:33)

seth · 2022-08-06 19:54:37

https://archlinux.org/packages/extra/x8 … idia-dkms/

LowkeyUndergrounder · 2022-08-06 21:11:07

seth wrote:

https://archlinux.org/packages/extra/x8 … idia-dkms/

It surprisingly seemed to have worked but i will need to further-test the consistency of the result as the open-source dkms package also worked for a while before breaking from what i am able to recall...

LowkeyUndergrounder · 2022-08-10 00:02:43

LowkeyUndergrounder wrote:

seth wrote:
https://archlinux.org/packages/extra/x8 … idia-dkms/
It surprisingly seemed to have worked but i will need to further-test the consistency of the result as the open-source dkms package also worked for a while before breaking from what i am able to recall...

Was not able to see any errors happen since switching to the proprietary nvidia-dkms package; yet.

seth · 2022-08-10 05:45:54

https://github.com/NVIDIA/open-gpu-kern … issues/223
https://github.com/NVIDIA/open-gpu-kern … /issues/94

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2022-07-21 20:30:11

[SOLVED] Unable to un-sleep computer after putting it to sleep

#2 2022-07-21 21:24:46

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#3 2022-07-21 22:06:24

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#4 2022-07-21 23:27:27

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#5 2022-07-22 06:02:43

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#6 2022-07-22 11:48:42

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#7 2022-07-22 12:12:32

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#8 2022-07-22 14:16:14

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#9 2022-07-22 15:29:18

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#10 2022-07-22 17:16:04

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#11 2022-07-22 20:52:30

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#12 2022-08-06 15:55:02

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#13 2022-08-06 19:54:37

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#14 2022-08-06 21:11:07

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#15 2022-08-10 00:02:43

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

#16 2022-08-10 05:45:54

Re: [SOLVED] Unable to un-sleep computer after putting it to sleep

Board footer