You are not logged in.

#1 2018-08-29 06:33:43

psic4t
Member
Registered: 2018-08-22
Posts: 3

No resume from suspend

Hi all,

my PC isn't able to resume from suspend. If I push a key on the USB keyboard the backlight activates but nothing else happens. To be able to boot again, I have to disconnect power.

- suspend and resume works fine with Ubuntu 18.04 on the same machine so it's not likely to be a BIOS issue
- /proc/acpi/wakeup is the same on Arch and on Ubuntu (see below)


Any ideas what I can check?

/proc/acpi/wakeup

Device  S-state   Status   Sysfs node
SBAZ      S4    *disabled  pci:0000:00:14.2
PS2K      S3    *disabled
PS2M      S3    *disabled
P0PC      S4    *disabled  pci:0000:00:14.4
GEC       S4    *disabled
UHC1      S4    *enabled   pci:0000:00:12.0
UHC2      S4    *enabled   pci:0000:00:12.2
USB3      S4    *enabled   pci:0000:00:13.0
UHC4      S4    *enabled   pci:0000:00:13.2
USB5      S4    *enabled   pci:0000:00:16.0
UHC6      S4    *enabled   pci:0000:00:16.2
UHC7      S4    *enabled   pci:0000:00:14.5
PE20      S4    *disabled  pci:0000:00:15.0
GBE       S4    *disabled  pci:0000:05:00.0
PE21      S4    *disabled
PE22      S4    *disabled
PE23      S4    *disabled
PC02      S4    *disabled  pci:0000:00:02.0
PC03      S4    *disabled
PC04      S4    *disabled
PC05      S4    *disabled
PC06      S4    *disabled
PC07      S4    *disabled
PC09      S4    *disabled  pci:0000:00:09.0
PC0A      S4    *disabled  pci:0000:00:0a.0
PC0B      S4    *disabled
PC0C      S4    *disabled
PC0D      S4    *disabled
PWRB      S3    *enabled   platform:PNP0C0C:00

Last journal entries with suspend:

Aug 19 19:29:05 c0re systemd[1]: Reached target Sleep.
Aug 19 19:29:05 c0re systemd[1]: Starting Suspend...
Aug 19 19:29:05 c0re systemd-sleep[22905]: Suspending system...
Aug 19 19:29:05 c0re kernel: PM: suspend entry (deep)

Last edited by psic4t (2018-08-29 06:34:42)

Offline

#2 2018-09-02 15:19:14

philipW
Member
Registered: 2017-03-21
Posts: 120

Re: No resume from suspend

Have you added the "resume" kernel parameter?

Offline

#3 2018-09-02 15:29:12

seth
Member
Registered: 2012-09-03
Posts: 8,665

Re: No resume from suspend

That's for hibernation, S4 - he's got trouble to awake from S3.
@psic4t
* do you have an nvidia GPU?
* does it matter how long the S3 lasts?
* did you try the lts kernel?
* from what environment do you go S3? Does the wakeup work if you S3 from the multi-user.target? (See https://wiki.archlinux.org/index.php/Sy … boot_into)

Offline

#4 2018-09-03 06:10:33

psic4t
Member
Registered: 2018-08-22
Posts: 3

Re: No resume from suspend

@philipW As seth pointed out, I just use suspend, not hibernate - no kernel parameters needed.

@seth

* Yes, I use an Nvidia card with proprietary drivers. But works in Ubuntu with the same drivers.
* No, time doesn't matter. I tried everything from 20 secs to an hour.
* No, didn't try the lts kernel. Will report back on that.
* I use the default graphical target and startx with i3.

With the multi-user.target the system behaves differently: It suspends and resumes immediately after this without any user intervention.

"journalctl -b -u systemd-suspend" shows

Sep 03 06:57:09 c0re systemd[1]: Starting Suspend...
Sep 03 06:57:09 c0re systemd-sleep[1756]: Suspending system...
Sep 03 06:57:17 c0re systemd-sleep[1756]: System resumed.
Sep 03 06:57:17 c0re systemd[1]: Started Suspend.

Can I check what makes it resume?


EDIT: Complete log:

Sep 03 06:57:09 c0re systemd[1]: Reached target Sleep.
Sep 03 06:57:09 c0re systemd[1]: Starting Suspend...
Sep 03 06:57:09 c0re systemd-sleep[1756]: Suspending system...
Sep 03 06:57:09 c0re kernel: PM: suspend entry (deep)
Sep 03 06:57:09 c0re kernel: PM: Syncing filesystems ... done.
Sep 03 06:57:17 c0re kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Sep 03 06:57:17 c0re kernel: OOM killer disabled.
Sep 03 06:57:17 c0re kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep 03 06:57:17 c0re kernel: Suspending console(s) (use no_console_suspend to debug)
Sep 03 06:57:17 c0re kernel: serial 00:03: disabled
Sep 03 06:57:17 c0re kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Sep 03 06:57:17 c0re kernel: sd 4:0:0:0: [sdd] Stopping disk
Sep 03 06:57:17 c0re kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Sep 03 06:57:17 c0re kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
Sep 03 06:57:17 c0re kernel: sd 3:0:0:0: [sdc] Stopping disk
Sep 03 06:57:17 c0re kernel: sd 2:0:0:0: [sdb] Stopping disk
Sep 03 06:57:17 c0re kernel: sd 0:0:1:0: [sda] Synchronizing SCSI cache
Sep 03 06:57:17 c0re kernel: sd 0:0:1:0: [sda] Stopping disk
Sep 03 06:57:17 c0re kernel: ACPI: Preparing to enter system sleep state S3
Sep 03 06:57:17 c0re kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Sep 03 06:57:17 c0re kernel: PM: Saving platform NVS memory
Sep 03 06:57:17 c0re kernel: Disabling non-boot CPUs ...
Sep 03 06:57:17 c0re kernel: smpboot: CPU 1 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 2 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 3 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 4 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 5 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 6 is now offline
Sep 03 06:57:17 c0re kernel: smpboot: CPU 7 is now offline
Sep 03 06:57:17 c0re kernel: ACPI: Low-level resume complete
Sep 03 06:57:17 c0re kernel: PM: Restoring platform NVS memory
Sep 03 06:57:17 c0re kernel: LVT offset 0 assigned for vector 0x400
Sep 03 06:57:17 c0re kernel: microcode: CPU0: new patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: Enabling non-boot CPUs ...
Sep 03 06:57:17 c0re kernel: x86: Booting SMP configuration:
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Sep 03 06:57:17 c0re kernel:  cache: parent cpu1 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU1: patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU1 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Sep 03 06:57:17 c0re kernel:  cache: parent cpu2 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU2: patch_level=0x06000822
Sep 03 06:57:17 c0re kernel: microcode: CPU2: new patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU2 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Sep 03 06:57:17 c0re kernel:  cache: parent cpu3 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU3: patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU3 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 4 APIC 0x14
Sep 03 06:57:17 c0re kernel:  cache: parent cpu4 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU4: patch_level=0x06000822
Sep 03 06:57:17 c0re kernel: microcode: CPU4: new patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU4 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 5 APIC 0x15
Sep 03 06:57:17 c0re kernel:  cache: parent cpu5 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU5: patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU5 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 6 APIC 0x16
Sep 03 06:57:17 c0re kernel:  cache: parent cpu6 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU6: patch_level=0x06000822
Sep 03 06:57:17 c0re kernel: microcode: CPU6: new patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU6 is up
Sep 03 06:57:17 c0re kernel: smpboot: Booting Node 0 Processor 7 APIC 0x17
Sep 03 06:57:17 c0re kernel:  cache: parent cpu7 should not be sleeping
Sep 03 06:57:17 c0re kernel: microcode: CPU7: patch_level=0x06000852
Sep 03 06:57:17 c0re kernel: CPU7 is up
Sep 03 06:57:17 c0re kernel: ACPI: Waking up from system sleep state S3
Sep 03 06:57:17 c0re kernel: usb usb1: root hub lost power or was reset
Sep 03 06:57:17 c0re kernel: usb usb2: root hub lost power or was reset
Sep 03 06:57:17 c0re kernel: serial 00:03: activated
Sep 03 06:57:17 c0re kernel: sd 0:0:1:0: [sda] Starting disk
Sep 03 06:57:17 c0re kernel: sd 2:0:0:0: [sdb] Starting disk
Sep 03 06:57:17 c0re kernel: sd 3:0:0:0: [sdc] Starting disk
Sep 03 06:57:17 c0re kernel: sd 4:0:0:0: [sdd] Starting disk
Sep 03 06:57:17 c0re kernel: r8169 0000:05:00.0 enp5s0: link down
Sep 03 06:57:17 c0re kernel: ata1.01: supports DRM functions and may not be fully accessible
Sep 03 06:57:17 c0re kernel: ata1.01: supports DRM functions and may not be fully accessible
Sep 03 06:57:17 c0re kernel: usb 4-3.3.2: reset full-speed USB device number 5 using ehci-pci
Sep 03 06:57:17 c0re kernel: ata1.01: Enabling discard_zeroes_data
Sep 03 06:57:17 c0re kernel: ata7: SATA link down (SStatus 0 SControl 300)
Sep 03 06:57:17 c0re kernel: ata8: SATA link down (SStatus 0 SControl 300)
Sep 03 06:57:17 c0re kernel: usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Sep 03 06:57:17 c0re kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 03 06:57:17 c0re kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 03 06:57:17 c0re kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 03 06:57:17 c0re kernel: ata3.00: supports DRM functions and may not be fully accessible
Sep 03 06:57:17 c0re kernel: ata3.00: NCQ Send/Recv Log not supported
Sep 03 06:57:17 c0re kernel: ata3.00: supports DRM functions and may not be fully accessible
Sep 03 06:57:17 c0re kernel: ata3.00: NCQ Send/Recv Log not supported
Sep 03 06:57:17 c0re kernel: ata3.00: configured for UDMA/133
Sep 03 06:57:17 c0re kernel: ata4.00: configured for UDMA/133
Sep 03 06:57:17 c0re kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd
Sep 03 06:57:17 c0re kernel: ata6.00: configured for UDMA/100
Sep 03 06:57:17 c0re kernel: firewire_core 0000:04:0e.0: rediscovered device fw0
Sep 03 06:57:17 c0re kernel: usb 1-1.2: reset high-speed USB device number 3 using xhci_hcd
Sep 03 06:57:17 c0re kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 03 06:57:17 c0re kernel: ata5.00: configured for UDMA/133
Sep 03 06:57:17 c0re kernel: r8169 0000:05:00.0 enp5s0: link up
Sep 03 06:57:17 c0re kernel: OOM killer enabled.
Sep 03 06:57:17 c0re kernel: Restarting tasks ... done.
Sep 03 06:57:17 c0re kernel: PM: suspend exit
Sep 03 06:57:17 c0re systemd-networkd[442]: enp5s0: Lost carrier
Sep 03 06:57:17 c0re systemd-networkd[442]: enp5s0: DHCP lease lost
Sep 03 06:57:17 c0re systemd-networkd[442]: enp5s0: DHCPv6 lease lost
Sep 03 06:57:17 c0re systemd-networkd[442]: enp5s0: Gained carrier
Sep 03 06:57:17 c0re systemd-sleep[1756]: System resumed.
Sep 03 06:57:17 c0re systemd-networkd[442]: enp5s0: DHCPv4 address 192.168.2.200/24 via 192.168.2.1
Sep 03 06:57:17 c0re systemd[1]: Started Suspend.
Sep 03 06:57:17 c0re systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Sep 03 06:57:17 c0re systemd[1]: Stopped target Sleep.
Sep 03 06:57:17 c0re systemd[1]: Reached target Suspend.
Sep 03 06:57:17 c0re systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Sep 03 06:57:17 c0re systemd[1]: Stopped target Suspend.
Sep 03 06:57:17 c0re systemd-logind[443]: Operation 'sleep' finished.

Last edited by psic4t (2018-09-03 06:24:46)

Offline

#5 2018-09-03 06:25:29

seth
Member
Registered: 2012-09-03
Posts: 8,665

Re: No resume from suspend

The exact same driver version on the exact same kernel? …
Briefly try the modesetting drivers on top of the nouveau kernel module (uninstall all nvidia packages) to rule out this cause - the nvidia drivers are notorious for this behavior.

How do you suspend from the mutliuser target? Lid-switch or "systemctl suspend" or  …?

Offline

#6 2018-09-04 07:45:30

psic4t
Member
Registered: 2018-08-22
Posts: 3

Re: No resume from suspend

So, tried suspend/resume with Nouveau. Same behaviour in multi-user.target. Resumes immediately.

In Ubuntu I have a different kernel and Nvidia driver version.

I susped with "systemctl suspend" (it's a PC).

Offline

#7 2018-09-12 14:54:16

seth
Member
Registered: 2012-09-03
Posts: 8,665

Re: No resume from suspend

Sorry for the delay.
The GPU driver is less relevant in the multi-user.target (which shows a behavior that desires independent investigation anyway) so for a meaningful test, try the per-driver resume behavior when the suspend actually works)

Offline

Board footer

Powered by FluxBB