重要编辑: 今天,Supermicro 正式回复了我的询问。X11SPA既不支持挂起到内存,也不支持挂起到磁盘。在我看来,这是一个重大缺陷,因为该主板是他们面向工作站的应用程序的旗舰产品。请注意这一点。
这里是 Ubuntu 20.10,首次在新建的系统上安装。除了一件对我来说非常重要的事情外,一切都运行正常:暂停2ram。
如果我尝试通过 暂停(睡眠)systemctl suspend
,屏幕会变黑,但不会有任何反应,电源保持开启,风扇旋转。此时,如果我按下电源按钮,显示器会打开,一切如我之前所想。
现在看看这个。在我的系统上:
$ cat /sys/power/mem_sleep
[s2idle]
而在笔记本电脑上暂停作品, 这是:
$ cat /sys/power/mem_sleep
s2idle [deep]
我该如何调试这个问题?当然,有些设备会阻止挂起,但如何找到它呢?
以下是:
inxi
dump 向您显示系统配置。- 相关
syslog
转储。
编辑1:尝试休眠。系统恢复时屏幕损坏,然后挂起并需要硬重置。
EDIT2:安装了 windows10,不允许使用 s2ram。休眠挂起的方式大致相同。
System: Host: bliz Kernel: 5.8.0-26-lowlatency x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.19.5
tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine: Mobo: Supermicro model: X11SPA-TF v: 1.01 serial: <superuser/root required> UEFI: American Megatrends v: 3.3
date: 02/21/2020
Memory: RAM: total: 125.44 GiB used: 1.94 GiB (1.5%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: 24-Core model: Intel Xeon Platinum 8260M bits: 64 type: MT MCP arch: Cascade Lake rev: 5
L2 cache: 33.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 220800
Speed: 1000 MHz min/max: 1000/3900 MHz Core speeds (MHz): 1: 1204 2: 1001 3: 1000 4: 1167 5: 1001 6: 1000
7: 1088 8: 1200 9: 1504 10: 1000 11: 1200 12: 1049 13: 1146 14: 1000 15: 1100 16: 1000 17: 1098 18: 1036
19: 1000 20: 1141 21: 1113 22: 1341 23: 1041 24: 1143 25: 1000 26: 1089 27: 1000 28: 1043 29: 1001 30: 1141
31: 1087 32: 1001 33: 1086 34: 1200 35: 1101 36: 1307 37: 1001 38: 1177 39: 1070 40: 1000 41: 1017 42: 1001
43: 1089 44: 1056 45: 1000 46: 1086 47: 1001 48: 1099
Graphics: Device-1: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 04:00.0 chip ID: 1a03:2000
Device-2: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 19:00.0 chip ID: 10de:1f06
Device-3: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 1a:00.0 chip ID: 10de:1f06
Device-4: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: 65:00.0 chip ID: 10de:1f06
Device-5: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 455.28 bus ID: b4:00.0 chip ID: 10de:1f06
Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa
resolution: 1920x1080~60Hz s-dpi: 101
OpenGL: renderer: GeForce RTX 2060 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 455.28 direct render: Yes
Network: Device-1: Intel I210 Gigabit Network vendor: Super Micro driver: igb v: 5.6.0-k port: 2000 bus ID: 05:00.0
chip ID: 8086:1533
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 00:25:90:be:43:2d
Device-2: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion] vendor: Super Micro driver: atlantic v: kernel
port: 2000 bus ID: 06:00.0 chip ID: 1d6a:07b1
IF: eth0 state: down mac: 00:25:90:be:43:f5
Drives: Local Storage: total: 476.94 GiB used: 11.38 GiB (2.4%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 PRO 512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4
Partition: ID-1: / size: 287.37 GiB used: 11.37 GiB (4.0%) fs: ext4 dev: /dev/nvme0n1p2
Swap: ID-1: swap-1 type: partition size: 180.06 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 50.0 C mobo: N/A gpu: nvidia temp: 62 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 29%
Info: Processes: 752 Uptime: 2m Init: systemd v: 246 runlevel: 5 Compilers: gcc: 10.2.0 alt: 10 Packages: apt: 2979
Shell: Bash v: 5.0.17 running in: konsole inxi: 3.1.07
Nov 7 17:50:25 bliz systemd[1]: anacron.service: Succeeded.
Nov 7 17:51:48 bliz ModemManager[1471]: <info> [sleep-monitor] system is about to suspend
Nov 7 17:51:48 bliz NetworkManager[1289]: <info> [1604767908.1255] manager: sleep: sleep requested (sleeping: no enabled: yes)
Nov 7 17:51:48 bliz NetworkManager[1289]: <info> [1604767908.1256] manager: NetworkManager state is now ASLEEP
Nov 7 17:51:48 bliz whoopsie[2263]: [17:51:48] offline
Nov 7 17:51:48 bliz systemd[1]: Reached target Sleep.
Nov 7 17:51:48 bliz systemd[1]: Starting Suspend...
Nov 7 17:51:48 bliz kernel: [ 995.921939] PM: suspend entry (s2idle)
Nov 7 17:51:48 bliz systemd-sleep[3346]: Suspending system...
Nov 7 17:51:48 bliz kernel: [ 995.928295] Filesystems sync: 0.006 seconds
Nov 7 17:51:48 bliz acpid: client 1788[0:0] has disconnected
Nov 7 17:52:10 bliz kernel: [ 996.340713] Freezing user space processes ... (elapsed 0.002 seconds) done.
Nov 7 17:52:10 bliz kernel: [ 996.343045] OOM killer disabled.
Nov 7 17:52:10 bliz kernel: [ 996.343046] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 7 17:52:10 bliz kernel: [ 996.344199] printk: Suspending console(s) (use no_console_suspend to debug)
Nov 7 17:52:10 bliz kernel: [ 996.346322] serial 00:04: disabled
Nov 7 17:52:10 bliz kernel: [ 996.346577] serial 00:03: disabled
Nov 7 17:52:10 bliz kernel: [ 1016.883067] pci 0000:16:05.0: disabled boot interrupts on device [8086:2034]
Nov 7 17:52:10 bliz kernel: [ 1016.883157] pci 0000:64:05.0: disabled boot interrupts on device [8086:2034]
Nov 7 17:52:10 bliz kernel: [ 1016.883192] pci 0000:b2:05.0: disabled boot interrupts on device [8086:2034]
Nov 7 17:52:10 bliz kernel: [ 1016.883581] usb usb3: root hub lost power or was reset
Nov 7 17:52:10 bliz kernel: [ 1016.883584] usb usb4: root hub lost power or was reset
Nov 7 17:52:10 bliz kernel: [ 1016.883594] usb usb5: root hub lost power or was reset
Nov 7 17:52:10 bliz kernel: [ 1016.883597] usb usb6: root hub lost power or was reset
Nov 7 17:52:10 bliz kernel: [ 1016.883940] power_meter ACPI000D:00: Found ACPI power meter.
Nov 7 17:52:10 bliz kernel: [ 1016.885528] serial 00:03: activated
Nov 7 17:52:10 bliz kernel: [ 1016.886870] serial 00:04: activated
Nov 7 17:52:10 bliz kernel: [ 1016.943776] nvme nvme0: Shutdown timeout set to 8 seconds
Nov 7 17:52:10 bliz kernel: [ 1016.972019] nvme nvme0: 32/0/0 default/read/poll queues
Nov 7 17:52:10 bliz kernel: [ 1017.212955] ata3: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214100] ata2: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214135] ata8: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214177] ata6: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214222] ata5: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214266] ata7: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214312] ata1: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.214368] ata4: SATA link down (SStatus 0 SControl 300)
Nov 7 17:52:10 bliz kernel: [ 1017.392324] usb 1-1.2: reset low-speed USB device number 6 using xhci_hcd
Nov 7 17:52:10 bliz kernel: [ 1017.751867] usb 1-1.2: device descriptor read/64, error -32
Nov 7 17:52:10 bliz kernel: [ 1018.749136] fbcon: Taking over console
Nov 7 17:52:10 bliz kernel: [ 1018.749140] OOM killer enabled.
Nov 7 17:52:10 bliz kernel: [ 1018.749141] Restarting tasks ...
Nov 7 17:52:10 bliz kernel: [ 1018.751194] Console: switching to colour frame buffer device 128x48
Nov 7 17:52:10 bliz kernel: [ 1018.751614] done.
Nov 7 17:52:10 bliz kernel: [ 1018.754898] PM: suspend exit
Nov 7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov 7 17:52:10 bliz pipewire[2335]: #033[1;33m[W][000000998.421004][main-loop.c:157 pw_main_loop_run()] main-loop 0x55fa059cc0a0: iterate error -4 (Interrupted system call)#033[0m
Nov 7 17:52:10 bliz systemd-sleep[3346]: System resumed.
Nov 7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov 7 17:52:10 bliz pipewire[2341]: #033[1;33m[W][000000998.421027][main-loop.c:157 pw_main_loop_run()] main-loop 0x55eacc699e10: iterate error -4 (Interrupted system call)#033[0m
Nov 7 17:52:10 bliz acpid: client 1788[0:0] has disconnected
Nov 7 17:52:10 bliz systemd[1]: systemd-suspend.service: Succeeded.
Nov 7 17:52:10 bliz systemd[1]: Finished Suspend.
Nov 7 17:52:10 bliz systemd[1]: Stopped target Sleep.
Nov 7 17:52:10 bliz systemd[1]: Reached target Suspend.
Nov 7 17:52:10 bliz systemd[1]: Stopped target Suspend.
Nov 7 17:52:10 bliz ModemManager[1471]: <info> [sleep-monitor] system is resuming
Nov 7 17:52:10 bliz NetworkManager[1289]: <info> [1604767930.9755] manager: sleep: wake requested (sleeping: yes enabled: yes)
Nov 7 17:52:10 bliz NetworkManager[1289]: <info> [1604767930.9757] device (eno1): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 7 17:52:10 bliz NetworkManager[1289]: <info> [1604767930.9928] dhcp4 (eno1): canceled DHCP transaction
Nov 7 17:52:10 bliz NetworkManager[1289]: <info> [1604767930.9929] dhcp4 (eno1): state changed bound -> done
Nov 7 17:52:10 bliz avahi-daemon[1283]: Withdrawing address record for 192.168.1.7 on eno1.
Nov 7 17:52:10 bliz avahi-daemon[1283]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.1.7.
Nov 7 17:52:10 bliz avahi-daemon[1283]: Interface eno1.IPv4 no longer relevant for mDNS.
Nov 7 17:52:10 bliz avahi-daemon[1283]: Withdrawing address record for fe80::b8ff:d7cb:f7bb:ca99 on eno1.
Nov 7 17:52:10 bliz avahi-daemon[1283]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::b8ff:d7cb:f7bb:ca99.
Nov 7 17:52:10 bliz avahi-daemon[1283]: Interface eno1.IPv6 no longer relevant for mDNS.
Nov 7 17:52:11 bliz NetworkManager[1289]: <info> [1604767931.0036] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 7 17:52:11 bliz NetworkManager[1289]: <info> [1604767931.0329] manager: NetworkManager state is now DISCONNECTED
Nov 7 17:52:11 bliz NetworkManager[1289]: <info> [1604767931.0341] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 7 17:52:11 bliz NetworkManager[1289]: <info> [1604767931.0369] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Nov 7 17:52:11 bliz dbus-daemon[1287]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1289 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Nov 7 17:52:11 bliz systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 7 17:52:11 bliz dbus-daemon[1287]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 7 17:52:11 bliz systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 7 17:52:11 bliz nm-dispatcher[3625]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Nov 7 17:52:11 bliz NetworkManager[1289]: <info> [1604767931.0651] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Nov 7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov 7 17:52:11 bliz acpid: 1 client rule loaded
Nov 7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov 7 17:52:11 bliz acpid: 1 client rule loaded
Nov 7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov 7 17:52:11 bliz acpid: 1 client rule loaded
Nov 7 17:52:11 bliz acpid: client connected from 1788[0:0]
Nov 7 17:52:11 bliz acpid: 1 client rule loaded
Nov 7 17:52:13 bliz ModemManager[1471]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.6/0000:05:00.0': not supported by any plugin
Nov 7 17:52:14 bliz kernel: [ 1021.957276] igb 0000:05:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Nov 7 17:52:14 bliz kernel: [ 1022.063973] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2455] device (eno1): carrier: link connected
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2459] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2475] policy: auto-activating connection 'Wired connection 1' (da1d0e20-bea3-38af-9caf-d380db64c81e)
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2485] device (eno1): Activation: starting connection 'Wired connection 1' (da1d0e20-bea3-38af-9caf-d380db64c81e)
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2487] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2494] manager: NetworkManager state is now CONNECTING
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2499] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2509] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2513] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Nov 7 17:52:14 bliz avahi-daemon[1283]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::b8ff:d7cb:f7bb:ca99.
Nov 7 17:52:14 bliz avahi-daemon[1283]: New relevant interface eno1.IPv6 for mDNS.
Nov 7 17:52:14 bliz avahi-daemon[1283]: Registering new address record for fe80::b8ff:d7cb:f7bb:ca99 on eno1.*.
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2811] dhcp4 (eno1): option dhcp_lease_time => '21600'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2811] dhcp4 (eno1): option domain_name => 'homenet.telecomitalia.it'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2811] dhcp4 (eno1): option domain_name_servers => '192.168.1.1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2811] dhcp4 (eno1): option expiry => '1604789534'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option ip_address => '192.168.1.7'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_broadcast_address => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_domain_name => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_domain_name_servers => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_domain_search => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_host_name => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_interface_mtu => '1'
Nov 7 17:52:14 bliz avahi-daemon[1283]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.1.7.
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2812] dhcp4 (eno1): option requested_ms_classless_static_routes => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_nis_domain => '1'
Nov 7 17:52:14 bliz avahi-daemon[1283]: New relevant interface eno1.IPv4 for mDNS.
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_nis_servers => '1'
Nov 7 17:52:14 bliz avahi-daemon[1283]: Registering new address record for 192.168.1.7 on eno1.IPv4.
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_ntp_servers => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_rfc3442_classless_static_routes => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_root_path => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_routers => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_static_routes => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2813] dhcp4 (eno1): option requested_subnet_mask => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2814] dhcp4 (eno1): option requested_time_offset => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2814] dhcp4 (eno1): option requested_wpad => '1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2814] dhcp4 (eno1): option routers => '192.168.1.1'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2814] dhcp4 (eno1): option subnet_mask => '255.255.255.0'
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2814] dhcp4 (eno1): state changed unknown -> bound
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2836] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2858] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2860] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2865] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2875] manager: NetworkManager state is now CONNECTED_SITE
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2876] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2953] device (eno1): Activation: successful, device activated.
Nov 7 17:52:14 bliz NetworkManager[1289]: <info> [1604767934.2965] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 7 17:52:16 bliz systemd-resolved[1264]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] Cannot reach: https://daisy.ubuntu.com
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/2
Nov 7 17:52:16 bliz whoopsie[2263]: [17:52:16] online
Nov 7 17:52:16 bliz dbus-daemon[2340]: [session uid=1000 pid=2340] Activating service name='org.kde.KSplash' requested by ':1.98' (uid=1000 pid=3707 comm="/usr/bin/kwin_x11 --crashes 1 " label="unconfined")
Nov 7 17:52:24 bliz systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Nov 7 17:52:29 bliz systemd-resolved[1264]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
答案1
Supermicro 正式回复了我的询问。X11SPA 支持两者都不 暂停至内存(ACPI S3)也不 暂停至磁盘(ACPI S4)。我认为这是一个重大缺陷,因为该主板是他们面向工作站应用的旗舰产品。请注意这一点。
答案2
您能将输出关闭吗:
sudo s2ram -n
查看您的配置是否被识别。如果无法识别,请编辑:
/etc/powersave/sleep
并尝试:
SUSPEND2RAM_FORCE=yes
从此页面开始:http://powersave.sourceforge.net/powersave/Suspend2Ram.html 您还可以尝试:
只需将它们添加到 /boot/grub/menu.lst 中的“内核”行即可。有关它们的更多信息,请参阅 /usr/src/linux/Documentation/power/video.txt。
您可以尝试以下操作:
* acpi_sleep=s3_bios calls the video BIOS during resume to initialize the video card. * acpi_sleep=s3_mode calls the video BIOS during resume to reset the text mode. * acpi_sleep=s3_bios,s3_mode combines the above.
此外,如果它“就是不起作用”,尝试使用内核参数“vga=normal”可能是一个好主意,这将在启动期间为您提供一个简单的文本控制台(抱歉,这个没有精美的图形)。您需要删除现有的“vga=0x317”
另一种可能性是您正在休眠而不是暂停,并且出现了问题。
我看到您有 128 GB 的 RAM 和 180 GB 的交换空间。这很多,所以我猜您在尝试挂起/休眠时会使用它。对于休眠,您至少需要使用相同数量的内存,交换空间上是空闲的。这应该不是问题,除非您尝试休眠时使用的 RAM + 交换空间大于空闲交换空间。例如,如果您使用的是 120GB 的 RAM 加上来自 NVMe 的 70 GB 的交换空间,那就是 190GB,而您的交换空间是 180 GB,因此在这种情况下崩溃是必然的。
请检查如下日志:
cat /var/log/syslog | grep -i "kill\|time\|hang\|panic"
dmesg -T | grep -i "kill\|time\|hang\|panic"
在某些情况下,系统很忙(例如 IO 或交换),系统无法暂停。您是否使用 iSCSI 卷作为客户机?
更新:您可以通过以 root 身份运行如下脚本来暂停以启用跟踪:
#!/bin/sh
sync
echo 1 > /sys/power/pm_trace
echo mem > /sys/power/state
这些解释和更多内容来自这里: https://www.kernel.org/doc/html/latest/power/s2ram.html
您可以使用以下方式检查 dmesg:
dmesg -T | less
答案3
试试这个,sleep 1 && xset dpms force standby
也许对 S2RAM 有用。
找到了这里。
答案4
权限如果您的挂起失败,并且 # tail /var/log/acpid 显示“权限被拒绝”错误,请确保您的新 ACPI 事件和操作脚本具有适当的权限。
写入错误 如果 # echo mem > /sys/power/state 显示“写入错误:操作不允许”,请验证内核中是否启用了 CONFIG_HOTPLUG_CPU 选项。Suspend2 会自动选择此选项。
损坏的 sysfs 接口 使用 # echo standby > /sys/power/state 或 # echo mem > /sys/power/state 时可能会遇到问题(机器进入睡眠状态并立即唤醒)。可以使用 # echo -n 3 >/proc/acpi/sleep 使其进入睡眠状态来避免这种情况。如果热插拔守护程序仍在运行或 usb hcd 模块仍在加载,也可能会发生这种情况。
挂起后立即恢复 如果挂起几秒后才开始恢复,原因可能是 USB 模块。挂起前请卸载模块 uhci_hcd 和 ehci_hcd。hibernate-scripts 用户将“UnloadModules uhci_hcd ehci_hcd”添加到 /etc/hibernate/common.conf。
挂起“切换到 UP 代码”您可能正在使用频率缩放调节器(例如“保守”或“按需”),这些调节器有时会出现挂起问题。在挂起之前切换到调节器(例如“powersave”或“性能”)可能会解决此问题。
MySQL 守护进程正在运行 如果您正在运行 MySQL,睡眠可能也不起作用,因此请先停止 MySQL,然后睡眠。请记住在唤醒时重新启动 MySQL。
LCD 背光在睡眠期间保持打开状态 如果您的系统配备了 Radeon Mobility 图形控制器,您的 LCD 背光可能不会自动关闭。使用 radeontool 在睡眠操作脚本中暂停之前关闭背光。
睡眠期间功耗高此外,您可能还需要注意 ACPI 睡眠期间功耗高的问题。
必须卸载 SD 卡 在当前 (10.x) 和更早版本的 Ubuntu 中,如果安装了 SD 卡,系统将无法挂起(黑屏,闪烁“月亮”)。使用 Aspire One 社区页面上的脚本可以安全地解决此问题。在其他系统上,您可能只需将“sdhci mmc_block mmc_core”添加到 acpi-support 中的 MODULES= 行即可。或者尝试此方法(pm-utils & pci-sd):将以下行添加到 # /etc/pm/config.d/00sleep_module 以在待机前卸载模块:
SUSPEND_MODULES="$SUSPEND_MODULES sdhci"