问题[suspend](ubuntu)

单击“暂停”：屏幕变黑，风扇停止，功耗短暂降至 0，然后稳定在 3 瓦左右。

按下键盘上的任意键：NumLock 灯亮起，风扇旋转，硬盘发出轻微咔嗒声。显示屏亮起，显示单击“暂停”时的屏幕。功耗高达 80 瓦（对于空闲系统来说大约合适）。

看起来不错……除了一切都冻结了：键盘或鼠标没有响应。系统尚未连接到网络，因此无法通过 SSH 进入。屏幕上只有冻结的图像。重置以重新启动……

/var/log/syslog 显示暂停条目：“内核：PM：暂停条目（深度）”日志中的下一个条目来自重置后的启动；没有“恢复”条目

这是 Ubuntu 问题、BIOS 问题，还是某些硬件不兼容？

没有“恢复”日志，因为系统没有启动。它在访问内存时出现问题，所以就停止了。

我安装了 6000MT/s DDR5 内存，但运行在“EXPO-2”配置文件中：5600MT/s。运行正常……除了挂起。将速度降至 5200MT/s，现在挂起可以正常工作。那么为什么 DRAM 频率会影响挂起？

好吧，它在 5200 下工作了几次，所以我认为问题已经解决了。切换到 Plasma 并尝试了它：像以前一样失败了，但现在显示空白。切换回 Gnome，它也失败了，恢复时显示空白。它工作了一段时间......

我是否需要尝试 4800？

在极少数情况下，它会起作用，暂停会将其写入系统日志：

2025-01-17T08:55:03.491302-08:00 ndesktop systemd[1]: Starting systemd-suspend.service - System Suspend...
2025-01-17T08:55:03.519102-08:00 ndesktop systemd-sleep[12872]: Successfully froze unit 'user.slice'.
2025-01-17T08:55:03.522856-08:00 ndesktop systemd-sleep[12872]: Performing sleep operation 'suspend'...
2025-01-17T08:55:03.523775-08:00 ndesktop kernel: PM: suspend entry (deep)
2025-01-17T08:55:03.525771-08:00 ndesktop kernel: Filesystems sync: 0.002 seconds
2025-01-17T08:55:13.925513-08:00 ndesktop kernel: Freezing user space processes
2025-01-17T08:55:13.925581-08:00 ndesktop kernel: Freezing user space processes completed (elapsed 0.001 seconds)

大多数情况下，暂停会像这样失败：

2025-01-17T08:56:27.288521-08:00 ndesktop systemd[1]: Starting systemd-suspend.service - System Suspend...
2025-01-17T08:56:27.311520-08:00 ndesktop systemd-sleep[14191]: Successfully froze unit 'user.slice'.
2025-01-17T08:56:27.315182-08:00 ndesktop systemd-sleep[14191]: Performing sleep operation 'suspend'...
2025-01-17T08:56:27.316049-08:00 ndesktop kernel: PM: suspend entry (deep)
2025-01-17T08:59:10.601312-08:00 ndesktop systemd-modules-load[444]: Inserted module 'lp'
2025-01-17T08:59:10.601362-08:00 ndesktop systemd-modules-load[444]: Inserted module 'ppdev'
2025-01-17T08:59:10.601368-08:00 ndesktop systemd-modules-load[444]: Inserted module 'parport_pc'

恢复失败并按下重置按钮后写入的模块加载条目。所以它在“文件系统同步”时失败了？

问题

每当我尝试将 PC 从睡眠/挂起模式唤醒时，系统最初似乎会做出响应，但随后屏幕会冻结并且对我所做的任何操作均不响应。此时，唯一的解决方法似乎是按住电源按钮 5 秒钟强制关闭机器，然后重新启动。

不管睡眠是手动触发的还是在长时间不活动后自动触发的，也不管唤醒尝试是通过移动鼠标、敲击键盘还是按下电源按钮进行的​​，都会发生这种情况。有时它会再次显示登录屏幕，但有时（我想如果我已经登录了），它会显示一个除了鼠标光标外完全是黑色的屏幕。无论如何，移动鼠标或在键盘上打字都不会产生任何可见的响应。

系统

我正在运行 Ubuntu Studio 24.10，但如果我没记错的话，当我还使用 24.04.x 时也出现了这个问题。

我的硬件如下：

主板： ASUS Z790 GAMING WIFI7
CPU： Intel Core i9-14900K (x86_64)
GPU： AMD Radeon RX 7900XT
存储： 8 TB SSD
内存： 96 GB NVMe DDR5

我已经尝试过的解决方案（无济于事）

• Ctrl冻结时，使用+ Alt+ F2–切换到不同的 TTY F6：它根本什么也不做。
  • （顺便说一句，当我没有被冻结时，特别是Ctrl++ ，它Alt不会带我进入一个新的 shell 会话，而是显示一个全黑的屏幕，上面只有一个鼠标光标，F2这与我在唤醒冻结期间有时看到的非常相似，只是我实际上可以移动鼠标，也可以使用Ctrl++返回到主图形会话。）AltF1
• 在 GRUB 配置中限制 CPU 的最大 C 状态：我尝试在/etc/default/grub.d/中创建一个新文件并添加行GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT intel_idle.max_cstate=1"，然后运行sudo update-grub并重新启动。我还尝试将变量名称更改为processor.max_cstate并将值4更改为 。上述步骤的排列似乎最终都没有任何区别。
• 增加交换空间：/swap.img的大小本来是 8 GB，但我根据我读到的建议将其增加到 10 GB，其中指出交换文件应该是系统总 RAM 的平方根。回想起来，我不确定我最初是否期望这会带来什么不同。
• 禁用 systemd 会话冻结：根据网上的其他建议，我尝试添加以下环境变量来配置 systemd 256+：
  • 创建/etc/systemd/system/systemd-suspend.service.d/freeze_fix.conf：

    [Service]
    Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
    

  • 创建/etc/systemd/system/systemd- sleep .service.d/作为指向/etc/systemd/system/systemd- suspend .service.d的符号链接。
  • 创建/etc/systemd/system/systemd-homed.service.d/freeze_fix.conf：

    [Service]
    Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=false"
    

（过去我看到在网上发布类似问题的人经常被告知检查/var/log/syslog中的系统日志和/或（或更具体地说， ）的输出。这篇文章的初始版本有来自暂停过程的那些日志的结果粘贴在下面，但我后来删除了它们，因为它们只包含来自暂停过程本身的消息，而不是来自再次唤醒过程的消息，而唤醒过程才是实际问题发生的时候。）journalctljournalctl -b -1

我买了一台第五代英特尔处理器，几天前一切都运行正常，但现在合上盖子时它不会暂停。我使用的是 Ubuntu 24.04，内核 6.8.0-50-generic，但我无法追踪哪个更新破坏了它。还有其他人遇到过这种情况吗？

我的系统时不时无法正常挂起。关闭盖子、选择从图形界面挂起或运行命令都会关闭屏幕，但系统会在几秒钟后重新启动。运行故障排除显示某些设备阻止系统挂起。如何才能让我的系统挂起？

突然，使系统进入睡眠状态开始失败，这里是整个/var/log/syslog https://gist.github.com/umpirsky/f3e1a8d32217ad4b8fb3186124866d69

我禁用了中的所有条目/proc/acpi/wakeup，但没有帮助。

Ubuntu 22.04.4 LTS

知道为什么会发生这种情况吗？谢谢。

我的新电脑配备 AMD Ryzen 5 7600 CPU 并运行 Ubuntu 24.04，在我挂起后立即自动唤醒。运行systemctl suspend后系统似乎进入挂起状态（显示屏变黑，外部设备电源关闭），随后很快被唤醒。整个过程需要几秒钟，但外部设备电源（通过有线鼠标上的指示灯可见）仅关闭不到 1 秒。

我发现很多人问过同样的问题，而我发现的唯一关于如何确定是什么唤醒了计算机的建议是 (a) 检查日志以找出是什么唤醒了计算机，例如通过sudo journalctl --since="-5 minutes"或sudo dmesg -T | tail -n 200或cat /var/log/syslog。这些似乎都提供了相同的信息，对我来说，其中包括计算机进入挂起模式并禁用 CPU，然后立即恢复的行。我没有看到任何迹象表明它为什么被唤醒。

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) 通过 echo XHC0 > /proc/acpi/wakeup 禁用各种设备唤醒计算机的功能 我已经这样做了，并禁用了 /proc/acpi/wakeup 中列出的每个设备。cat /proc/acpi/wakeup | grep ena没有输出任何内容。但我的电脑仍然立即被唤醒。

(c) systemd-inhibit：使用 查找可能阻止挂起的内容systemd-inhibit --list --mode=block。运行此命令时，我从 GNOME 获得一个结果。我能够通过将其包含InhibitorsMax=0在 /etc/systemd/logind.conf 中来禁用它。重新启动后，list 命令未显示任何结果。我的计算机继续立即唤醒，尽管现在需要稍长的时间，并且直到我移动鼠标或按下键盘上的某个键时，显示屏才会亮起。重复 (b) 中的解决方案，禁用 /proc/acpi/wakeup 中的所有设备，同样无效。

(d) 更改 BIOS 设置：我在 BIOS 设置中只看到键盘和鼠标唤醒选项。鼠标已关闭。我不想关闭键盘，但我确实测试过，断开键盘连接后计算机仍会自动唤醒。

我还尝试了休眠模式，它似乎只是关闭了计算机。重新打开它后，启动正常。编辑：我现在可以让休眠模式正常工作，这很好，但不能解决暂停的问题。

LAN 唤醒已禁用。sudo ethtool enp4s0显示Wake-on: d。（显示的其他两个以太网接口ip a都没有唤醒条目。）我还拔掉了鼠标以防万一，并再次拔掉了键盘以防万一。这些都没有任何效果。

我还可以做什么来排除故障或解决这个问题？

我只想让我的笔记本电脑在合上盖子的情况下继续正常运行。我已经看过几个类似的问题并已经尝试过以下方法。任何帮助将不胜感激。

我尝试过的方法：

• Gnome 调整 - 禁用盖子关闭时的自动暂停
• 编辑/etc/systemd/logind.conf

  HandleLidSwitch=ignore
  HandleListSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore
  LidSwitchIgnoreInhibited=no
  

我在用：

• 发行商 ID：Ubuntu
• 说明：Ubuntu 22.04.4 LTS
• 发布时间：22.04
• 代号： 杰米

笔记本电脑详细信息：

• 华硕 ROG GL552VW-DH71
• GPU GeForce GTX 960M 2GB 显存
• 16GB DDR4
• 英特尔 i7 CPU

从 23.04 升级到 23.10 后，我的笔记本电脑无法休眠：尝试休眠时，它立即再次唤醒。当没有连接任何外围设备（蓝牙、键盘、显示器等）时，就会发生这种情况。

我尝试过切换“唤醒设备”，/proc/acpi/wakeup就像Ubuntu 在睡眠几秒钟后醒来一样，但禁用它们并不能阻止计算机立即唤醒。

非常感谢任何帮助！

我在 Ubuntu 22.04 上的华硕 VivoBook 17 上遇到问题（全新安装）
一切似乎都工作正常，除了挂起模式：之后，计算机不想执行任何操作：黑屏（如挂起），然后鼠标单击 /触控板/键盘不起作用，我必须按电源按钮 5 秒才能强制计算机进入待机状态。重新启动后，它工作正常（直到暂停......）

在启动时，我看到了这个（简短地）：

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)

所以我将BIOS从版本302（或其他）更新到310（序列号：X705QA）
但它没有改变任何东西。

正如这个问题所示：Ubuntu 22.04 不会从睡眠中唤醒，这可能是由于驱动程序造成的。但没有找到额外的驱动程序（只有一个用于wifi卡的驱动程序，但wifi工作正常，所以我没有更改它）

我不知道该怎么做；这里有人有主意吗？

一些信息：

$ 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

电脑 ：

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)

还有一些我让计算机暂停的会话日志

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

提前致谢

编辑 ：

$ 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

BIOS 的一些图片： https: //imgur.com/a/OzONUyu

我无法改变。

好像锁了

想要进入低功耗状态。

s2idle [深]

这是怎么做到的。谷歌搜索点击讨论并非所有可能的正确更改路径。

更新：

人们说的通常是错误的：

例如，这是发生的事情：

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

与下面导致深度的示例相比，我的系统是否已损坏！？？？？或者这是他们的错字？网络上到处都是这样的混乱。

为什么会失败？

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

我怀疑人们写的答案会触发一些潜在的东西……但他们不明白那东西是什么或如何更改它的设置。是蛆吗？

这似乎是相关的https://forums.linuxmint.com/viewtopic.php?t=335139

更新：

问题似乎出在 BIOS 设置上。将 config power sleep state 设置为 Linux！