Can't wake from sleep

A-Fellow-Human · 2023-03-26 08:47:34

Sorry, haven't really been bothered to try and fix this issue, so I've let this go dead for a month.

seth wrote:

https://wiki.archlinux.org/title/Solid_ … nd_support

I've had iommu=soft as kernel parameter the entire time, it seems, so I guess it doesn't work.

seth wrote:

Otherwise:
Cut the multi-user.target.
Only boot the rescue.target, suspend and resume from there.

Not working.

seth wrote:

Also try rtcwake, https://man.archlinux.org/man/core/util … cwake.8.en

I've been using "rtcwake -m mem -s 10"
When in GUI, my PC just turns on immediately and the output is "rtcwake: write error"
When in rescue.target, it turns off and the fans and RGB turn on as expected, but still no signal.

seth · 2023-03-27 15:15:31

Wrt. the earlier findings: can you suspend from the current archlinux install iso?

seth wrote:

Double and triple check that windows fast-start is indeed still disabled.

A-Fellow-Human · 2023-04-04 12:59:36

seth wrote:

Wrt. the earlier findings: can you suspend from the current archlinux install iso?

Still working, even with "rtcwake -m mem -s 10".

seth wrote:

Double and triple check that windows fast-start is indeed still disabled.

It is definitely off.

seth · 2023-04-04 14:03:38

So it's not the kernel (install iso), it's not a service (rescue.target) it's not windows, it's unlikely the nvidia kernel module
=> https://wiki.archlinux.org/title/Solid_ … leshooting

nvme_core.default_ps_max_latency_us=0 iommu=soft

A-Fellow-Human · 2023-04-05 16:03:06

Unfortunately adding that kernel parameter didn't fix things. Worth noting that I use a Crucial P2, which AFAIK doesn't have APST issues anyways.

seth · 2023-04-05 16:19:06

Boot the install iso, make sure to mount the nvme somewhere and "less /etc/securetty" just to have some file there open.
Then try to suspend/resume.

Quadruple-check that windows isn't hibernating.
If you can't suspend from the rescue target but can from the usb system and it's not the nvidia kernel module either (blacklist it and "nomodeset" the rescue.target in doubt), we're runnig out of meaningful differences (except the ACPI mayb behave differently which is why you should then quituple-check for windows fast-start)

A-Fellow-Human · 2023-04-06 14:47:00

I've tried mounting the NVME onto /arch, then doing "less /arch/etc/securetty" and the live USB ISO was able to boot.

I've gone over to Windows and shut down from there, but sleep still isn't working.

seth · 2023-04-06 15:13:01

the live USB ISO was able to boot

???
The point is to see whether you can resume from suspend there.
Eg. hibernation would not work from the iso, you'd just reboot.

A-Fellow-Human · 2023-04-06 15:44:02

Oh sorry, I meant I was able to sleep, then start from sleep while having a terminal page running "less /arch/etc/securetty"

Last edited by A-Fellow-Human (2023-04-06 15:48:09)

A-Fellow-Human · 2023-04-07 14:59:38

Do you think it's worth trying booting my install on a different device? I happen to have a 128 GB HDD, so I could copy everything except /home over and see if sleep from there works.

If it works, then we'd conclusively show that there's an issue with either Windows or the NVME drive.

seth · 2023-04-07 15:41:46

Windows would not be affected by the boot device (the problem is w/ the firmware resp. the ACPI entries) but getting the nvme out of the system would be interesting.

A-Fellow-Human · 2023-04-28 10:46:59

I was going to try this out, but unfortunately my hard drive seems to have died.

Anything I should do to test, or should I but another hard drive to try booting from?

seth · 2023-04-28 13:13:54

Do you want to buy another drive?

But at this point I can't come up w/ a cause other than the nvme.
As you likely(?) intended to install arch on the other drive from scratch, you could try the same w/ the nvme to rule out that it's not some weird change or freak accident before you invest money in another SSD.

A-Fellow-Human · 2023-05-31 05:06:14

Hi sorry, didn't end up responding to you.

I ended up buying a 128 GB USB to try installing to. I also added a partition to test out my current NVME drive.

For the NVME drive, I took a backup of my installation and rsync'd it to my partition. My PC was unable to wake from sleep.

For my USB, I didn't have enough storage space to install my entire backup, so I used to bottom-to-top method (backup all pacman native packages, run archinstall, re-install native packages) and my PC was able to wake.

Ideally I would also try to install my bottom-to-top OS onto my partition, but for some reason with authentication I couldn't boot. I decided against fixing it since this seems conclusive enough.

So we should be able to expect that there is some issue with the NVME itself, and I should buy a new NVME? Or is it possible that the problem lies in the NVME driver or the PCIe slot?

seth · 2023-05-31 06:02:13

some issue with the NVME itself … Or … possible that the problem lies in the NVME driver or the PCIe slot

or a combination of all.
The nvme probably doesn't power up or re-initialize, but there's no way to tell/guarantee that the replacement won't run into the same situation.

Are there firmware updates for the system (BIOS/UEFI) or the nvme available?

A-Fellow-Human · 2023-05-31 06:45:38

Actually, coming back to this - I was able to get the "bottom-to-top" installation working on my NVME. Now, when I sleep from this installation, the screen turns off for a few seconds, some text (appearing to be dmesg) appears, and then I land back at my home page.

I then ran sudo dmesg, which gave output as follows: https://pastebin.com/P8p2e8NK

This issue persists when I replaced nvidia-open-dkms with nvidia-dkms, and when I tried putting "options nvidia NVreg_PreserveVideoMemoryAllocations=0" in /etc/modprobe.d/nvidia-power-management.conf.

This is bizarre behaviour. I have to emphasise that this does not happen in my USB installation, and that sleeping and waking still works perfectly fine from there. There don't seem to be any NVidia-related output logs during the sleep and wake process.

Any idea what might be going on? Is this some weird interaction with an NVME issue and an NVidia driver bug?

seth · 2023-05-31 07:06:38

[   57.318110] NVRM: GPU 0000:08:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
[   57.318115] nvidia 0000:08:00.0: PM: pci_pm_suspend(): nv_pmops_suspend+0x0/0x30 [nvidia] returns -5
[   57.318210] nvidia 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -5
[   57.318237] nvidia 0000:08:00.0: PM: failed to suspend async: error -5

Try to disable https://download.nvidia.com/XFree86/Lin … ement.html

A-Fellow-Human · 2023-05-31 07:23:34

Turns out nvidia-suspend.service, nvidia-hibernate.service and nvidia-resume.service were all disabled on my bottom-to-top installation. Interestingly enough, running "sudo systemctl start nvidia-suspend.service", or running "sudo systemctl enable nvidia-suspend.service" and then suspending, results in not being able to wake from sleep.

There isn't a firmware update for my NVME drive, but there is one for my motherboard's BIOS. I'm currently in the process of installing it.

Last edited by A-Fellow-Human (2023-05-31 07:24:44)

seth · 2023-05-31 07:26:41

Did you try to completely disable the VRAM preservation?

A-Fellow-Human · 2023-05-31 07:32:05

Well, I tried to do so by putting "options nvidia NVreg_PreserveVideoMemoryAllocations=0" in /etc/modprobe.d/nvidia-power-management.conf. Is that the correct way of disabling VRAM preservation?

(Also worth noting: Updating BIOS did not fix issues. If I disable nvidia-suspend.service on my main installation, I get the same error messages as I do on my bottom-to-top installation.)

Maybe nvidia-suspend is working as intended when enabled but the NVME isn't?

Last edited by A-Fellow-Human (2023-05-31 07:33:07)

seth · 2023-05-31 07:35:32

You'll in doubt also have to rebuild the initramfs.

A-Fellow-Human · 2023-05-31 07:46:36

Yep, that finally solved the issue. After disabling VRAM preservation on my main installation, suspend is working perfectly fine.

Thank you for your help!

seth · 2023-05-31 11:52:43

Where did you store the VRAM? tmpfs or somewhere on the nvme…?

Arch Linux

#26 2023-03-26 08:47:34

Re: Can't wake from sleep

#27 2023-03-27 15:15:31

Re: Can't wake from sleep

#28 2023-04-04 12:59:36

Re: Can't wake from sleep

#29 2023-04-04 14:03:38

Re: Can't wake from sleep

#30 2023-04-05 16:03:06

Re: Can't wake from sleep

#31 2023-04-05 16:19:06

Re: Can't wake from sleep

#32 2023-04-06 14:47:00

Re: Can't wake from sleep

#33 2023-04-06 15:13:01

Re: Can't wake from sleep

#34 2023-04-06 15:44:02

Re: Can't wake from sleep

#35 2023-04-07 14:59:38

Re: Can't wake from sleep

#36 2023-04-07 15:41:46

Re: Can't wake from sleep

#37 2023-04-28 10:46:59

Re: Can't wake from sleep

#38 2023-04-28 13:13:54

Re: Can't wake from sleep

#39 2023-05-31 05:06:14

Re: Can't wake from sleep

#40 2023-05-31 06:02:13

Re: Can't wake from sleep

#41 2023-05-31 06:45:38

Re: Can't wake from sleep

#42 2023-05-31 07:06:38

Re: Can't wake from sleep

#43 2023-05-31 07:23:34

Re: Can't wake from sleep

#44 2023-05-31 07:26:41

Re: Can't wake from sleep

#45 2023-05-31 07:32:05

Re: Can't wake from sleep

#46 2023-05-31 07:35:32

Re: Can't wake from sleep

#47 2023-05-31 07:46:36

Re: Can't wake from sleep

#48 2023-05-31 11:52:43

Re: Can't wake from sleep

Board footer