Hi, something weird has happened since tumbleweed upgrade from 20220214-0 or 20220215-0. Currently I’m on 20220217-0 using xfce.
Before when I resume from suspend I’d get the xfce login screen and things are ok.
Now when I resume from suspend there’s no login screen and I get shown my desktop immediately. There’s no respond to mouse clicks or the keyboard. I can Ctrl+Alt+F2 but no login appears. Back to Ctrl+Alt+F7 and the screen is basically dead. I have to poweroff by holding down the power button and reboot.
This is the journalctl output for the suspend -
Feb 20 16:37:28 asus-roc.lan ModemManager[1038]: <info> [sleep-monitor] system is about to suspend
Feb 20 16:37:28 asus-roc.lan systemd[1]: Reached target Sleep.
Feb 20 16:37:28 asus-roc.lan systemd[1]: Starting System Suspend...
Feb 20 16:37:28 asus-roc.lan systemd-sleep[12702]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
Feb 20 16:37:28 asus-roc.lan systemd-sleep[12700]: Entering sleep state 'suspend'...
Feb 20 16:37:28 asus-roc.lan kernel: PM: suspend entry (deep)
Feb 20 16:37:28 asus-roc.lan kernel: Filesystems sync: 0.033 seconds
And this is for the resume from suspend, lot’s of what I think are Nvidia issues? Not sure -
Feb 20 18:33:01 asus-roc.lan kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 20 18:33:01 asus-roc.lan kernel: OOM killer disabled.
Feb 20 18:33:01 asus-roc.lan kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 20 18:33:01 asus-roc.lan kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 20 18:33:01 asus-roc.lan kernel: e1000e: EEE TX LPI TIMER: 00000011
Feb 20 18:33:01 asus-roc.lan kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
Feb 20 18:33:01 asus-roc.lan kernel: sd 2:0:0:0: [sda] Stopping disk
Feb 20 18:33:01 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Feb 20 18:33:01 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Stopping disk
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: interrupt blocked
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: PM: Preparing to enter system sleep state S3
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: event blocked
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: EC stopped
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: PM: Saving platform NVS memory
Feb 20 18:33:01 asus-roc.lan kernel: Disabling non-boot CPUs ...
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 1 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 2 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 3 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 4 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 5 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 6 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 7 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 8 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 9 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 10 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: CPU 11 is now offline
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: PM: Low-level resume complete
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: EC started
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: PM: Restoring platform NVS memory
Feb 20 18:33:01 asus-roc.lan kernel: Enabling non-boot CPUs ...
Feb 20 18:33:01 asus-roc.lan kernel: x86: Booting SMP configuration:
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 20 18:33:01 asus-roc.lan kernel: CPU1 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Feb 20 18:33:01 asus-roc.lan kernel: CPU2 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Feb 20 18:33:01 asus-roc.lan kernel: CPU3 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Feb 20 18:33:01 asus-roc.lan kernel: CPU4 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Feb 20 18:33:01 asus-roc.lan kernel: CPU5 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Feb 20 18:33:01 asus-roc.lan kernel: CPU6 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Feb 20 18:33:01 asus-roc.lan kernel: CPU7 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Feb 20 18:33:01 asus-roc.lan kernel: CPU8 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Feb 20 18:33:01 asus-roc.lan kernel: CPU9 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Feb 20 18:33:01 asus-roc.lan kernel: CPU10 is up
Feb 20 18:33:01 asus-roc.lan kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Feb 20 18:33:01 asus-roc.lan kernel: CPU11 is up
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: PM: Waking up from system sleep state S3
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: interrupt unblocked
Feb 20 18:33:01 asus-roc.lan kernel: ACPI: EC: event unblocked
Feb 20 18:33:01 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Starting disk
Feb 20 18:33:01 asus-roc.lan kernel: sd 2:0:0:0: [sda] Starting disk
Feb 20 18:33:01 asus-roc.lan kernel: usb usb3: root hub lost power or was reset
Feb 20 18:33:01 asus-roc.lan kernel: usb usb4: root hub lost power or was reset
Feb 20 18:33:01 asus-roc.lan kernel: ata6: SATA link down (SStatus 4 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata2: SATA link down (SStatus 4 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata5: SATA link down (SStatus 4 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata3.00: configured for UDMA/133
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata4.00: configured for UDMA/133
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 20 18:33:01 asus-roc.lan kernel: ata1.00: configured for UDMA/33
Feb 20 18:33:01 asus-roc.lan kernel: OOM killer enabled.
Feb 20 18:33:01 asus-roc.lan kernel: Restarting tasks ... done.
Feb 20 18:33:01 asus-roc.lan kernel: PM: suspend exit
Feb 20 18:33:01 asus-roc.lan kernel: "filter_IN_public_REJECT: "IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:2efd:a1ff:fe5c:521c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=188 TC=0 HOPLIMIT=255 FLOWLBL=313296 PROTO=UDP SPT=5353 DPT=5353 LEN=148
Feb 20 18:33:01 asus-roc.lan systemd-networkd[1200]: eth0: Lost carrier
Feb 20 18:33:01 asus-roc.lan dbus-daemon[911]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.6' (uid=483 pid=1200 comm="/usr/lib/systemd/systemd-networkd ")
Feb 20 18:33:01 asus-roc.lan systemd-networkd[1200]: eth0: DHCP lease lost
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Withdrawing address record for 10.1.1.20 on eth0.
Feb 20 18:33:01 asus-roc.lan systemd-resolved[1205]: Clock change detected. Flushing caches.
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.1.1.20.
Feb 20 18:33:01 asus-roc.lan systemd-sleep[12700]: System returned from sleep state.
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 20 18:33:01 asus-roc.lan systemd-networkd[1200]: eth0: DHCPv6 lease lost
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Withdrawing address record for fd6c:1c5d:8413:0:2efd:a1ff:fe5c:521c on eth0.
Feb 20 18:33:01 asus-roc.lan systemd[1]: Started Timeline of Snapper Snapshots.
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Leaving mDNS multicast group on interface eth0.IPv6 with address fd6c:1c5d:8413:0:2efd:a1ff:fe5c:521c.
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::2efd:a1ff:fe5c:521c.
Feb 20 18:33:01 asus-roc.lan avahi-daemon[4300]: Registering new address record for fe80::2efd:a1ff:fe5c:521c on eth0.*.
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 ignored inotify event for `/etc/resolv.conf` (file exists)
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 ignored inotify event for `/etc/resolv.conf` (file exists)
Feb 20 18:33:01 asus-roc.lan systemd-sleep[12776]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
Feb 20 18:33:01 asus-roc.lan systemd[1]: Starting Hostname Service...
Feb 20 18:33:01 asus-roc.lan systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 20 18:33:01 asus-roc.lan systemd[1]: Finished System Suspend.
Feb 20 18:33:01 asus-roc.lan systemd[1]: Stopped target Sleep.
Feb 20 18:33:01 asus-roc.lan systemd[1]: Reached target Suspend.
Feb 20 18:33:01 asus-roc.lan systemd[1]: Stopped target Suspend.
Feb 20 18:33:01 asus-roc.lan systemd-logind[1009]: Operation 'sleep' finished.
Feb 20 18:33:01 asus-roc.lan systemd-networkd[1200]: lo: Reset carrier
Feb 20 18:33:01 asus-roc.lan ModemManager[1038]: <info> [sleep-monitor] system is resuming
Feb 20 18:33:01 asus-roc.lan dbus-daemon[911]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.222' (uid=0 pid=12784 comm="/usr/lib/snapper/systemd-helper --timeline ")
Feb 20 18:33:01 asus-roc.lan systemd[1]: Starting DBus interface for snapper...
Feb 20 18:33:01 asus-roc.lan dbus-daemon[911]: [system] Successfully activated service 'org.opensuse.Snapper'
Feb 20 18:33:01 asus-roc.lan systemd[1]: Started DBus interface for snapper.
Feb 20 18:33:01 asus-roc.lan systemd[1]: snapper-timeline.service: Deactivated successfully.
Feb 20 18:33:01 asus-roc.lan dbus-daemon[911]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 20 18:33:01 asus-roc.lan systemd[1]: Started Hostname Service.
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 monitoring file `/etc/nsswitch.conf` (6)
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 monitoring directory `/etc` (2)
Feb 20 18:33:01 asus-roc.lan systemd-hostnamed[12786]: Hostname set to <asus-roc.lan> (static)
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 monitoring file `/etc/resolv.conf` (7)
Feb 20 18:33:01 asus-roc.lan nscd[933]: 933 monitoring directory `/etc` (2)
Feb 20 18:33:01 asus-roc.lan kernel: "filter_IN_public_REJECT: "IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:2efd:a1ff:fe5c:521c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=90 TC=0 HOPLIMIT=255 FLOWLBL=313296 PROTO=UDP SPT=5353 DPT=5353 LEN=50
Feb 20 18:33:01 asus-roc.lan rtkit-daemon[4698]: Supervising 2 threads of 2 processes of 1 users.
Feb 20 18:33:01 asus-roc.lan rtkit-daemon[4698]: Supervising 2 threads of 2 processes of 1 users.
Feb 20 18:33:01 asus-roc.lan rtkit-daemon[4698]: Supervising 2 threads of 2 processes of 1 users.
Feb 20 18:33:01 asus-roc.lan rtkit-daemon[4698]: Supervising 2 threads of 2 processes of 1 users.
Feb 20 18:33:01 asus-roc.lan rtkit-daemon[4698]: Supervising 2 threads of 2 processes of 1 users.
Feb 20 18:33:01 asus-roc.lan kernel: "filter_IN_public_REJECT: "IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:2efd:a1ff:fe5c:521c DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=200 TC=0 HOPLIMIT=255 FLOWLBL=313296 PROTO=UDP SPT=5353 DPT=5353 LEN=160
Feb 20 18:33:02 asus-roc.lan kernel: NVRM: GPU at PCI:0000:01:00: GPU-e3d09615-3527-dee2-b8cb-a8198857ba08
Feb 20 18:33:02 asus-roc.lan kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=4875, Ch 00000010, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST faulted @ 0x1_02890000. Fault is of type FAULT_PDE ACCESS_TYPE_READ
.
.
.
.
Feb 20 18:33:16 asus-roc.lan kernel: "filter_IN_public_REJECT: "IN=eth0 OUT= MAC= SRC=10.1.1.20 DST=224.0.0.251 LEN=70 TOS=0x00 PREC=0x00 TTL=255 ID=54742 DF PROTO=UDP SPT=5353 DPT=5353 LEN=50
Feb 20 18:33:21 asus-roc.lan rtkit-daemon[4698]: Supervising 1 threads of 1 processes of 1 users.
Feb 20 18:33:21 asus-roc.lan rtkit-daemon[4698]: Supervising 1 threads of 1 processes of 1 users.
Feb 20 18:33:21 asus-roc.lan rtkit-daemon[4698]: Supervising 1 threads of 1 processes of 1 users.
Feb 20 18:33:21 asus-roc.lan rtkit-daemon[4698]: Supervising 1 threads of 1 processes of 1 users.
Feb 20 18:33:21 asus-roc.lan rtkit-daemon[4698]: Supervising 1 threads of 1 processes of 1 users.
I think 20220214-0 had an Nvidia driver update. Is there something I can test or do I just have to wait for another Nvidia driver update? I’m cautious at the moment at blindly doing a snapshot restore.
Thanks.