Início / ubuntu / 问题

Perguntas[suspend](ubuntu)

Martin Hope
IndexOutOfBoundsException
Asked: 2024-10-12 22:55:42 +0800 CST
  • 5

De vez em quando, meu sistema não está suspendendo corretamente. Fechar a tampa, escolher suspender na interface gráfica ou executar um comando está desligando a tela, mas o sistema voltará a funcionar após alguns segundos. Executar a solução de problemas mostra que alguns dispositivos estão bloqueando a suspensão do sistema. O que pode ser feito para permitir que meu sistema suspenda?

suspend
Martin Hope
umpirsky
Asked: 2024-08-14 02:19:19 +0800 CST
  • 7

De repente, colocar o sistema para hibernar começou a falhar, aqui está o link completo /var/log/syslog https://gist.github.com/umpirsky/f3e1a8d32217ad4b8fb3186124866d69

Desativei todas as entradas /proc/acpi/wakeup, não ajudou.

Ubuntu 22.04.4LTS

Alguma ideia de por que isso começou a acontecer? Obrigado.

suspend
Martin Hope
Victor Gray
Asked: 2024-07-03 15:29:03 +0800 CST
  • 5

Meu novo computador, com CPU AMD Ryzen 5 7600 e rodando Ubuntu 24.04, acorda sozinho imediatamente após a suspensão. A execução systemctl suspendresulta no sistema aparentemente entrando no estado de suspensão (a tela fica preta, a energia dos dispositivos externos é desligada), seguida logo após o despertar. Todo o processo leva alguns segundos, embora a energia dos dispositivos externos (visto por uma luz no meu mouse com fio) fique desligada por menos de 1 segundo.

Encontrei várias outras pessoas perguntando sobre esse mesmo problema, e o único conselho que encontrei sobre como determinar o que está despertando o computador é (a) inspecionar os logs para descobrir o que está despertando o computador, por exemplo, via sudo journalctl --since="-5 minutes"ou sudo dmesg -T | tail -n 200ou cat /var/log/syslog. Tudo isso parece fornecer a mesma informação, o que para mim inclui linhas para o computador entrar no modo de suspensão e desabilitar CPUs e, em seguida, reiniciar imediatamente. Não vejo nenhuma indicação de por que ele está despertando.

smpboot: CPU 11 is now offline
kernel: ACPI: PM: Low-level resume complete
kernel: ACPI: PM: Restoring platform NVS memory
kernel: AMD-Vi: Virtual APIC enabled
kernel: AMD-Vi: Virtual APIC enabled
kernel: LVT offset 0 assigned for vector 0x400
kernel: Enabling non-boot CPUs ...

(b) desabilitar a capacidade de vários dispositivos de ativar o computador via echo XHC0 > /proc/acpi/wakeup Eu fiz isso e desabilitei todos os dispositivos listados em /proc/acpi/wakeup. cat /proc/acpi/wakeup | grep enanão produz nada. Mesmo assim, meu computador continua a despertar imediatamente.

(c) systemd-inhibit: Descubra o que pode estar bloqueando a suspensão com systemd-inhibit --list --mode=block. Quando executo isso, obtenho um resultado, do GNOME. Consegui desabilitar isso incluindo InhibitorsMax=0em /etc/systemd/logind.conf. Após a reinicialização, o comando list não mostra resultados. Meu computador continua a despertar imediatamente, embora agora demore um pouco mais e a tela não apareça até que eu mova o mouse ou pressione uma tecla no teclado. Repetir a solução de (b), desabilitando todos os dispositivos em /proc/acpi/wakeup, novamente não tem efeito.

(d) alterar as configurações do BIOS: só vejo opções para ativação do teclado e do mouse nas configurações do BIOS. O mouse está desligado. Não quero desligar o teclado, mas testei se o computador ainda desperta automaticamente quando o teclado é desconectado.

Também tentei hibernar, que parece ter acabado de desligar o computador. Ligá-lo novamente resultou em uma inicialização normal. EDIT: Consegui fazer a hibernação funcionar agora, o que é bom, mas não resolve o problema da suspensão.

Wake on LAN está desativado. sudo ethtool enp4s0mostra Wake-on: d. (Nenhuma das outras duas interfaces Ethernet mostradas por ip atem uma entrada para Wake-on.) Também suspendi com o mouse desconectado, por precaução, e novamente com o teclado desconectado, apenas por precaução. Nenhum destes teve qualquer efeito.

O que mais posso fazer para solucionar ou possivelmente resolver esse problema?

suspend
Martin Hope
Moksh Chitkara
Asked: 2024-03-05 13:17:25 +0800 CST
  • 10

Eu só quero que meu laptop continue funcionando normalmente com a tampa fechada. Analisei várias perguntas semelhantes e já tentei os métodos abaixo. Qualquer ajuda seria muito apreciada.

Métodos que tentei:

  • Gnome Tweaks - desative a suspensão automática ao fechar a tampa
  • editar/etc/systemd/logind.conf 
    HandleLidSwitch=ignore
HandleListSwitchExternalPower=ignore
HandleLidSwitchDocked=ignore
LidSwitchIgnoreInhibited=no

Estou usando:

  • ID do Distribuidor: Ubuntu
  • Descrição: Ubuntu 22.04.4 LTS
  • Lançamento: 22.04
  • Codinome: jammy

Detalhes do portátil:

  • ASUS ROG GL552VW-DH71
  • GPU GeForce GTX 960M 2GB VRAM
  • 16GB DDR4
  • Processador Intel i7
suspend
Martin Hope
jon
Asked: 2024-01-18 17:25:52 +0800 CST
  • 5

Depois de atualizar de 23.04 para 23.10, meu laptop não consegue dormir: ao tentar dormir, ele acorda imediatamente novamente. Isso ocorre quando nenhum periférico (qualquer coisa Bluetooth, teclado, monitor, etc.) também está conectado.

Eu tentei alternar "dispositivos de ativação" /proc/acpi/wakeupcomo no Ubuntu acorda após alguns segundos de suspensão , mas desabilitar todos eles não impediu que o computador acordasse imediatamente.

Qualquer ajuda muito apreciada!

suspend
Martin Hope
Anon2482
Asked: 2023-07-29 21:21:51 +0800 CST
  • 6

Estou com um problema em um Asus VivoBook 17 no Ubuntu 22.04 (instalação limpa)
Tudo parece funcionar bem, exceto o modo de suspensão: depois, o computador não quer fazer nada: tela preta (como em suspensão) e clique do mouse / trackpad / teclado não faz nada, tenho que apertar o botão liga / desliga 5 segundos para forçar o computador a ficar em espera. Após uma reinicialização, funciona bem (até suspender...)

Na inicialização, vi isso (brevemente):

12:33:10 kernel: FAT-fs (sdc1): unable to read boot sector to mark fs as dirty
11:51:13 systemd: Failed to start Application launched by gnome-session-binary.
11:51:04 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xe57d2000-0xe57d2fff]
11:51:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)

Então atualizei o BIOS da versão 302 (ou algo assim) para 310 (Número de série: X705QA)
Mas não mudou nada.

Como visto nesta pergunta: o Ubuntu 22.04 não vai acordar do modo de espera que pode ser devido aos drivers. Mas nenhum driver adicional foi encontrado (apenas um para placa wifi, mas o WiFi funciona bem, então não mudei isso)

Eu não sei como fazer isso; alguém aqui tem uma ideia?

Algumas informações :

$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models
60h-6fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev ca)
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini
HDMI/DP Audio
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Host Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Root Port
00:02.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Root Port
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Root Port
00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD]
Carrizo Platform Security Processor
00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Carrizo Audio
Dummy Host Bridge
00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Audio Controller
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI
Controller (rev 20)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA
Controller [AHCI mode] (rev 49)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI
Controller (rev 49)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
(rev 4a)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
(rev 11)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h
(Models 60h-6fh) Processor Function 5
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
802.11ac PCIe Wireless Network Adapter
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

$ lsusb
Bus 001 Device 004: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam
Bus 001 Device 003: ID 13d3:3529 IMC Networks Bluetooth Radio
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129
Card Reader Controller
Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Computador :

ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X705QA_R702QA
Asus VivoBook 17
Serial Number : X705QA
BIOS version 310 (updated from 302?)
AMD® A10-9620p radeon r5, 10 compute cores 4c+6g × 4
CARRIZO (carrizo, LLVM 15.0.7, DRM 3.47, 5.19.0-50-generic)

Também alguns logs de uma sessão onde fiz o computador suspender

12:36:26 gdm-session-wor: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=  user=fred
12:36:25 gnome-shell: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23

12:36:25 systemd: Started Fingerprint Authentication Daemon.
12:36:25 dbus-daemon: [system] Successfully activated service 'net.reactivated.Fprint'
12:36:25 fprintd: Failed to install a sleep delay inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
12:36:25 systemd: Starting Fingerprint Authentication Daemon...
12:36:25 dbus-daemon: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.45' (uid=1000 pid=1092 comm="/usr/bin/gnome-shell " label="unconfined")
12:36:21 wpa_supplicant: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
12:36:21 NetworkManager: <info>  [1690626981.4095] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
12:36:21 systemd-resolve: wlp1s0: Bus client reset DNS server list.
12:36:21 avahi-daemon: Interface wlp1s0.IPv4 no longer relevant for mDNS.
12:36:21 NetworkManager: <info>  [1690626981.3771] dhcp4 (wlp1s0): state changed no lease
12:36:21 gnome-shell: An active wireless connection, in infrastructure mode, involves no access point?
12:36:21 avahi-daemon: Interface wlp1s0.IPv6 no longer relevant for mDNS.
12:36:21 NetworkManager: <info>  [1690626981.3511] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
12:36:21 wpa_supplicant: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
12:36:21 systemd: Started Network Manager Script Dispatcher Service.
12:36:21 dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
12:36:21 systemd: Starting Network Manager Script Dispatcher Service...
12:36:21 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=741 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
12:36:21 ModemManager: <info>  [sleep-monitor-systemd] system is about to suspend
12:36:14 update-notifier: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
12:35:57 systemd: app-gnome-thunderbird-5707.scope: Consumed 39.844s CPU time.
12:34:54 wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=40500
12:33:28 systemd: NetworkManager-dispatcher.service: Deactivated successfully.
12:33:24 gnome-shell: Window manager warning: last_focus_time (2544325) is greater than comparison timestamp (2544324).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
12:33:18 wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=117000
12:33:18 systemd: Started Network Manager Script Dispatcher Service.
12:33:18 dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
12:33:18 systemd: Starting Network Manager Script Dispatcher Service...
12:33:18 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=741 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
12:33:18 NetworkManager: <info>  [1690626798.2210] dhcp4 (wlp1s0): state changed new lease, address=192.168.0.18
12:33:16 wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=292500
12:33:16 NetworkManager: <info>  [1690626796.0548] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
12:33:16 wpa_supplicant: wlp1s0: CTRL-EVENT-CONNECTED - Connection to dc:00:b0:b5:c1:5c completed [id=0 id_str=]
12:33:16 NetworkManager: <info>  [1690626796.0157] device (wlp1s0): supplicant interface state: associating -> 4way_handshake
12:33:16 kernel: wlp1s0: associated
12:33:15 NetworkManager: <info>  [1690626795.9989] device (wlp1s0): ip:dhcp4: restarting
12:33:15 wpa_supplicant: wlp1s0: Trying to associate with dc:00:b0:b5:c1:5c (SSID='freebox_LSSIZN' freq=5200 MHz)
12:33:10 systemd: media-fred-USB.mount: Deactivated successfully.
12:33:10 kernel: FAT-fs (sdc1): unable to read boot sector to mark fs as dirty
12:33:10 udisksd: Cleaning up mount point /media/fred/USB (device 8:33 no longer exists)
12:33:10 kernel: usb 1-1.2: USB disconnect, device number 5
12:33:08 gnome-shell: JS ERROR: TypeError: this.window_container is null
hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9
vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26

12:33:03 wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=1000
12:32:48 systemd: systemd-hostnamed.service: Deactivated successfully.
12:32:39 avahi-daemon: Registering new address record for 2a01:e0a:5b6:f0c0:8a74:d281:4ce0:664b on wlp1s0.*.
12:32:37 systemd-resolve: wlp1s0: Bus client set DNS server list to: 192.168.0.200, 1.1.1.1, 2a01:e0a:5b6:f0c0:5df2:eed0:37f1:5b9c, 2606:4700:4700::1111
12:32:37 avahi-daemon: Withdrawing address record for fe80::3e69:a166:d584:e0f5 on wlp1s0.
12:32:37 NetworkManager: <info>  [1690626757.4322] policy: set 'freebox_LSSIZN' (wlp1s0) as default for IPv6 routing and DNS
12:32:35 wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=26000

desde já, obrigado

EDITAR:

$ sudo dmesg | grep -i tpm
[    0.000000] efi: TPMFinalLog=0xe579a000 ACPI 2.0=0xe5699000
ACPI=0xe5699000 SMBIOS=0xe5a00000 SMBIOS 3.0=0xe59ff000 ESRT=0xe32a2b18
MEMATTR=0xe329c018 MOKvar=0xe5883000 RNG=0xe5698018 TPMEventLog=0xe20e3018
[    0.007250] ACPI: TPM2 0x00000000E56B54D8 000034 (v04 _ASUS_ Notebook
00000001 AMI  00000000)
[    0.007304] ACPI: Reserving TPM2 table memory at [mem
0xe56b54d8-0xe56b550b]
[    1.166879] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
cover the entire command/response buffer. [mem 0xe57d2000-0xe57d2fff
flags 0x200] vs e57d2000 4000
[    1.166896] tpm_crb MSFT0101:00: can't request region for resource
[mem 0xe57d2000-0xe57d2fff]
[    1.166902] tpm_crb: probe of MSFT0101:00 failed with error -16
[    1.267930] ima: No TPM chip found, activating TPM-bypass!

$ journalctl --grep='sleep|suspend|resume' --no-pager --since='-1day'
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.1930]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.1932]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 11:06:59 pc-fred ModemManager[850]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.2074]
manager: NetworkManager state is now ASLEEP
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.2088]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.3978]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 11:06:59 pc-fred NetworkManager[742]: <info> [1690621619.4551]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 11:07:00 pc-fred systemd[1]: Reached target Sleep.
juil. 29 11:07:00 pc-fred systemd[1]: Starting System Suspend...
juil. 29 11:07:00 pc-fred systemd-sleep[9853]: Entering sleep state
'suspend'...
juil. 29 11:07:00 pc-fred kernel: PM: suspend entry (deep)
-- Boot 8eb1c29676604afb978454772236921d --
juil. 29 11:17:22 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 11:17:22 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 11:17:22 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 11:17:22 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 11:17:22 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 11:17:29 pc-fred systemd-logind[795]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot 91dc9f8c3198476d8b86571ad215f6b8 --
juil. 29 11:29:23 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 11:29:23 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 11:29:23 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 11:29:23 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 11:29:23 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 11:29:30 pc-fred systemd-logind[796]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot 674fc68e33c84c12bffcae069959c1a0 --
juil. 29 11:40:59 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 11:40:59 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 11:40:59 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 11:40:59 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 11:40:59 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 11:41:06 pc-fred systemd-logind[840]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot 9d53812554664f7ba75b88e8e305f30e --
juil. 29 11:48:17 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 11:48:17 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 11:48:17 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 11:48:17 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 11:48:17 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 11:48:25 pc-fred systemd-logind[853]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot db095f9eb42e47b6ae2eabe6d6f6083b --
juil. 29 11:51:04 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 11:51:04 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 11:51:04 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 11:51:04 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 11:51:04 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 11:51:11 pc-fred systemd-logind[794]: Watching system buttons
on /dev/input/event2 (Sleep Button)
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.1701]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.1703]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.1806]
manager: NetworkManager state is now ASLEEP
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.1813]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 12:36:21 pc-fred ModemManager[839]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.3511]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 12:36:21 pc-fred NetworkManager[741]: <info> [1690626981.4095]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 12:36:25 pc-fred fprintd[6321]: Failed to install a sleep delay
inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgress: The
operation inhibition has been requested for is already running
-- Boot f2d9a40e84fc4055b1a4937c1a8f16d9 --
juil. 29 12:36:54 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 12:36:54 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 12:36:54 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 12:36:54 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 12:36:54 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 12:37:01 pc-fred systemd-logind[794]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot aa353a3787734f2e9bd049f8b287d5b5 --
juil. 29 12:44:41 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 12:44:41 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 12:44:41 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 12:44:41 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 12:44:41 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 12:44:47 pc-fred systemd-logind[773]: Watching system buttons
on /dev/input/event2 (Sleep Button)
-- Boot 9e4c8f9cbe1b443ba46507edcf1914f1 --
juil. 29 13:48:56 pc-fred kernel: BIOS may not properly restore RDRAND
after suspend, hiding RDRAND via CPUID. Use rdrand=force to reenable.
juil. 29 13:48:56 pc-fred kernel: input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
juil. 29 13:48:56 pc-fred kernel: ACPI: button: Sleep Button [SLPB]
juil. 29 13:48:56 pc-fred kernel: x86/pm: family 0x15 cpu detected, MSR
saving is needed during suspending.
juil. 29 13:48:56 pc-fred kernel: ata1.00: Features: Dev-Sleep
juil. 29 13:49:02 pc-fred systemd-logind[779]: Watching system buttons
on /dev/input/event2 (Sleep Button)
juil. 29 13:54:27 pc-fred NetworkManager[738]: <info> [1690631667.7620]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 13:54:27 pc-fred NetworkManager[738]: <info> [1690631667.7622]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 13:54:27 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 13:54:27 pc-fred NetworkManager[738]: <info> [1690631667.7736]
manager: NetworkManager state is now ASLEEP
juil. 29 13:54:27 pc-fred NetworkManager[738]: <info> [1690631667.7741]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 13:54:27 pc-fred NetworkManager[738]: <info> [1690631667.9743]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 13:54:28 pc-fred NetworkManager[738]: <info> [1690631668.0232]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 13:54:29 pc-fred systemd[1]: Reached target Sleep.
juil. 29 13:54:29 pc-fred systemd[1]: Starting System Suspend...
juil. 29 13:54:29 pc-fred systemd-sleep[6151]: Entering sleep state
'suspend'...
juil. 29 13:54:29 pc-fred kernel: PM: suspend entry (deep)
juil. 29 14:18:53 pc-fred kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
juil. 29 14:18:53 pc-fred kernel: ACPI: PM: Preparing to enter system
sleep state S3
juil. 29 14:18:53 pc-fred kernel: ACPI: PM: Low-level resume complete
juil. 29 14:18:53 pc-fred kernel: ACPI: PM: Waking up from system sleep
state S3
juil. 29 14:18:53 pc-fred kernel: PM: suspend exit
juil. 29 14:18:53 pc-fred systemd-sleep[6151]: System returned from
sleep state.
juil. 29 14:18:53 pc-fred systemd[1]: systemd-suspend.service:
Deactivated successfully.
juil. 29 14:18:53 pc-fred systemd[1]: Finished System Suspend.
juil. 29 14:18:53 pc-fred systemd[1]: Stopped target Sleep.
juil. 29 14:18:53 pc-fred systemd[1]: Reached target Suspend.
juil. 29 14:18:53 pc-fred systemd[1]: Stopped target Suspend.
juil. 29 14:18:53 pc-fred systemd-logind[779]: Operation 'sleep' finished.
juil. 29 14:18:53 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is resuming
juil. 29 14:18:53 pc-fred NetworkManager[738]: <info> [1690633133.9936]
manager: sleep: wake requested (sleeping: yes enabled: yes)
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.4670]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.4672]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 14:29:53 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.4810]
manager: NetworkManager state is now ASLEEP
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.4814]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.6898]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 14:29:53 pc-fred NetworkManager[738]: <info> [1690633793.7578]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 14:29:54 pc-fred systemd[1]: Reached target Sleep.
juil. 29 14:29:54 pc-fred systemd[1]: Starting System Suspend...
juil. 29 14:29:54 pc-fred systemd-sleep[6684]: Entering sleep state
'suspend'...
juil. 29 14:29:54 pc-fred kernel: PM: suspend entry (deep)
juil. 29 15:21:13 pc-fred kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
juil. 29 15:21:13 pc-fred kernel: ACPI: PM: Preparing to enter system
sleep state S3
juil. 29 15:21:13 pc-fred kernel: ACPI: PM: Low-level resume complete
juil. 29 15:21:13 pc-fred kernel: ACPI: PM: Waking up from system sleep
state S3
juil. 29 15:21:13 pc-fred kernel: PM: suspend exit
juil. 29 15:21:13 pc-fred systemd-sleep[6684]: System returned from
sleep state.
juil. 29 15:21:14 pc-fred systemd[1]: systemd-suspend.service:
Deactivated successfully.
juil. 29 15:21:14 pc-fred systemd[1]: Finished System Suspend.
juil. 29 15:21:14 pc-fred systemd[1]: Stopped target Sleep.
juil. 29 15:21:14 pc-fred systemd[1]: Reached target Suspend.
juil. 29 15:21:14 pc-fred systemd[1]: Stopped target Suspend.
juil. 29 15:21:14 pc-fred systemd-logind[779]: Operation 'sleep' finished.
juil. 29 15:21:14 pc-fred NetworkManager[738]: <info> [1690636874.0295]
manager: sleep: wake requested (sleeping: yes enabled: yes)
juil. 29 15:21:14 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is resuming
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.1354]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.1357]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 16:06:00 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.1469]
manager: NetworkManager state is now ASLEEP
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.1472]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.3602]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 16:06:00 pc-fred NetworkManager[738]: <info> [1690639560.4017]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 16:06:01 pc-fred systemd[1]: Reached target Sleep.
juil. 29 16:06:01 pc-fred systemd[1]: Starting System Suspend...
juil. 29 16:06:01 pc-fred systemd-sleep[10673]: Entering sleep state
'suspend'...
juil. 29 16:06:01 pc-fred kernel: PM: suspend entry (deep)
juil. 29 18:01:26 pc-fred kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
juil. 29 18:01:26 pc-fred kernel: ACPI: PM: Preparing to enter system
sleep state S3
juil. 29 18:01:26 pc-fred kernel: ACPI: PM: Low-level resume complete
juil. 29 18:01:26 pc-fred kernel: ACPI: PM: Waking up from system sleep
state S3
juil. 29 18:01:26 pc-fred kernel: PM: suspend exit
juil. 29 18:01:26 pc-fred systemd-sleep[10673]: System returned from
sleep state.
juil. 29 18:01:26 pc-fred systemd[1]: systemd-suspend.service:
Deactivated successfully.
juil. 29 18:01:26 pc-fred systemd[1]: Finished System Suspend.
juil. 29 18:01:26 pc-fred systemd[1]: Stopped target Sleep.
juil. 29 18:01:26 pc-fred systemd[1]: Reached target Suspend.
juil. 29 18:01:26 pc-fred systemd[1]: Stopped target Suspend.
juil. 29 18:01:26 pc-fred systemd-logind[779]: Operation 'sleep' finished.
juil. 29 18:01:26 pc-fred NetworkManager[738]: <info> [1690646486.9547]
manager: sleep: wake requested (sleeping: yes enabled: yes)
juil. 29 18:01:26 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is resuming
juil. 29 20:27:01 pc-fred ModemManager[827]: <info>
[sleep-monitor-systemd] system is about to suspend
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.7095]
manager: sleep: sleep requested (sleeping: no enabled: yes)
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.7096]
device (enp2s0): state change: unavailable -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.7246]
manager: NetworkManager state is now ASLEEP
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.7263]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.8819]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 20:27:01 pc-fred NetworkManager[738]: <info> [1690655221.9475]
device (wlp1s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
juil. 29 20:27:02 pc-fred systemd[1]: Reached target Sleep.
juil. 29 20:27:02 pc-fred systemd[1]: Starting System Suspend...
juil. 29 20:27:02 pc-fred systemd-sleep[16661]: Entering sleep state
'suspend'...
juil. 29 20:27:02 pc-fred kernel: PM: suspend entry (deep)
juil. 29 21:09:32 pc-fred kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
juil. 29 21:09:32 pc-fred kernel: ACPI: PM: Preparing to enter system
sleep state S3
juil. 29 21:09:32 pc-fred kernel: ACPI: PM: Low-level resume complete
juil. 29 21:09:32 pc-fred kernel: ACPI: PM: Waking up from system sleep
state S3
juil. 29 21:09:32 pc-fred kernel: PM: suspend exit
juil. 29 21:09:32 pc-fred systemd-sleep[16661]: System returned from
sleep state.
juil. 29 21:09:32 pc-fred systemd[1]: systemd-suspend.service:
Deactivated successfully.
juil. 29 21:09:32 pc-fred systemd[1]: Finished System Suspend.
juil. 29 21:09:32 pc-fred systemd[1]: Stopped target Sleep.
juil. 29 21:09:32 pc-fred systemd[1]: Reached target Suspend.
juil. 29 21:09:32 pc-fred systemd[1]: Stopped target Suspend.
juil. 29 21:09:32 pc-fred systemd-logind[779]: Operation 'sleep' finished.
juil. 29 21:09:32 pc-fred NetworkManager[738]: <info> [1690657772.9717]
manager: sleep: wake requested (s

Algumas fotos do BIOS: https://imgur.com/a/OzONUyu

suspend
Martin Hope
mathtick
Asked: 2023-05-27 21:16:52 +0800 CST
  • 5

Não posso mudar.

Parece bloqueado.

Deseja colocar em um estado de energia inferior.

s2idle [profundo]

Como isso é feito. A pesquisa do Google atinge a discussão nem todos os caminhos possíveis para alterar corretamente.

ATUALIZAÇÃO :

O que as pessoas dizem geralmente está errado:

Por exemplo, isto é o que acontece:

$ echo s2idle | sudo tee /sys/power/mem_sleep
s2idle
$ cat /sys/power/mem_sleep
[s2idle]

Meu sistema está quebrado em comparação com o exemplo abaixo que resulta em deep!???? Ou é um erro de digitação da parte deles? Há confusão como essa em toda a web.

Por que isso falha?

echo deep | sudo tee /sys/power/mem_sleep
deep
tee: /sys/power/mem_sleep: Invalid argument

Minha suspeita é que as pessoas estão escrevendo respostas que acionam alguma coisa latente ... mas não entendem o que é essa coisa ou como alterar suas configurações. É grub?

E isso parece relevante https://forums.linuxmint.com/viewtopic.php?t=335139

ATUALIZAÇÃO :

O problema parece ter sido uma configuração do BIOS. Defina o estado de suspensão de energia de configuração para Linux!

suspend
Martin Hope
Rasmus Hjorth Lüdeking
Asked: 2023-02-25 00:05:38 +0800 CST
  • 5

Então... o ubuntu suspend não está funcionando no meu lenovo z13. Originalmente, eu estava inicializando o Windows e o Ubuntu e suspendendo o funcionamento perfeitamente bem no Windows, mas não no Ubuntu. Em seguida, tentei limpar todo o disco no sistema efi e nos gerenciadores de inicialização e instalei um novo ubuntu em uma lousa absolutamente limpa. O problema persiste no novo 22.04.1.

Nota lateral engraçada; systemctl suspend funciona bem ao inicializar no ubuntu usb se "tentar o ubuntu".

O problema exato gira em torno da função de suspensão que parece. Quando o systemctl suspend é executado pela primeira vez após a inicialização, ele funciona bem. Mas a qualquer momento depois disso, ele desliga a tela, enquanto o pc ainda está funcionando (ainda capaz de usar os botões Fn (luz de fundo, etc.)), consumindo energia e ventiladores em chamas. Além disso, não sou capaz de "acordar" desse estado por qualquer meio. A única coisa que resolve esse estado é forçar a reinicialização manual.

TL; DR é a função de suspensão funciona bem no ubuntu usb e em qualquer instalação do Windows, mas não no ubuntu local (pelo menos qualquer suspensão consecutiva após a primeira).

suspend
Martin Hope
Polymerase
Asked: 2023-02-13 17:13:04 +0800 CST
  • 5

Configurei uma máquina para convidados e para uso doméstico quando precisamos de uma navegação rápida na web. Esta máquina é usada com pouca frequência. Na maioria das vezes está em modo de suspensão (consumindo 2 watts).

Eu gostaria de executar o Pi-Hole nesta máquina. Mas isso exigiria que a máquina estivesse permanentemente ligada (Ryzen 5700G, gráficos integrados, medidor de watt mostra 30 W quando o computador está ocioso, não suspenso). Talvez eu só precise aplicar How to Disable Suspend and Hibernation Modes In Linux . Ou instale o servidor Ubuntu + ambiente de área de trabalho.

Qual é a recomendação para executar um desktop Linux como servidor? "Servidor" aqui significa "servidor interno", apenas exposto à rede doméstica.

suspend
Martin Hope
precise
Asked: 2023-01-25 03:42:27 +0800 CST
  • 5

Estou usando o Ubuntu 22.04 LTS (no Dell Inspiron 3505) com arquivo de troca de 16 GB que criei recentemente após excluir o arquivo de troca padrão de 2 GB de acordo com as instruções em Swap FAQ .

Q1. Meus aplicativos abertos ainda estão fechados quando inicio após uma hibernação. Isso é normal? E/ou, há uma correção?

Q2. Além disso, após a hibernação, pressionar apenas o botão liga / desliga não é suficiente para ativar o laptop, sou obrigado a pressionar o botão liga / desliga somente depois de conectar a fonte de alimentação. Este é um comportamento normal?

suspend