Issues with suspending (New issue)

ArchFen1x · 2018-08-19 21:50:13

When I suspend my system from the logout manager in XFCE, the screens will not turn back on when I turn my system back on. I originally thought this was a kernel or mesa issue, so I rolled both of those back to the backup folder I had from two weeks ago where I knew it was working fine and nothing changed. It turns out that if I type in "systemctl suspend" into the terminal, suspend acts how it is supposed to but it doesn't work correctly from the logout manager as described above. What could be the cause of this? Obviously the systemctl suspend command is a workaround, but I would still like to do it from the login manager and want to figure out why this issue occurs. Thanks.

Last edited by ArchFen1x (2018-08-19 21:50:35)

jasonwryan · 2018-08-19 21:54:20

Look in your journal for differences between the two approaches.

ArchFen1x · 2018-08-19 22:17:17

jasonwryan wrote:

Look in your journal for differences between the two approaches.

With logout manager:

Aug 19 18:05:08 ArchFen1x systemd[1]: Reached target Sleep.
Aug 19 18:05:08 ArchFen1x systemd[1]: Starting Suspend...
Aug 19 18:05:08 ArchFen1x systemd-sleep[1019]: Suspending system...
Aug 19 18:05:08 ArchFen1x kernel: PM: suspend entry (deep)
-- Reboot -- //This is where I have no choice but to reset.

with "systemctl suspend"

Aug 19 18:08:15 ArchFen1x systemd[1]: Reached target Sleep.
Aug 19 18:08:15 ArchFen1x systemd[1]: Starting Suspend...
Aug 19 18:08:15 ArchFen1x systemd-sleep[1019]: Suspending system...
Aug 19 18:08:15 ArchFen1x kernel: PM: suspend entry (deep)
Aug 19 18:08:25 ArchFen1x kernel: PM: Syncing filesystems ... done.
Aug 19 18:08:25 ArchFen1x kernel: Freezing user space processes ... (elapsed 0.>
Aug 19 18:08:25 ArchFen1x kernel: OOM killer disabled.
Aug 19 18:08:25 ArchFen1x kernel: Freezing remaining freezable tasks ... (elaps>
Aug 19 18:08:25 ArchFen1x kernel: Suspending console(s) (use no_console_suspend>
Aug 19 18:08:25 ArchFen1x kernel: serial 00:05: disabled
Aug 19 18:08:25 ArchFen1x kernel: e1000e: EEE TX LPI TIMER: 00000011
Aug 19 18:08:25 ArchFen1x kernel: sd 7:0:0:0: [sdb] Synchronizing SCSI cache
Aug 19 18:08:25 ArchFen1x kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Aug 19 18:08:25 ArchFen1x kernel: sd 7:0:0:0: [sdb] Stopping disk
Aug 19 18:08:25 ArchFen1x kernel: sd 1:0:0:0: [sda] Stopping disk
Aug 19 18:08:25 ArchFen1x kernel: amdgpu 0000:01:00.0: 00000000418bddf4 unpin n>
Aug 19 18:08:25 ArchFen1x kernel: amdgpu 0000:01:00.0: 00000000418bddf4 unpin n>
Aug 19 18:08:25 ArchFen1x kernel: ACPI: Preparing to enter system sleep state S3
Aug 19 18:08:25 ArchFen1x kernel: PM: Saving platform NVS memory
Aug 19 18:08:25 ArchFen1x kernel: Disabling non-boot CPUs ...
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 1 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 2 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 3 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 4 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 5 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 6 is now offline
Aug 19 18:08:25 ArchFen1x kernel: smpboot: CPU 7 is now offline
Aug 19 18:08:25 ArchFen1x kernel: ACPI: Low-level resume complete
Aug 19 18:08:25 ArchFen1x kernel: PM: Restoring platform NVS memory
Aug 19 18:08:25 ArchFen1x kernel: Enabling non-boot CPUs ...
Aug 19 18:08:25 ArchFen1x kernel: x86: Booting SMP configuration:
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu1 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU1 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu2 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU2 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu3 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU3 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu4 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU4 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu5 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU5 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu6 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU6 is up
Aug 19 18:08:25 ArchFen1x kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Aug 19 18:08:25 ArchFen1x kernel:  cache: parent cpu7 should not be sleeping
Aug 19 18:08:25 ArchFen1x kernel: CPU7 is up
Aug 19 18:08:25 ArchFen1x kernel: ACPI: Waking up from system sleep state S3
Aug 19 18:08:25 ArchFen1x kernel: usb usb2: root hub lost power or was reset
Aug 19 18:08:25 ArchFen1x kernel: usb usb4: root hub lost power or was reset
Aug 19 18:08:25 ArchFen1x kernel: usb usb5: root hub lost power or was reset
Aug 19 18:08:25 ArchFen1x kernel: usb usb6: root hub lost power or was reset
Aug 19 18:08:25 ArchFen1x kernel: serial 00:05: activated
Aug 19 18:08:25 ArchFen1x kernel: sd 1:0:0:0: [sda] Starting disk
Aug 19 18:08:25 ArchFen1x kernel: sd 7:0:0:0: [sdb] Starting disk
Aug 19 18:08:25 ArchFen1x kernel: [drm] PCIE GART of 256M enabled (table at 0x0>
Aug 19 18:08:25 ArchFen1x kernel: [drm] SADs count is: -2, don't need to read it
Aug 19 18:08:25 ArchFen1x kernel: [drm] SADs count is: -2, don't need to read it
Aug 19 18:08:25 ArchFen1x kernel: usb 1-1: reset high-speed USB device number 2>
Aug 19 18:08:25 ArchFen1x kernel: usb 3-1: reset high-speed USB device number 2>
Aug 19 18:08:25 ArchFen1x kernel: ata7: SATA link down (SStatus 0 SControl 300)
Aug 19 18:08:25 ArchFen1x kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SCon>
Aug 19 18:08:25 ArchFen1x kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SCon>
Aug 19 18:08:25 ArchFen1x kernel: ata2.00: configured for UDMA/133
Aug 19 18:08:25 ArchFen1x kernel: ata4.00: configured for UDMA/100
Aug 19 18:08:25 ArchFen1x kernel: [drm] UVD and UVD ENC initialized successfull>
Aug 19 18:08:25 ArchFen1x kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SCon>
Aug 19 18:08:25 ArchFen1x kernel: ata8.00: configured for UDMA/133
Aug 19 18:08:25 ArchFen1x kernel: usb 5-2: reset high-speed USB device number 2>
Aug 19 18:08:25 ArchFen1x kernel: usb 2-3: reset low-speed USB device number 2 >
Aug 19 18:08:25 ArchFen1x kernel: [drm] VCE initialized successfully.
Aug 19 18:08:25 ArchFen1x kernel: usb 2-4: reset full-speed USB device number 3>
Aug 19 18:08:25 ArchFen1x kernel: usb 5-2.7: reset high-speed USB device number>
Aug 19 18:08:25 ArchFen1x kernel: usb 5-2.4: reset high-speed USB device number>
Aug 19 18:08:25 ArchFen1x kernel: OOM killer enabled.
Aug 19 18:08:25 ArchFen1x kernel: Restarting tasks ... 
Aug 19 18:08:25 ArchFen1x kernel: pci_bus 0000:04: Allocating resources
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: bridge window [io  0x1000-0>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: bridge window [mem 0x001000>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: bridge window [mem 0x001000>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: BAR 14: assigned [mem 0xf06>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: BAR 15: assigned [mem 0xf08>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: BAR 13: assigned [io  0x300>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0: PCI bridge to [bus 04]
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0:   bridge window [io  0x3000>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0:   bridge window [mem 0xf060>
Aug 19 18:08:25 ArchFen1x kernel: pci 0000:03:00.0:   bridge window [mem 0xf080>
Aug 19 18:08:25 ArchFen1x kernel: done.
Aug 19 18:08:25 ArchFen1x kernel: PM: suspend exit
Aug 19 18:08:25 ArchFen1x dhcpcd[535]: eno1: carrier lost
Aug 19 18:08:25 ArchFen1x systemd-sleep[1019]: System resumed.
Aug 19 18:08:25 ArchFen1x dhcpcd[535]: eno1: deleting address fe80::fe70:5389:a>
Aug 19 18:08:25 ArchFen1x systemd[1]: Started Suspend.
Aug 19 18:08:25 ArchFen1x dhcpcd[535]: eno1: deleting route to 192.168.86.0/24
Aug 19 18:08:25 ArchFen1x systemd[1]: sleep.target: Unit not needed anymore. St>
Aug 19 18:08:25 ArchFen1x dhcpcd[535]: eno1: deleting default route via 192.168>
Aug 19 18:08:25 ArchFen1x systemd[1]: Stopped target Sleep.
Aug 19 18:08:25 ArchFen1x systemd[1]: Reached target Suspend.
Aug 19 18:08:25 ArchFen1x systemd[1]: suspend.target: Unit not needed anymore. >
Aug 19 18:08:25 ArchFen1x systemd[1]: Stopped target Suspend.
Aug 19 18:08:25 ArchFen1x systemd-logind[516]: Operation 'sleep' finished.
Aug 19 18:08:26 ArchFen1x kernel: [drm] SADs count is: -2, don't need to read it
Aug 19 18:08:26 ArchFen1x kernel: [drm] SADs count is: -2, don't need to read it
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: carrier acquired
Aug 19 18:08:27 ArchFen1x kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Du>
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: IAID 5b:9c:9e:24
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: adding address fe80::fe70:5389:a7b>
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: soliciting an IPv6 router
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: rebinding lease of 192.168.86.202
Aug 19 18:08:27 ArchFen1x dhcpcd[535]: eno1: probing address 192.168.86.202/24
Aug 19 18:08:27 ArchFen1x lightdm[1215]: pam_unix(lightdm-greeter:session): ses>
Aug 19 18:08:27 ArchFen1x systemd[1]: Started /run/user/620 mount wrapper.
Aug 19 18:08:27 ArchFen1x systemd[1]: Created slice User Slice of UID 620.
Aug 19 18:08:27 ArchFen1x systemd[1]: Starting User Manager for UID 620...
Aug 19 18:08:27 ArchFen1x systemd-logind[516]: New session c2 of user lightdm.
Aug 19 18:08:27 ArchFen1x systemd[1]: Started Session c2 of user lightdm.
Aug 19 18:08:27 ArchFen1x kernel: audit: type=1006 audit(1534716507.990:27): pi>
Aug 19 18:08:27 ArchFen1x systemd[1219]: pam_unix(systemd-user:session): sessio>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Reached target Paths.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Reached target Timers.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on GnuPG cryptographic agent>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on GnuPG cryptographic agent>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on GnuPG cryptographic agent>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on Sound System.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on GnuPG cryptographic agent>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on p11-kit server.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on GnuPG network certificate>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Starting D-Bus User Message Bus Socket.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Listening on D-Bus User Message Bus So>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Reached target Sockets.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Reached target Basic System.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Reached target Default.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Startup finished in 16ms.
Aug 19 18:08:28 ArchFen1x systemd[1]: Started User Manager for UID 620.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Started D-Bus User Message Bus.
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Activat>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Starting Accessibility services bus...
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Success>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Started Accessibility services bus.
Aug 19 18:08:28 ArchFen1x at-spi-bus-launcher[1235]: dbus-daemon[1240]: Activat>
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Activat>
Aug 19 18:08:28 ArchFen1x at-spi-bus-launcher[1235]: dbus-daemon[1240]: Success>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Starting Virtual filesystem service...
Aug 19 18:08:28 ArchFen1x systemd[1]: Started User Manager for UID 620.
Aug 19 18:08:28 ArchFen1x systemd[1219]: Started D-Bus User Message Bus.
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Activat>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Starting Accessibility services bus...
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Success>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Started Accessibility services bus.
Aug 19 18:08:28 ArchFen1x at-spi-bus-launcher[1235]: dbus-daemon[1240]: Activat>
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Activat>
Aug 19 18:08:28 ArchFen1x at-spi-bus-launcher[1235]: dbus-daemon[1240]: Success>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Starting Virtual filesystem service...
Aug 19 18:08:28 ArchFen1x at-spi-bus-launcher[1235]: SpiRegistry daemon is runn>
Aug 19 18:08:28 ArchFen1x dbus-daemon[1234]: [session uid=620 pid=1234] Success>
Aug 19 18:08:28 ArchFen1x systemd[1219]: Started Virtual filesystem service.
Aug 19 18:08:28 ArchFen1x polkitd[574]: /usr/share/polkit-1/rules.d/lightdm.rul>
Aug 19 18:08:28 ArchFen1x polkitd[574]: /usr/share/polkit-1/rules.d/lightdm.rul>
Aug 19 18:08:32 ArchFen1x lightdm[1263]: pam_unix(lightdm:auth): authentication>
Aug 19 18:08:32 ArchFen1x dhcpcd[535]: eno1: leased 192.168.86.202 for 86400 se>
...

With that info, what do you think the issue might be?

Last edited by ArchFen1x (2018-08-19 22:27:11)

jasonwryan · 2018-08-19 22:19:48

Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

ArchFen1x · 2018-08-19 22:28:29

jasonwryan wrote:

Use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

Edited.

I just disabled lightdm and suspended without a display manager, it behaved as it should. Perhaps the issue is lightdm? It hasn't been updated since March though, so it doesn't make sense that this issue began to happen out of nowhere. It makes me find it hard to believe lightdm is the issue.

EDIT: I rolled back xorg-server and that fixed it. Odd, we'll see if that is fixed in the next update. I'll try to report it.

Last edited by ArchFen1x (2018-08-19 22:56:07)

Arch Linux

#1 2018-08-19 21:50:13

Issues with suspending (New issue)

#2 2018-08-19 21:54:20

Re: Issues with suspending (New issue)

#3 2018-08-19 22:17:17

Re: Issues with suspending (New issue)

#4 2018-08-19 22:19:48

Re: Issues with suspending (New issue)

#5 2018-08-19 22:28:29

Re: Issues with suspending (New issue)

Board footer