Recently not waking from suspend / system locks up

General system Kernel, boot, graphics & hardware
1

I’m fairly new to Endeavour, I’ve been running it for several months now and while it had been working just fine it has recently decided to have problems with suspend/sleep. I have been trying to search around and figure it out, but I’m at a complete loss as to what caused it or how to fix it.

I’m running on an ASUS TUF A15-FA507NUR laptop. As I said, suspend has been working just fine until very recently. Now, completely randomly, when it goes into suspend I get a couple of possible outcomes.

  1. (most often) The system appears like it is going to wake up, keyboard lights up, cursor appears, but the screen stays black. Attempting to switch TTYL does nothing. Only recourse is a hard power down at which point the system forgets some settings, browser completely loses all history and dumps any current tabs and fails to sync said tabs/history to my other devices.
  2. The system appears to wakes up as above, but after hard power cycle the browser and settings are intact or able to be auto restored.
  3. The system looks like it got stuck trying to go to sleep. System LED stays solid, keyboard lights on and respond to brightness controls, but nothing else works.
  4. The system appears to wake up, but I only get a cursor on a black screen. Switching TTYL actually works and I am able to command shutdown or reboot.
  5. (least often) The system LED slow blinks showing it is in suspend state, but will not wake up.

At first it appeared related to running certain software, but when I’ve tried to recreate the problem I cannot. Once again today, it happened when I was using RustDesk connected to another machine and walked away for a while, the system looks like it was trying to go to sleep, but the keyboard was lit, screen was black, system/power LEDs were solid and yet nothing would respond.

FWIW I am dual booted, but each OS resides on separate drives and they do not share bootloader.

I’m not sure what all info/logs will help, but I’ll start with this
https://0x0.st/8Yas.txt

image
image865×500 82.8 KB

image
image1546×993 242 KB

Also adding this from journalctl, the system woke up just fine this morning and then had problems hours later.

$ journalctl --since today --grep=suspend
Jun 01 10:35:57 Newt kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 01 10:35:57 Newt kernel: PM: suspend exit
Jun 01 10:35:57 Newt systemd-sleep[110162]: System returned from sleep operation ‘suspend’.
Jun 01 10:35:58 Newt systemd[1]: systemd-suspend.service: Deactivated successfully.
Jun 01 10:35:58 Newt systemd[1]: Finished System Suspend.
Jun 01 10:35:58 Newt systemd[1]: systemd-suspend.service: Consumed 1.299s CPU time, 4.1M memory peak.
Jun 01 10:35:58 Newt systemd[1]: Reached target Suspend.
Jun 01 10:35:58 Newt systemd-logind[930]: Operation ‘suspend’ finished.
Jun 01 10:35:58 Newt systemd[1]: Stopped target Suspend.
Jun 01 10:35:58 Newt logger[110412]: <13>Jun 1 10:35:58 suspend: nvidia-resume.service
– Boot 6fc8afb1fbc74bc3ab3e007092ae1c97 –
Jun 01 06:37:28 Newt kernel: Low-power S0 idle used by default for system suspend
Jun 01 06:37:28 Newt kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
Jun 01 06:37:28 Newt kernel: nvme 0000:05:00.0: platform quirk: setting simple suspend
Jun 01 13:09:17 Newt systemd-logind[923]: The system will suspend now!
Jun 01 13:09:17 Newt systemd[1]: Starting NVIDIA system suspend actions…
Jun 01 13:09:17 Newt suspend[61770]: nvidia-suspend.service
Jun 01 13:09:17 Newt logger[61770]: <13>Jun 1 13:09:17 suspend: nvidia-suspend.service
Jun 01 13:09:23 Newt systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jun 01 13:09:23 Newt systemd[1]: Finished NVIDIA system suspend actions.
Jun 01 13:09:23 Newt systemd[1]: nvidia-suspend.service: Consumed 3.525s CPU time, 1.1G memory peak.
Jun 01 13:09:23 Newt systemd[1]: Starting System Suspend…
Jun 01 13:09:23 Newt systemd-sleep[62211]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 01 13:09:23 Newt systemd-sleep[62211]: Performing sleep operation ‘suspend’…
Jun 01 13:09:23 Newt kernel: PM: suspend entry (s2idle)
Jun 01 13:13:00 Newt kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 01 13:13:00 Newt systemd-sleep[62211]: System returned from sleep operation ‘suspend’.
Jun 01 13:13:00 Newt kernel: PM: suspend exit
Jun 01 13:13:03 Newt systemd[1]: systemd-suspend.service: Deactivated successfully.
Jun 01 13:13:03 Newt systemd[1]: Finished System Suspend.
Jun 01 13:13:03 Newt systemd[1]: systemd-suspend.service: Consumed 2.565s CPU time, 3.9M memory peak.
Jun 01 13:13:03 Newt systemd[1]: Reached target Suspend.
Jun 01 13:13:03 Newt systemd-logind[923]: Operation ‘suspend’ finished.
Jun 01 13:13:03 Newt systemd[1]: Stopped target Suspend.
Jun 01 13:13:03 Newt logger[62545]: <13>Jun 1 13:13:03 suspend: nvidia-resume.service
Jun 01 15:23:35 Newt systemd-logind[923]: The system will suspend now!
Jun 01 15:23:35 Newt systemd[1]: Starting NVIDIA system suspend actions…
Jun 01 15:23:35 Newt suspend[124178]: nvidia-suspend.service
Jun 01 15:23:35 Newt logger[124178]: <13>Jun 1 15:23:35 suspend: nvidia-suspend.service
Jun 01 15:23:40 Newt systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jun 01 15:23:40 Newt systemd[1]: Finished NVIDIA system suspend actions.
Jun 01 15:23:40 Newt systemd[1]: nvidia-suspend.service: Consumed 2.165s CPU time, 567.7M memory peak.
Jun 01 15:23:40 Newt systemd[1]: Starting System Suspend…
Jun 01 15:23:40 Newt systemd-sleep[124547]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 01 15:23:40 Newt systemd-sleep[124547]: Performing sleep operation ‘suspend’…
– Boot 42ee3b8292aa4a7d8d696dabc4417703 –
Jun 01 11:48:00 Newt kernel: Low-power S0 idle used by default for system suspend
Jun 01 11:48:01 Newt kernel: nvme 0000:05:00.0: platform quirk: setting simple suspend
Jun 01 11:48:01 Newt kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend

2

Do you have latest BIOS ? https://www.asus.com/laptops/for-gaming/tuf-gaming/asus-tuf-gaming-a15-2023/helpdesk_bios?model2Name=FA507NUR

Did you try latest Kernel 6.14?

Did you try previous LTS kernel? You can check when it was updated here, to see if it is aligned with the date you started to have problems: https://gitlab.archlinux.org/archlinux/packaging/packages/linux-lts/-/commits/main

3

Yes, I’ve had the latest BIOS (303 in this case) since I bought the laptop.

I have not tried the later kernel as there was a notice I read somewhere about instability being caused by utilizing more than one kernel so I’ve just kept with 6.12. Which was working prior anyhow and was/is the only kernel I have been using daily so I don’t see how that could be the problem.

Today I did a system update and it bumped my 6.12.32lts up to 6.12.33lts and my secondary kernel went from 6.14 to 6.15. I’m still concerned about that dual use kernel problem as I haven’t had time to really investigate it.

Despite there being a ridiculous load of things updated this week, the problem persists with suspend having a mixed bag of sometimes works, sometimes black screen, sometimes black with cursor, sometimes lets me log in and then black, sometimes lets me all the way back to functional desktop.

I even threw this at ChatGPT out of desperation and almost thought I was getting somewhere, but then no..no..problem remains if not slightly worse.

4

I do not know where did you get this notion, that using more than one kernel causes instability but this just not true. You can install multiple kernels, and they sleep on hard disk. When you boot , you boot only one of them. Other kernels continue to sleep. There is no situation, when 2 are active. So there is no difference if you have one or two.

Brief looking for Google of those words: ASUS TUF A15-FA507NUR arch linux suspend

Brings either AMD CPU related problems or Nvidia related problems.

I would go both routes to try to mitigate them.