Unable to suspend my machine after switching to KDE Plasma

rakeshdas · 2018-07-19 00:35:15

I have recently switched from using Cinnamon as my DE to KDE and I am having some issues with suspending my system. I have set KDE to automatically lock and suspend my system after 5 mins of inactivity and I have noticed that after I get back to my desk, the system is just locked, not suspended. So, I started debugging by manually running `systemctl suspend` on the command line and I have noticed that my PC will start suspending, monitors turn off, the backlight on my keyboard turns off too, but a couple seconds later, my monitors come back on, greeting me with the KDE lock screen. During this time, none of the lights on my motherboard nor my the fans inside my case turn off, so I'm not even sure if my PC does suspend properly.

After, I looked through journalctl and saw this:

    Jul 16 23:04:32 rakesh-arch kernel: PM: suspend entry (deep)
    Jul 16 23:04:32 rakesh-arch plasmashell[794]: QXcbClipboard: SelectionRequest too old
    Jul 16 23:04:32 rakesh-arch ksmserver[752]: CreateNotify: 33554483
    Jul 16 23:04:34 rakesh-arch kernel: PM: Syncing filesystems ... done.
    Jul 16 23:04:34 rakesh-arch kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
    Jul 16 23:04:34 rakesh-arch kernel: OOM killer disabled.
    Jul 16 23:04:34 rakesh-arch kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    Jul 16 23:04:34 rakesh-arch kernel: Suspending console(s) (use no_console_suspend to debug)
    Jul 16 23:04:34 rakesh-arch kernel: e1000e: EEE TX LPI TIMER: 00000011
    Jul 16 23:04:34 rakesh-arch kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
    Jul 16 23:04:34 rakesh-arch kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
    Jul 16 23:04:34 rakesh-arch kernel: sd 3:0:0:0: [sdb] Stopping disk
    Jul 16 23:04:34 rakesh-arch kernel: sd 1:0:0:0: [sda] Stopping disk
    Jul 16 23:04:34 rakesh-arch kernel: DMAR: DRHD: handling fault status reg 2
    Jul 16 23:04:34 rakesh-arch kernel: DMAR: [DMA Read] Request device [04:00.0] fault addr 0 [fault reason 06] PTE Read access is not set
    Jul 16 23:04:34 rakesh-arch kernel: xhci_hcd 0000:04:00.0: WARN: xHC save state timeout
    Jul 16 23:04:34 rakesh-arch kernel: suspend_common(): xhci_pci_suspend+0x0/0xc0 [xhci_pci] returns -110
    Jul 16 23:04:34 rakesh-arch kernel: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -110
    Jul 16 23:04:34 rakesh-arch kernel: dpm_run_callback(): pci_pm_suspend+0x0/0x120 returns -110
    Jul 16 23:04:34 rakesh-arch kernel: PM: Device 0000:04:00.0 failed to suspend async: error -110
    Jul 16 23:04:34 rakesh-arch kernel: PM: Some devices failed to suspend, or early wake event detected

After reading this, I figured that the USB device with the ID 04:00.0 was the culprit, so I ran lspci to identify it and found out that it was USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller. So I guess it's the USB C port on the back of my MSI Z170A? Next, I attempted to toggle the device on and off during suspend using the advice described in this thread but, no dice. Alternatively, I went into my BIOS and disabled any option resembling "USB wakeup" or "USB power during poweroff" and that didn't fix it either. Something that I found a bit odd was if I attempted to suspend my system via sudo pm-suspend, it does the exact same thing, but it does not bring me back to the KDE lock screen, instead it brings me back to the regular, unlocked session. I guess KDE suspends using systemctl suspend rather than pm-suspend. Additionally, I tried the advice given in this thread and changed the file /sys/bus/pci/devices/0000:04:00.0/power/wakeup to say disabled instead of enabled, but that did not change anything either. Finally, I found this package in the AUR that claims to suspend kernel modules placed in the file /etc/suspend-modules.conf, so I placed xhci_hcd into that file since that kernel module seems to handle that USB controller, but that did not help anything either.

So does anyone have any other idea of how to solve this issue? Let me know if you need more logs!

seth · 2018-07-19 06:11:48

Jul 16 23:04:34 rakesh-arch kernel: DMAR: DRHD: handling fault status reg 2

Is this still the Antergos system you try to use w/ IOMMU?

rakeshdas · 2018-07-21 23:41:59

seth wrote:

Jul 16 23:04:34 rakesh-arch kernel: DMAR: DRHD: handling fault status reg 2
Is this still the Antergos system you try to use w/ IOMMU?

Nope - it's a different machine with a similar hostname

seth · 2018-07-22 05:07:19

The point is that this sounds very iommu related…

rakeshdas · 2018-07-22 15:13:42

I have IOMMU enabled on this machine as well, what leads you to believe that this is IOMMU related?

seth · 2018-07-22 16:24:33

The line I quoted?

Arch Linux

#1 2018-07-19 00:35:15

Unable to suspend my machine after switching to KDE Plasma

#2 2018-07-19 06:11:48

Re: Unable to suspend my machine after switching to KDE Plasma

#3 2018-07-21 23:41:59

Re: Unable to suspend my machine after switching to KDE Plasma

#4 2018-07-22 05:07:19

Re: Unable to suspend my machine after switching to KDE Plasma

#5 2018-07-22 15:13:42

Re: Unable to suspend my machine after switching to KDE Plasma

#6 2018-07-22 16:24:33

Re: Unable to suspend my machine after switching to KDE Plasma

Board footer