Can't suspend and wakeup outside of gnome

  • Open
  • quality assurance status badge
Details
One participant
  • Stefan Huchler
Owner
unassigned
Submitted by
Stefan Huchler
Severity
normal
S
S
Stefan Huchler wrote on 24 Apr 2023 04:13
(address . bug-guix@gnu.org)
87ildmf2n6.fsf@mail.de
When I try to suspend as example with loginctl suspend, but also other
methods like dbus command sending or the echo mem > ... it sometimes
works but around 60% mostly the 2nd time never reaches fully the suspend
state but monitor is out, no suspend typical power blinking, the only
way to recover is then to shut down the pc long power button press.

Now I switched from nixos where it worked I also tried to install the
5.15 kernel so in case it's a kernel bug, but the same issue.

I run into another person on #guix irc which claimed to have the same
issue, with a totally different system, I use a amd Ryzen 5 2400G with
the vanilla kernel not linux-libre he said he used the libre kernel with
a intel system.

Did report this already to the nonguix repo.

My workaround is to have a gnome instance runnig on tty8 and switch
there to suspend it over gnome then it works always.
S
S
Stefan Huchler wrote on 26 Apr 2023 02:04
(address . bug-guix@gnu.org)
87a5yvfqzb.fsf@mail.de
here is the part of the log that should show a crash from suspend.
Apr 15 19:38:32 localhost elogind[352]: Suspending system...
Apr 15 19:38:32 localhost vmunix: [ 96.960350] PM: suspend entry (deep)
Apr 15 19:38:34 localhost vmunix: [ 96.971363] Filesystems sync: 0.011 seconds
Apr 15 19:38:34 localhost vmunix: [ 96.971643] Freezing user space processes
Apr 15 19:38:34 localhost vmunix: [ 96.972920] Freezing user space processes completed (elapsed 0.001 seconds)
Apr 15 19:38:34 localhost vmunix: [ 96.972926] OOM killer disabled.
Apr 15 19:38:34 localhost vmunix: [ 96.972927] Freezing remaining freezable tasks
Apr 15 19:38:34 localhost vmunix: [ 96.974038] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Apr 15 19:38:34 localhost vmunix: [ 96.974062] printk: Suspending console(s) (use no_console_suspend to debug)
Apr 15 19:38:34 localhost vmunix: [ 96.975397] serial 00:04: disabled
Apr 15 19:38:34 localhost vmunix: [ 96.975545] r8169 0000:02:00.0 enp2s0: Link is Down
Apr 15 19:38:34 localhost vmunix: [ 97.002210] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 15 19:38:34 localhost vmunix: [ 97.002481] sd 0:0:0:0: [sda] Stopping disk
Apr 15 19:38:34 localhost vmunix: [ 97.290213] ACPI: PM: Preparing to enter system sleep state S3
Apr 15 19:38:34 localhost vmunix: [ 97.830759] ACPI: PM: Saving platform NVS memory
Apr 15 19:38:34 localhost vmunix: [ 97.830872] Disabling non-boot CPUs ...
Apr 15 19:38:34 localhost vmunix: [ 97.830875] Wakeup pending. Abort CPU freeze
Apr 15 19:38:34 localhost vmunix: [ 97.830876] Non-boot CPUs are not disabled
Apr 15 19:38:34 localhost vmunix: [ 97.830886] ACPI: PM: Waking up from system sleep state S3
Apr 15 19:38:34 localhost vmunix: [ 98.162855] xhci_hcd 0000:03:00.3: Controller not ready at resume -19
Apr 15 19:38:34 localhost vmunix: [ 98.162881] xhci_hcd 0000:03:00.3: PCI post-resume error -19!
Apr 15 19:38:34 localhost vmunix: [ 98.162884] xhci_hcd 0000:03:00.3: HC died; cleaning up
Apr 15 19:38:34 localhost vmunix: [ 98.162892] xhci_hcd 0000:03:00.3: PM: dpm_run_callback(): pci_pm_resume+0x0/0x110
returns -19
Apr 15 19:38:34 localhost vmunix: [ 98.162908] xhci_hcd 0000:03:00.3: PM: failed to resume async: error -19
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 63045@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 63045
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch