You are not logged in.

#1 2022-11-11 11:04:49

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Can't come back from S3 suspend to RAM

I recently discovered that my computer was set to s2idle by default, but when I switched to STR with

echo deep > /sys/power/mem_sleep 

my computer does not come back entirely after trying to exit suspend. The power button light changes from "breathing" to constant, but the screen remains dark, without backlight, and I have no keyboard or trackpad functionality.

On a possibly related note, when I try to hibernate with

echo disk > /sys/power/state

The screen blanks, comes back, and then the machine just shuts off entirely.

In both cases, s3 and s4, I lose all information about what happened in the journal, I see the following in the next session's journal.

systemd-journald[322]: File /var/log/journal/2a31ac27dc0f461f88112aa464433720/system.journal corrupted or uncleanly shut down, renaming and replacing.

I tried using pm_test, and got the following for each option:

  • core:

    [  688.918571] PM: suspend entry (deep)
    [  688.922540] Filesystems sync: 0.003 seconds
    [  688.949207] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [  688.950297] OOM killer disabled.
    [  688.950298] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [  688.951583] printk: Suspending console(s) (use no_console_suspend to debug)
    [  688.952920] wlo1: deauthenticating from ::::: by local choice (Reason: 3=DEAUTH_LEAVING)
    [  689.246135] ACPI: EC: interrupt blocked
    [  689.500928] ACPI: PM: Preparing to enter system sleep state S3
    [  689.512630] ACPI: EC: event blocked
    [  689.512631] ACPI: EC: EC stopped
    [  689.512631] ACPI: PM: Saving platform NVS memory
    [  689.512665] Disabling non-boot CPUs ...
    [  689.514502] smpboot: CPU 1 is now offline
    [  689.517744] smpboot: CPU 2 is now offline
    [  689.520190] smpboot: CPU 3 is now offline
    [  689.522336] smpboot: CPU 4 is now offline
    [  689.524557] smpboot: CPU 5 is now offline
    [  689.528102] smpboot: CPU 6 is now offline
    [  689.529792] smpboot: CPU 7 is now offline
    [  689.532351] smpboot: CPU 8 is now offline
    [  689.534652] smpboot: CPU 9 is now offline
    [  689.536121] smpboot: CPU 10 is now offline
    [  689.537628] smpboot: CPU 11 is now offline
    [  689.539095] smpboot: CPU 12 is now offline
    [  689.540662] smpboot: CPU 13 is now offline
    [  689.542099] smpboot: CPU 14 is now offline
    [  689.543527] smpboot: CPU 15 is now offline
    [  689.545807] PM: suspend debug: Waiting for 5 second(s).
    [  694.547051] Enabling non-boot CPUs ...
    [  694.547098] x86: Booting SMP configuration:
    [  694.547099] smpboot: Booting Node 0 Processor 1 APIC 0x2
    [  694.548522] CPU1 is up
    [  694.548548] smpboot: Booting Node 0 Processor 2 APIC 0x4
    [  694.549978] CPU2 is up
    [  694.550001] smpboot: Booting Node 0 Processor 3 APIC 0x6
    [  694.551458] CPU3 is up
    [  694.551509] smpboot: Booting Node 0 Processor 4 APIC 0x8
    [  694.553008] CPU4 is up
    [  694.553031] smpboot: Booting Node 0 Processor 5 APIC 0xa
    [  694.554582] CPU5 is up
    [  694.554605] smpboot: Booting Node 0 Processor 6 APIC 0xc
    [  694.556252] CPU6 is up
    [  694.556277] smpboot: Booting Node 0 Processor 7 APIC 0xe
    [  694.558502] CPU7 is up
    [  694.558537] smpboot: Booting Node 0 Processor 8 APIC 0x1
    [  694.560351] CPU8 is up
    [  694.560378] smpboot: Booting Node 0 Processor 9 APIC 0x3
    [  694.562092] CPU9 is up
    [  694.562122] smpboot: Booting Node 0 Processor 10 APIC 0x5
    [  694.563883] CPU10 is up
    [  694.563916] smpboot: Booting Node 0 Processor 11 APIC 0x7
    [  694.565701] CPU11 is up
    [  694.565746] smpboot: Booting Node 0 Processor 12 APIC 0x9
    [  694.567587] CPU12 is up
    [  694.567618] smpboot: Booting Node 0 Processor 13 APIC 0xb
    [  694.569502] CPU13 is up
    [  694.569527] smpboot: Booting Node 0 Processor 14 APIC 0xd
    [  694.571468] CPU14 is up
    [  694.571501] smpboot: Booting Node 0 Processor 15 APIC 0xf
    [  694.573525] CPU15 is up
    [  694.581255] ACPI: EC: EC started
    [  694.581276] ACPI: PM: Waking up from system sleep state S3
    [  694.587108] ACPI: EC: interrupt unblocked
    [  695.058959] ACPI: EC: event unblocked
    [  695.074199] nvme nvme0: 16/0/0 default/read/poll queues
    [  695.075457] nvme nvme0: Ignoring bogus Namespace Identifiers
    [  777.776564] thunderbolt 0000:00:0d.2: failed to send driver ready to ICM
    [  777.777446] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
    [  777.778070] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
    [  777.782605] OOM killer enabled.
    [  777.782606] Restarting tasks ... done.
    [  777.782981] random: crng reseeded on system resumption
    [  777.786035] audit: type=1334 audit(1668156337.232:84): prog-id=15 op=LOAD
    [  777.796727] PM: suspend exit
  • devices:

    [ 3385.980061] PM: suspend entry (deep)
    [ 3385.984795] Filesystems sync: 0.004 seconds
    [ 3386.011913] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 3386.013372] OOM killer disabled.
    [ 3386.013373] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 3386.014556] printk: Suspending console(s) (use no_console_suspend to debug)
    [ 3386.015384] wlo1: deauthenticating from ::::: by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 3386.285596] PM: suspend debug: Waiting for 5 second(s).
    [ 3391.299082] nvme nvme0: 16/0/0 default/read/poll queues
    [ 3391.301230] nvme nvme0: Ignoring bogus Namespace Identifiers
    [ 3474.553158] thunderbolt 0000:00:0d.2: failed to send driver ready to ICM
    [ 3474.553595] OOM killer enabled.
    [ 3474.553598] Restarting tasks ... 
    [ 3474.553931] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
    [ 3474.554925] done.
    [ 3474.554938] random: crng reseeded on system resumption
    [ 3474.555061] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
    [ 3474.567564] PM: suspend exit
  • platform:

    [ 4381.677752] PM: suspend entry (deep)
    [ 4381.682607] Filesystems sync: 0.004 seconds
    [ 4381.709578] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 4381.711103] OOM killer disabled.
    [ 4381.711104] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 4381.712280] printk: Suspending console(s) (use no_console_suspend to debug)
    [ 4381.713265] wlo1: deauthenticating from ::::: by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 4381.724651] queueing ieee80211 work while going to suspend
    [ 4381.724652] queueing ieee80211 work while going to suspend
    [ 4382.011642] ACPI: EC: interrupt blocked
    [ 4382.263284] ACPI: PM: Preparing to enter system sleep state S3
    [ 4382.274442] ACPI: EC: event blocked
    [ 4382.274443] ACPI: EC: EC stopped
    [ 4382.274443] ACPI: PM: Saving platform NVS memory
    [ 4382.274468] PM: suspend debug: Waiting for 5 second(s).
    [ 4387.274725] ACPI: EC: EC started
    [ 4387.274729] ACPI: PM: Waking up from system sleep state S3
    [ 4387.280743] ACPI: EC: interrupt unblocked
    [ 4387.658095] ACPI: EC: event unblocked
    [ 4387.672634] nvme nvme0: 16/0/0 default/read/poll queues
    [ 4387.673898] nvme nvme0: Ignoring bogus Namespace Identifiers
    [ 4471.129629] thunderbolt 0000:00:0d.2: failed to send driver ready to ICM
    [ 4471.130624] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
    [ 4471.131255] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
    [ 4471.135256] OOM killer enabled.
    [ 4471.135257] Restarting tasks ... 
    [ 4471.135590] Core dump to |/usr/lib/systemd/systemd-coredump pipe failed
    [ 4471.135701] audit: type=1701 audit(1668162980.610:122): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=328 comm="systemd-udevd" exe="/usr/bin/udevadm" sig=6 res=1
    [ 4471.136084] done.
    [ 4471.136089] random: crng reseeded on system resumption
    [ 4471.136461] audit: type=1131 audit(1668162980.613:123): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
    [ 4471.137114] audit: type=1130 audit(1668162980.613:124): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    [ 4471.137120] audit: type=1131 audit(1668162980.613:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    [ 4471.137449] audit: type=1334 audit(1668162980.613:126): prog-id=15 op=LOAD
    [ 4471.137467] audit: type=1334 audit(1668162980.613:127): prog-id=16 op=LOAD
    [ 4471.147525] PM: suspend exit
  • processors:

    [ 3034.175235] PM: suspend entry (deep)
    [ 3034.178706] Filesystems sync: 0.003 seconds
    [ 3034.205535] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 3034.207055] OOM killer disabled.
    [ 3034.207056] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 3034.208233] printk: Suspending console(s) (use no_console_suspend to debug)
    [ 3034.209197] wlo1: deauthenticating from ::::: by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 3034.504847] ACPI: EC: interrupt blocked
    [ 3034.766492] ACPI: PM: Preparing to enter system sleep state S3
    [ 3034.780815] ACPI: EC: event blocked
    [ 3034.780817] ACPI: EC: EC stopped
    [ 3034.780818] ACPI: PM: Saving platform NVS memory
    [ 3034.780880] Disabling non-boot CPUs ...
    [ 3034.783456] smpboot: CPU 1 is now offline
    [ 3034.789957] smpboot: CPU 2 is now offline
    [ 3034.793959] smpboot: CPU 3 is now offline
    [ 3034.796651] smpboot: CPU 4 is now offline
    [ 3034.799366] smpboot: CPU 5 is now offline
    [ 3034.801595] smpboot: CPU 6 is now offline
    [ 3034.804030] smpboot: CPU 7 is now offline
    [ 3034.806766] smpboot: CPU 8 is now offline
    [ 3034.809576] smpboot: CPU 9 is now offline
    [ 3034.811165] smpboot: CPU 10 is now offline
    [ 3034.812794] smpboot: CPU 11 is now offline
    [ 3034.814318] smpboot: CPU 12 is now offline
    [ 3034.815957] smpboot: CPU 13 is now offline
    [ 3034.817575] smpboot: CPU 14 is now offline
    [ 3034.819057] smpboot: CPU 15 is now offline
    [ 3034.819291] PM: suspend debug: Waiting for 5 second(s).
    [ 3039.819551] Enabling non-boot CPUs ...
    [ 3039.819597] x86: Booting SMP configuration:
    [ 3039.819598] smpboot: Booting Node 0 Processor 1 APIC 0x2
    [ 3039.821028] CPU1 is up
    [ 3039.821052] smpboot: Booting Node 0 Processor 2 APIC 0x4
    [ 3039.822497] CPU2 is up
    [ 3039.822520] smpboot: Booting Node 0 Processor 3 APIC 0x6
    [ 3039.823976] CPU3 is up
    [ 3039.823998] smpboot: Booting Node 0 Processor 4 APIC 0x8
    [ 3039.825448] CPU4 is up
    [ 3039.825470] smpboot: Booting Node 0 Processor 5 APIC 0xa
    [ 3039.827008] CPU5 is up
    [ 3039.827031] smpboot: Booting Node 0 Processor 6 APIC 0xc
    [ 3039.828676] CPU6 is up
    [ 3039.828698] smpboot: Booting Node 0 Processor 7 APIC 0xe
    [ 3039.830459] CPU7 is up
    [ 3039.830482] smpboot: Booting Node 0 Processor 8 APIC 0x1
    [ 3039.832296] CPU8 is up
    [ 3039.832324] smpboot: Booting Node 0 Processor 9 APIC 0x3
    [ 3039.834031] CPU9 is up
    [ 3039.834068] smpboot: Booting Node 0 Processor 10 APIC 0x5
    [ 3039.835806] CPU10 is up
    [ 3039.835834] smpboot: Booting Node 0 Processor 11 APIC 0x7
    [ 3039.837594] CPU11 is up
    [ 3039.837627] smpboot: Booting Node 0 Processor 12 APIC 0x9
    [ 3039.839436] CPU12 is up
    [ 3039.839467] smpboot: Booting Node 0 Processor 13 APIC 0xb
    [ 3039.841342] CPU13 is up
    [ 3039.841375] smpboot: Booting Node 0 Processor 14 APIC 0xd
    [ 3039.843317] CPU14 is up
    [ 3039.843353] smpboot: Booting Node 0 Processor 15 APIC 0xf
    [ 3039.845381] CPU15 is up
    [ 3039.853110] ACPI: EC: EC started
    [ 3039.853133] ACPI: PM: Waking up from system sleep state S3
    [ 3039.857731] ACPI: button: The lid device is not compliant to SW_LID.
    [ 3039.859319] ACPI: EC: interrupt unblocked
    [ 3041.822472] pcieport 0000:00:1c.0: Data Link Layer Link Active not set in 1000 msec
    [ 3041.822585] igc 0000:2e:00.0: Unable to change power state from D3cold to D0, device inaccessible
    [ 3041.888573] ACPI: EC: event unblocked
    [ 3041.900522] nvme nvme0: 16/0/0 default/read/poll queues
    [ 3041.901740] igc 0000:2e:00.0: Unable to change power state from D3cold to D0, device inaccessible
    [ 3041.902146] nvme nvme0: Ignoring bogus Namespace Identifiers
    [ 3041.903858] igc 0000:2e:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -19
    [ 3041.903864] igc 0000:2e:00.0: PM: failed to resume async: error -19
    [ 3124.686196] thunderbolt 0000:00:0d.2: failed to send driver ready to ICM
    [ 3124.687207] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
    [ 3124.687838] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
    [ 3124.691996] OOM killer enabled.
    [ 3124.691997] Restarting tasks ... done.
    [ 3124.692632] random: crng reseeded on system resumption
    [ 3124.692879] igc 0000:2e:00.0 enp46s0: PHC removed
    [ 3124.704991] PM: suspend exit

The one thing I noticed was the significant time leading up to the thunderbolt issue, which I believe is a separate problem with thunderbolt. Doing this again after unloading the thunderbolt module, removes that time gap entirely, and does not fix the issue if I suspend to ram, without using pm_test.

Edit: Also, I am unable to ssh into my computer while this is happening. So I don't think it's just an issue with the screen/keyboard.

Last edited by swamp_rabbit (2022-11-11 11:08:59)

Offline

#2 2022-11-11 12:35:39

seth
Member
Registered: 2012-09-03
Posts: 35,166

Re: Can't come back from S3 suspend to RAM

Hibernation needs some preparation:
https://wiki.archlinux.org/title/Power_ … ibernation

Is there a parallel windows installation?
(3rd link below…)

Online

#3 2022-11-11 14:03:12

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Re: Can't come back from S3 suspend to RAM

Right, I still have some setting up to do for hibernation.

I have windows installed on a separate SSD plugged into the second slot on my laptop. Could that still have an effect? Either way, I'm fairly certain I disabled fast startup when I first got this laptop. I'll have to check in a moment.

Would fast startup cause problems for suspend to RAM? That's what I'm mainly concerned with at the moment.

Offline

#4 2022-11-11 14:08:51

d.ALT
Member
Registered: 2019-05-10
Posts: 563

Re: Can't come back from S3 suspend to RAM

swamp_rabbit wrote:

Either way, I'm fairly certain I disabled fast startup when I first got this laptop. I'll have to check in a moment.

Windows Updates happens to silently re-enable Fast Startup sometimes.


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#5 2022-11-11 14:09:37

seth
Member
Registered: 2012-09-03
Posts: 35,166

Re: Can't come back from S3 suspend to RAM

Could that still have an effect?

Yes.

Would fast startup cause problems for suspend to RAM?

Yes. Next to devices randomly not showing up, anything involving the ACPI is almost guaranteed to be affected by a hibernating windows (what "fast start" really is)

Online

#6 2022-11-12 07:02:27

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Re: Can't come back from S3 suspend to RAM

Alright, so I just booted into windows, and fast startup was not enabled, but neither was hibernate. I enabled hibernate, just to see if that would somehow affect suspend-to-ram, and I basically got the same result when I tried to STR.

Any other ideas? Any information that might be useful? I really wish I could see a log of what was happening when I tried to leave suspend, but I guess it gets corrupted and deleted.

Offline

#7 2022-11-12 08:24:55

seth
Member
Registered: 2012-09-03
Posts: 35,166

Re: Can't come back from S3 suspend to RAM

[ 3041.822585] igc 0000:2e:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 3041.901740] igc 0000:2e:00.0: Unable to change power state from D3cold to D0, device inaccessible
[ 3041.903858] igc 0000:2e:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -19
[ 3041.903864] igc 0000:2e:00.0: PM: failed to resume async: error -19

That's your ethernet.
Stop your network manager, bring the NIC down and "modprobe -r igc" the module before you suspend.
Do you have WOL enabled?

Online

#8 2022-11-12 13:54:51

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Re: Can't come back from S3 suspend to RAM

Turned off ethernet controller, disabled WOL, and network controller, and did "modprobe -r igc." Same result. WOL was enabled before.

Offline

#9 2022-11-12 18:08:15

seth
Member
Registered: 2012-09-03
Posts: 35,166

Re: Can't come back from S3 suspend to RAM

What kidn of device is this exactly?
Is there a dock involved and for a (likely) notbook, does it matter whether you're on battery or AC?

Online

#10 2022-11-13 08:30:22

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Re: Can't come back from S3 suspend to RAM

It's a notebook. Specifically: ADATA XPG Xenia 15 kc

No dock. I just tried to suspend on battery, same issue.

Offline

#11 2022-11-13 16:04:21

seth
Member
Registered: 2012-09-03
Posts: 35,166

Re: Can't come back from S3 suspend to RAM

This seems to be a NUC M15

https://www.intel.com/content/www/us/en … l-nuc.html
Next to the BIOS settings, you can also try to pass "pcie_aspm=off" to the kernel.

nb. that either might result in higher battery drain.

Online

#12 2022-11-25 12:22:21

swamp_rabbit
Member
Registered: 2022-04-05
Posts: 27

Re: Can't come back from S3 suspend to RAM

I had to take a break from trying to figure this out.

As an aside I did get hibernate working properly, so that was an unrelated issue. Although, for some reason short pressing the power button still shuts down the machine. Just needed to RTFM

I found that s3 also doesn't work on windows, so I think it was intentionally disabled by manufacturers, which is fucked. I was unable to find the relevant settings in BIOS that were listed in the link you posted.

Passing "pcie_aspm=off" to the kernel did not change anything.

Last edited by swamp_rabbit (2022-11-25 12:35:29)

Offline

#13 2022-11-26 01:10:35

Strangiato
Member
Registered: 2020-01-10
Posts: 246

Re: Can't come back from S3 suspend to RAM

swamp_rabbit wrote:

my computer does not come back entirely after trying to exit suspend. The power button light changes from "breathing" to constant, but the screen remains dark, without backlight, and I have no keyboard or trackpad functionality.

My desktop computer has exactly the same symptoms. I even tested the lts kernel.

Offline

#14 2022-11-26 02:04:04

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,127

Re: Can't come back from S3 suspend to RAM

swamp_rabbit wrote:

I found that s3 also doesn't work on windows, so I think it was intentionally disabled by manufacturers, which is fucked.

Yes. There seems to be a move to 'replace' s3 with s2idle i.e. to remove s3. From the random stuff I've seen, the official story is that s2idle will achieve similar power savings but faster resume. Since s2idle is already an option on machines with s3, I assume there's an unofficial story.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

Board footer

Powered by FluxBB