Suspend a ram no funciona

Español (Spanish) Hardware
1

Hola.
Estoy intentando suspender el sistema pero se arranca de nuevo en solo enseguida.
Pruebo con el comando:
systemctl suspend

Esta es la salida del journalctl a ver si alguien sabe como solucionarlo :

juan@leap160:~> sudo journalctl -b --since "09:29:00" --until "09:29:30" | grep -iE 'kernel:|hardware|fail|wake'
ago 14 09:29:11 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:11 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:11 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:11 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:11 leap160 kwin_wayland[1639]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
ago 14 09:29:11 leap160 kernel: r8169 0000:04:00.0 eno1: Link is Down
ago 14 09:29:12 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:12 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:12 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:12 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:12 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:12 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:12 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:12 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:12 leap160 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
ago 14 09:29:12 leap160 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
ago 14 09:29:12 leap160 kernel: PM: suspend entry (deep)
ago 14 09:29:14 leap160 kernel: Filesystems sync: 2.382 seconds
ago 14 09:29:19 leap160 kernel: Freezing user space processes
ago 14 09:29:19 leap160 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
ago 14 09:29:19 leap160 kernel: OOM killer disabled.
ago 14 09:29:19 leap160 kernel: Freezing remaining freezable tasks
ago 14 09:29:19 leap160 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
ago 14 09:29:19 leap160 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
ago 14 09:29:19 leap160 kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
ago 14 09:29:19 leap160 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
ago 14 09:29:19 leap160 kernel: ata2.00: Entering standby power mode
ago 14 09:29:19 leap160 kernel: ata1.00: Entering standby power mode
ago 14 09:29:19 leap160 kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
ago 14 09:29:19 leap160 kernel: ACPI: PM: Preparing to enter system sleep state S3
ago 14 09:29:19 leap160 kernel: ACPI: PM: Saving platform NVS memory
ago 14 09:29:19 leap160 kernel: Disabling non-boot CPUs ...
ago 14 09:29:19 leap160 kernel: smpboot: CPU 11 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 10 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 9 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 8 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 7 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 6 is now offline
ago 14 09:29:19 leap160 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
ago 14 09:29:19 leap160 kernel: smpboot: CPU 5 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 4 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 3 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 2 is now offline
ago 14 09:29:19 leap160 kernel: smpboot: CPU 1 is now offline
ago 14 09:29:19 leap160 kernel: ACPI: PM: Low-level resume complete
ago 14 09:29:19 leap160 kernel: ACPI: PM: Restoring platform NVS memory
ago 14 09:29:19 leap160 kernel: LVT offset 0 assigned for vector 0x400
ago 14 09:29:19 leap160 kernel: Enabling non-boot CPUs ...
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
ago 14 09:29:19 leap160 kernel: CPU1 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
ago 14 09:29:19 leap160 kernel: CPU2 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x8
ago 14 09:29:19 leap160 kernel: CPU3 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 4 APIC 0xa
ago 14 09:29:19 leap160 kernel: CPU4 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 5 APIC 0xc
ago 14 09:29:19 leap160 kernel: CPU5 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
ago 14 09:29:19 leap160 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
ago 14 09:29:19 leap160 kernel: CPU6 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
ago 14 09:29:19 leap160 kernel: CPU7 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
ago 14 09:29:19 leap160 kernel: CPU8 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
ago 14 09:29:19 leap160 kernel: CPU9 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xb
ago 14 09:29:19 leap160 kernel: CPU10 is up
ago 14 09:29:19 leap160 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xd
ago 14 09:29:19 leap160 kernel: CPU11 is up
ago 14 09:29:19 leap160 kernel: ACPI: PM: Waking up from system sleep state S3
ago 14 09:29:19 leap160 kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
ago 14 09:29:19 leap160 kernel: usb usb1: root hub lost power or was reset
ago 14 09:29:19 leap160 kernel: usb usb2: root hub lost power or was reset
ago 14 09:29:19 leap160 kernel: nvme nvme0: D3 entry latency set to 8 seconds
ago 14 09:29:19 leap160 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400380000).
ago 14 09:29:19 leap160 kernel: usb 1-7: WARN: invalid context state for evaluate context command.
ago 14 09:29:19 leap160 kernel: [drm] UVD and UVD ENC initialized successfully.
ago 14 09:29:19 leap160 kernel: ata3: SATA link down (SStatus 0 SControl 330)
ago 14 09:29:19 leap160 kernel: ata6: SATA link down (SStatus 0 SControl 330)
ago 14 09:29:19 leap160 kernel: ata4: SATA link down (SStatus 0 SControl 330)
ago 14 09:29:19 leap160 kernel: nvme nvme0: 12/0/0 default/read/poll queues
ago 14 09:29:19 leap160 kernel: usb 1-7: reset full-speed USB device number 3 using xhci_hcd
ago 14 09:29:19 leap160 kernel: [drm] VCE initialized successfully.
ago 14 09:29:19 leap160 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ago 14 09:29:19 leap160 kernel: sd 1:0:0:0: [sdb] Starting disk
ago 14 09:29:19 leap160 kernel: ata2.00: configured for UDMA/133
ago 14 09:29:19 leap160 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ago 14 09:29:19 leap160 kernel: ata1.00: NCQ Send/Recv Log not supported
ago 14 09:29:19 leap160 kernel: sd 0:0:0:0: [sda] Starting disk
ago 14 09:29:19 leap160 kernel: ata1.00: NCQ Send/Recv Log not supported
ago 14 09:29:19 leap160 kernel: ata1.00: configured for UDMA/133
ago 14 09:29:19 leap160 kernel: ata1.00: Enabling discard_zeroes_data
ago 14 09:29:19 leap160 kernel: usb 1-6: reset high-speed USB device number 2 using xhci_hcd
ago 14 09:29:19 leap160 kernel: usb 1-8: WARN: invalid context state for evaluate context command.
ago 14 09:29:19 leap160 kernel: ata5: failed to resume link (SControl 0)
ago 14 09:29:19 leap160 kernel: ata5: SATA link down (SStatus 0 SControl 0)
ago 14 09:29:19 leap160 kernel: usb 1-8: reset full-speed USB device number 4 using xhci_hcd
ago 14 09:29:19 leap160 kernel: OOM killer enabled.
ago 14 09:29:19 leap160 kernel: Restarting tasks ... done.
ago 14 09:29:19 leap160 kernel: random: crng reseeded on system resumption
ago 14 09:29:19 leap160 kernel: PM: suspend exit
ago 14 09:29:19 leap160 NetworkManager[1173]: <info>  [1786692559.8412] manager: sleep: wake requested (sleeping: yes  enabled: yes)
ago 14 09:29:19 leap160 kernel: Realtek Internal NBASE-T PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
ago 14 09:29:19 leap160 kernel: r8169 0000:04:00.0 eno1: Link is Down
ago 14 09:29:22 leap160 kernel: r8169 0000:04:00.0 eno1: Link is Up - 1Gbps/Full - flow control rx/tx
ago 14 09:29:23 leap160 kscreenlocker_greet[14564]: Failed to write to the pipe: Descriptor de fichero erróneo.

Saludos.

2

Hola.
Siempre está bien proporcionar toda la información posible: Qué sistema operativo tienes (Leap, Tumbleweed, Slowroll, etc), entorno de escritorio, características técnicas de tu equipo (RAM, etc…)
Saludos.

3

Hola.
El disco de arranque está compartido entre Win11 y Leap 16.0. Esta es la configuración del equipo y lo suelo tener siempre actualizado:

imagen
imagen488×487 37.8 KB

4

“Waking up”: Eso quiere decir que un dispositivo de tu hardware no deja suspender tu gecko porque le “despierta”.

Por los mensajes que aparecen, hay varios candidatos:
El controlador USB muestra actividad ¿ratón?, la tarjeta de red esta en modo wake-on-lan, el kernel está en modo “Lockdown”

Tienes que identificar cual dispositivo despierta la siuspensión.

cat /proc/acpi/wakeup

¿Tienes Secure Boot activado en la BIOS?

5

“Secure Boot” está activado en BIOS.
Esta es la salida del comando:

imagen
imagen317×293 13.1 KB

Estos son los discos que tengo.
sda lo uso entre Win11 y Linux aunque muchas veces windows lo deja bloqueado y no puedo escribir desde linux en ese disco.
sdb es donde está instalado linux.
nvme0n1 donde está Win11

imagen
imagen491×406 34.3 KB

6

Si sabes inglés te sería más fácil y rápido de preguntar para solucionar tu problema en la sección inglesa.
Cuando tenga tiempo te explico como localizar los dispositivos que están enable del fichero wakeup.
De modo rápido, compará los valores de la columna “Sysfs node” con los valores de la primera columna de la ejecución del comando lspci
Escrito desde un móvil.

7

Gracias por la ayuda,
preguntaré a ver en la sección inglesa.

8

Desactiva el “Inicio Rapido” de Windows si quieres escribir en la particiones de Windows.

Sobre tu problema de Suspender.
Como puedes ver en la salida de los dos comandos, si comparas la primera columna del primer comando con la ultima columna del segundo comando, te dice que dispositivos tiene permisos (enabled) para “despertar” tu gecko.

:~> sudo lspci
[sudo] contraseña para root: 
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller (rev 01)
03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
20:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
20:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
22:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
26:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1)
26:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
26:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
26:00.3 Serial bus controller: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1)
27:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
27:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
27:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 xHCI Compliant Host Controller
28:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
28:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
28:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

:~> cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP0      S4    *disabled
GPP1      S4    *disabled
GPP3      S4    *disabled
GPP4      S4    *disabled
GPP5      S4    *disabled
GPP6      S4    *disabled
GPP7      S4    *disabled
GPP8      S4    *enabled   pci:0000:00:03.1
GPP9      S4    *disabled
GPPA      S4    *disabled
GPPB      S4    *disabled
GPPC      S4    *disabled
GPPD      S4    *disabled
GPPE      S4    *disabled
GPPF      S4    *disabled
GP17      S4    *enabled   pci:0000:00:07.1
XHC0      S4    *enabled   pci:0000:27:00.3
GP18      S4    *enabled   pci:0000:00:08.1
GPP2      S4    *enabled   pci:0000:00:01.3
PT21      S4    *enabled   pci:0000:20:01.0
PTXH      S4    *enabled   pci:0000:03:00.0

Fijate los nombres que aparece en la primera columna del segundo comando, los que estan enabled son: GPP8, GP17, XHC…

Puedes apagar temporalmente un dispositivo enviando su nombre de nuevo al archivo. Por ejemplo, si esta enabled es XHC:
sudo sh -c "echo XHC > /proc/acpi/wakeup"
Vuelve a probar el comando de suspensión (systemctl suspend). Si el equipo ya se queda dormido correctamente, habrás encontrado al responsable. De lo contrario, vuelve a activarlo y prueba con el siguiente dispositivo de la lista.

Cuando encuentres al culpable, lo desactivas permanetemente. Más información:

2 Likes
9

Al final entró en suspensión con los 2 últimos dispositivos que probé a poner disabled: GPP0 y GPP8.
Muchas gracias de nuevo DiabloRojo :+1:

1 Like
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.