System freezes randomly after resume from suspend

I have been using openSUSE for quite a while on a Intel NUC (NUC8i3BEH) and I am not done yet setting it up. My installation is as follows: openSUSE Leap 15.1 with GNOME, Linux version 4.12.14-lp151.28.52-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux) ). The hardware that didn’t came with the NUC: 16GB RAM, 256GB PCIe SSD and a 500GB HDD. The device boots from the HDD and the SSD has the fancy Chameleon OS, nothing is encrypted.
The first weeks of usage were done through a VNC and SSH setup, suspend and resume worked without any issues. Now I’m using a display connected through the HDMI port and I’m facing a strange behavior when telling the computer to sleep then trying to resume: It goes to sleep and the power button light starts blinking, then the power button or a key is pressed and it starts to resume, sometimes it fails. When it fails the fan and HDD start spinning, the Num Lock keyboard light turns on, the hard drive light indicator blinks once and then nothing but the fan spinning and the power indicator light. I don’t get any video signal, no keys combination work (I also tried switching between tty) and the keyboard light indicators can’t be switched either, I can’t access through SSH but is possible to ping and get responses for a brief time, only option left is force it to power off. Whenever resume doesn’t fail everything works properly.

I have done this so far trying to find a solution:

  1. Searched in /var/log/messages and found different messages for both resume cases:
  • Whenever it fails:
2020-06-14T21:36:20.392585-05:00 linux-y7h7 gnome-shell[3390]: Screen lock is locked down, not locking
2020-06-14T21:36:20.393564-05:00 linux-y7h7 /usr/lib/gdm/gdm-wayland-session[3379]: Window manager warning: Failed to set power save mode for output DP-1: Permiso denegado
2020-06-14T21:36:20.461512-05:00 linux-y7h7 gnome-software[5099]: no app for changed apps-menu@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:36:20.466232-05:00 linux-y7h7 gnome-software[5099]: no app for changed window-list@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:36:20.470022-05:00 linux-y7h7 gnome-software[5099]: no app for changed places-menu@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:36:20.470511-05:00 linux-y7h7 gnome-software[5099]: no app for changed launch-new-instance@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:36:21.453748-05:00 linux-y7h7 systemd[1]: Reached target Sleep.
2020-06-14T21:36:21.455055-05:00 linux-y7h7 systemd[1]: Starting Suspend...

  • The opposite situation:
2020-06-14T21:32:32.559120-05:00 linux-y7h7 gnome-software[5099]: no app for changed window-list@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:32:32.562708-05:00 linux-y7h7 gnome-software[5099]: no app for changed places-menu@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:32:32.563001-05:00 linux-y7h7 gnome-software[5099]: no app for changed launch-new-instance@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:32:32.568452-05:00 linux-y7h7 gnome-software[5099]: no app for changed apps-menu@gnome-shell-extensions.gcampax.github.com
2020-06-14T21:32:35.143710-05:00 linux-y7h7 gnome-shell[3390]: Screen lock is locked down, not locking
2020-06-14T21:32:35.143991-05:00 linux-y7h7 /usr/lib/gdm/gdm-wayland-session[3379]: Window manager warning: Failed to set power save mode for outp
ut DP-1: Permiso denegado
2020-06-14T21:32:40.323218-05:00 linux-y7h7 systemd-logind[950]: Delay lock is active (UID 1000/ldelgadillo, PID 4597/gnome-shell) but inhibitor timeout is reached.
2020-06-14T21:32:40.327007-05:00 linux-y7h7 systemd[1]: Reached target Sleep.
2020-06-14T21:32:40.327610-05:00 linux-y7h7 systemd[1]: Starting Suspend...
2020-06-14T21:32:40.340315-05:00 linux-y7h7 systemd-sleep[31426]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
2020-06-14T21:32:40.340842-05:00 linux-y7h7 systemd-sleep[31426]: Suspending system...
2020-06-14T21:32:45.208634-05:00 linux-y7h7 kernel:  1089.884365] PM: Syncing filesystems ... done.
2020-06-14T21:32:45.208648-05:00 linux-y7h7 kernel:  1089.885233] PM: Preparing system for sleep (mem)
2020-06-14T21:32:45.208687-05:00 linux-y7h7 kernel:  1089.886910] Freezing user space processes ... (elapsed 0.001 seconds) done.
2020-06-14T21:32:45.208690-05:00 linux-y7h7 kernel:  1089.888899] OOM killer disabled.
2020-06-14T21:32:45.208690-05:00 linux-y7h7 kernel:  1089.888900] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
2020-06-14T21:32:45.208691-05:00 linux-y7h7 kernel:  1089.889990] PM: Suspending system (mem)
2020-06-14T21:32:45.208691-05:00 linux-y7h7 kernel:  1089.890026] Suspending console(s) (use no_console_suspend to debug)
2020-06-14T21:32:45.208692-05:00 linux-y7h7 kernel:  1089.930658] wlan1: deauthenticating from f8:2d:c0:fc:44:76 by local choice (Reason: 3=DEAUT
H_LEAVING)
2020-06-14T21:32:45.208693-05:00 linux-y7h7 kernel:  1090.061072] sd 2:0:0:0: [sda] Synchronizing SCSI cache
2020-06-14T21:32:45.208693-05:00 linux-y7h7 kernel:  1090.062330] sd 2:0:0:0: [sda] Stopping disk
2020-06-14T21:32:45.208694-05:00 linux-y7h7 kernel:  1090.383481] e1000e: EEE TX LPI TIMER: 00000011
2020-06-14T21:32:45.208694-05:00 linux-y7h7 kernel:  1090.819259] PM: suspend of devices complete after 928.950 msecs
2020-06-14T21:32:45.208695-05:00 linux-y7h7 kernel:  1091.312381] PM: late suspend of devices complete after 493.124 msecs
2020-06-14T21:32:45.208696-05:00 linux-y7h7 kernel:  1091.910288] PM: noirq suspend of devices complete after 597.911 msecs
2020-06-14T21:32:45.208696-05:00 linux-y7h7 kernel:  1091.910522] ACPI: Preparing to enter system sleep state S3
2020-06-14T21:32:45.208697-05:00 linux-y7h7 kernel:  1091.911412] ACPI : EC: event blocked
2020-06-14T21:32:45.208698-05:00 linux-y7h7 kernel:  1091.911412] ACPI : EC: EC stopped
2020-06-14T21:32:45.208699-05:00 linux-y7h7 kernel:  1091.911413] PM: Saving platform NVS memory
2020-06-14T21:32:45.208699-05:00 linux-y7h7 kernel:  1091.911417] Disabling non-boot CPUs ...
2020-06-14T21:32:45.208714-05:00 linux-y7h7 kernel:  1091.911703] Broke affinity for irq 450
2020-06-14T21:32:45.208715-05:00 linux-y7h7 kernel:  1091.912711] smpboot: CPU 1 is now offline
2020-06-14T21:32:45.208716-05:00 linux-y7h7 kernel:  1091.913288] Broke affinity for irq 438
2020-06-14T21:32:45.208716-05:00 linux-y7h7 kernel:  1091.913294] Broke affinity for irq 448
2020-06-14T21:32:45.208717-05:00 linux-y7h7 kernel:  1091.913297] Broke affinity for irq 449
2020-06-14T21:32:45.208717-05:00 linux-y7h7 kernel:  1091.913299] Broke affinity for irq 450
2020-06-14T21:32:45.208718-05:00 linux-y7h7 kernel:  1091.913301] Broke affinity for irq 451
2020-06-14T21:32:45.208718-05:00 linux-y7h7 kernel:  1091.914539] smpboot: CPU 2 is now offline
2020-06-14T21:32:45.208719-05:00 linux-y7h7 kernel:  1091.914895] Broke affinity for irq 16
2020-06-14T21:32:45.208719-05:00 linux-y7h7 kernel:  1091.914901] Broke affinity for irq 124
2020-06-14T21:32:45.208720-05:00 linux-y7h7 kernel:  1091.914922] Broke affinity for irq 438
2020-06-14T21:32:45.208720-05:00 linux-y7h7 kernel:  1091.914926] Broke affinity for irq 441
2020-06-14T21:32:45.208721-05:00 linux-y7h7 kernel:  1091.914928] Broke affinity for irq 448
2020-06-14T21:32:45.208721-05:00 linux-y7h7 kernel:  1091.914930] Broke affinity for irq 449
2020-06-14T21:32:45.208722-05:00 linux-y7h7 kernel:  1091.914932] Broke affinity for irq 450
2020-06-14T21:32:45.208722-05:00 linux-y7h7 kernel:  1091.914934] Broke affinity for irq 451
2020-06-14T21:32:45.208723-05:00 linux-y7h7 kernel:  1091.914935] Broke affinity for irq 452
2020-06-14T21:32:45.208723-05:00 linux-y7h7 kernel:  1091.915938] smpboot: CPU 3 is now offline
2020-06-14T21:32:45.208724-05:00 linux-y7h7 kernel:  1091.918902] ACPI: Low-level resume complete
2020-06-14T21:32:45.208724-05:00 linux-y7h7 kernel:  1091.918987] ACPI : EC: EC started
2020-06-14T21:32:45.208725-05:00 linux-y7h7 kernel:  1091.918987] PM: Restoring platform NVS memory
2020-06-14T21:32:45.208725-05:00 linux-y7h7 kernel:  1091.921372] Enabling non-boot CPUs ...
2020-06-14T21:32:45.208726-05:00 linux-y7h7 kernel:  1091.921426] x86: Booting SMP configuration:
2020-06-14T21:32:45.208726-05:00 linux-y7h7 kernel:  1091.921427] smpboot: Booting Node 0 Processor 1 APIC 0x2
2020-06-14T21:32:45.208727-05:00 linux-y7h7 kernel:  1091.921809] unchecked MSR access error: RDMSR from 0x123 at rIP: 0xffffffff8106a736 (native
_read_msr+0x6/0x30)
2020-06-14T21:32:45.208727-05:00 linux-y7h7 kernel:  1091.921810] Call Trace:
2020-06-14T21:32:45.208728-05:00 linux-y7h7 kernel:  1091.921815]  update_srbds_msr+0x34/0x70
2020-06-14T21:32:45.208728-05:00 linux-y7h7 kernel:  1091.921817]  smp_store_cpu_info+0x45/0x50
2020-06-14T21:32:45.208729-05:00 linux-y7h7 kernel:  1091.921819]  start_secondary+0xaa/0x200
2020-06-14T21:32:45.208729-05:00 linux-y7h7 kernel:  1091.921820]  secondary_startup_64+0xa5/0xb0
2020-06-14T21:32:45.208730-05:00 linux-y7h7 kernel:  1091.921824] unchecked MSR access error: WRMSR to 0x123 (tried to write 0x0000000000000000) at rIP: 0xffffffff8106a864 (native_write_msr+0x4/0x20)
2020-06-14T21:32:45.208730-05:00 linux-y7h7 kernel:  1091.921824] Call Trace:
2020-06-14T21:32:45.208731-05:00 linux-y7h7 kernel:  1091.921826]  update_srbds_msr+0x5d/0x70
2020-06-14T21:32:45.208732-05:00 linux-y7h7 kernel:  1091.921827]  smp_store_cpu_info+0x45/0x50
2020-06-14T21:32:45.208732-05:00 linux-y7h7 kernel:  1091.921828]  start_secondary+0xaa/0x200
2020-06-14T21:32:45.208733-05:00 linux-y7h7 kernel:  1091.921829]  secondary_startup_64+0xa5/0xb0
2020-06-14T21:32:45.208733-05:00 linux-y7h7 kernel:  1091.921834] microcode: sig=0x806ea, pf=0x40, revision=0xca
2020-06-14T21:32:45.208733-05:00 linux-y7h7 kernel:  1091.923413] microcode: updated to revision 0xd6, date = 2020-04-27
2020-06-14T21:32:45.208734-05:00 linux-y7h7 kernel:  1091.923538]  cache: parent cpu1 should not be sleeping
2020-06-14T21:32:45.208734-05:00 linux-y7h7 kernel:  1091.923827] CPU1 is up
2020-06-14T21:32:45.208735-05:00 linux-y7h7 kernel:  1091.923868] smpboot: Booting Node 0 Processor 2 APIC 0x1
2020-06-14T21:32:45.208735-05:00 linux-y7h7 kernel:  1091.924294] microcode: sig=0x806ea, pf=0x40, revision=0xd6
2020-06-14T21:32:45.208736-05:00 linux-y7h7 kernel:  1091.924436]  cache: parent cpu2 should not be sleeping
2020-06-14T21:32:45.208736-05:00 linux-y7h7 kernel:  1091.924874] CPU2 is up
2020-06-14T21:32:45.208737-05:00 linux-y7h7 kernel:  1091.924916] smpboot: Booting Node 0 Processor 3 APIC 0x3
2020-06-14T21:32:45.208738-05:00 linux-y7h7 kernel:  1091.925435]  cache: parent cpu3 should not be sleeping
2020-06-14T21:32:45.208738-05:00 linux-y7h7 kernel:  1091.925707] CPU3 is up
2020-06-14T21:32:45.208738-05:00 linux-y7h7 kernel:  1091.929271] ACPI: Waking up from system sleep state S3
2020-06-14T21:32:45.208739-05:00 linux-y7h7 kernel:  1092.625246] PM: noirq resume of devices complete after 687.441 msecs
2020-06-14T21:32:45.208740-05:00 linux-y7h7 kernel:  1093.089766] PM: early resume of devices complete after 463.315 msecs
2020-06-14T21:32:45.208740-05:00 linux-y7h7 kernel:  1093.184839] ACPI : EC: event unblocked
2020-06-14T21:32:45.208741-05:00 linux-y7h7 kernel:  1094.021970] sd 2:0:0:0: [sda] Starting disk
2020-06-14T21:32:45.208741-05:00 linux-y7h7 kernel:  1094.243944] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
2020-06-14T21:32:45.208742-05:00 linux-y7h7 kernel:  1094.275041] ata3.00: configured for UDMA/100
2020-06-14T21:32:45.208742-05:00 linux-y7h7 kernel:  1094.714118] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
2020-06-14T21:32:45.208743-05:00 linux-y7h7 kernel:  1094.754847] PM: resume of devices complete after 1665.098 msecs
2020-06-14T21:32:45.208743-05:00 linux-y7h7 kernel:  1094.755153] acpi LNXPOWER:04: Turning OFF
2020-06-14T21:32:45.208744-05:00 linux-y7h7 kernel:  1094.755190] PM: Finishing wakeup.
2020-06-14T21:32:45.208744-05:00 linux-y7h7 kernel:  1094.755191] OOM killer enabled.
2020-06-14T21:32:45.215264-05:00 linux-y7h7 systemd-sleep[31426]: System resumed.
2020-06-14T21:32:45.217334-05:00 linux-y7h7 kernel:  1094.755191] Restarting tasks ... done.
2020-06-14T21:32:45.217347-05:00 linux-y7h7 kernel:  1094.760954] Possible incorrect RTC due to pm_trace, please use 'ntpdate' or 'rdate' to reset it.
2020-06-14T21:32:45.217348-05:00 linux-y7h7 kernel:  1094.762201] video LNXVIDEO:00: Restoring backlight state
2020-06-14T21:32:45.227599-05:00 linux-y7h7 systemd-sleep[31426]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
2020-06-14T21:32:45.248309-05:00 linux-y7h7 systemd[1]: Started Suspend.
2020-06-14T21:32:45.248496-05:00 linux-y7h7 systemd[1]: sleep.target: Unit not needed anymore. Stopping.
2020-06-14T21:32:45.249921-05:00 linux-y7h7 systemd[1]: Stopped target Sleep.
2020-06-14T21:32:45.250081-05:00 linux-y7h7 systemd[1]: suspend.target: Bound to unit systemd-suspend.service, but unit isn't active.
2020-06-14T21:32:45.250241-05:00 linux-y7h7 systemd[1]: Dependency failed for Suspend.
2020-06-14T21:32:45.250503-05:00 linux-y7h7 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
2020-06-14T21:32:45.251525-05:00 linux-y7h7 systemd-logind[950]: Operation 'sleep' finished.
2020-06-14T21:32:45.288258-05:00 linux-y7h7 /usr/lib/gdm/gdm-wayland-session[3379]: Window manager warning: Failed to set power save mode for output DP-1: Permiso denegado
...

At first I thought the line ***Window manager warning: Failed to set power save mode for output DP-1: Permiso denegado ***(Permission denied) was a hint, later realized it showed up in both situations. I updated the BIOS to the latest available, then modified settings in the BIOS menu thinking the thunderbolt / eDP connector was the problem (I completely disabled it and then reverted the changes because that didn’t work).

  1. I tried to suspend directly from tty with root permissions (root user) to see if the GNOME session, Wayland or anything else was to blame.
systemctl suspend

After pressing the power button to resume I got a frozen video signal of the tty containing the last commands sent, same behavior as before.

File /sys/power/state:freeze mem disk

File /sys/power/mem_sleep:s2idle [deep]

The swap partition:NAME TYPE SIZE USED PRIO
/dev/sda7 partition 4G 0B -1

Just to make it clear, the only settings I have messed with are from network and VNC.
I already examined this other thread with no luck at all, but looks like it is related:
https://forums.opensuse.org/showthread.php/538833-Crashes-on-Suspend

Any help is appreciated.

Welcome to openSUSE Forums. Just to concentrate my attention on the thread you linked to…I noticed that the OP in that thread mentioned…

Yesterday, I ran another distribution upgrade to 5.4.13, which included a long list of kernel hardware packages. After the upgrade, I used modprobe to re-enable all of the modules I removed earlier and the issue is now totally resolved!

It might be worth trying the current stable kernel perhaps. To do that…

sudo zypper ar -f https://download.opensuse.org/repositories/Kernel:/stable/standard Kernel:stable
sudo zypper in --from Kernel:stable kernel-default

then reboot when done. You can always boot to an older kernel if there are issues with the new kernel.

See if that changes the suspend behaviour.

I installed the latest current stable kernel available (5.7.2-3.ga96d63c-defaul) as you recommended. Seemed to solve the issue but I’m still doubtful because it would disappear for a couple of hours and then all of a sudden the computer was unable to resume. Will keep testing tomorrow to be sure.

Thank you for the answer, deano_ferrari, it really helped me out. I wasn’t sure where to start from.

All good. Monitor it and report back with any issues encountered or if resolved.

Ooops, I took almost a year to answer.

Feedback: Problem solved, definitely.