笔记本最近没法进入睡眠模式了

chen05_20 · 2021-11-13 22:59:08

型号：thinkpad x1 nano
内核：5.15.2
好像就是用了显示器之后，笔记本时间到了只能进入待机模式（指示灯常亮，很多设备还在运转，后盖摸着一直很热），不能进入呼吸灯闪烁的睡眠模式

依云 · 2021-11-14 12:47:49

你是怎么操作的呢？当时的系统日志看一看？

chen05_20 · 2021-11-14 14:46:12

依云说：

你是怎么操作的呢？当时的系统日志看一看？

就是直接盖上盖子，我在gnome tweak 里面设置成了盖上盖子休眠，可能截多了，但睡眠相关的应该在里面了。

11月 14 14:39:22 cm-pc kernel: audit: type=1101 audit(1636871962.388:205): pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc kernel: audit: type=1110 audit(1636871962.388:206): pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc kernel: audit: type=1105 audit(1636871962.388:207): pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc sudo[4148]: pam_unix(sudo:session): session closed for user root
11月 14 14:39:22 cm-pc audit[4148]: USER_END pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc audit[4148]: CRED_DISP pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc kernel: audit: type=1106 audit(1636871962.415:208): pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:22 cm-pc kernel: audit: type=1104 audit(1636871962.415:209): pid=4148 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:39:48 cm-pc systemd[803]: app-gnome-org.gnome.tweaks-3469.scope: Consumed 1.588s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit UNIT completed and consumed the indicated resources.
11月 14 14:39:58 cm-pc systemd-logind[353]: Lid closed.
11月 14 14:39:58 cm-pc systemd-logind[353]: Suspending...
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.2439] manager: sleep: sleep requested (sleeping: no  enabled: yes)
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.2440] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.2444] manager: NetworkManager state is now ASLEEP
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.2445] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:39:58 cm-pc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1' (uid=0 pid=352 comm="/usr/bin/NetworkManager --no-daemon ")
11月 14 14:39:58 cm-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: NetworkManager-dispatcher.service 单元已开始启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ NetworkManager-dispatcher.service 单元已开始启动。
11月 14 14:39:58 cm-pc dbus-daemon[351]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
11月 14 14:39:58 cm-pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: NetworkManager-dispatcher.service 单元已结束启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ NetworkManager-dispatcher.service 单元已结束启动。
░░ 
░░ 启动结果为“done”。
11月 14 14:39:58 cm-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:39:58 cm-pc kernel: audit: type=1130 audit(1636871998.245:210): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:39:58 cm-pc kernel: wlp0s20f3: deauthenticating from fc:34:97:d7:21:28 by local choice (Reason: 3=DEAUTH_LEAVING)
11月 14 14:39:58 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:d7:21:28 reason=3 locally_generated=1
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.4031] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:39:58 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
11月 14 14:39:58 cm-pc google-chrome.desktop[1676]: [1669:1699:1114/143958.406019:ERROR:registration_request.cc(247)] Registration URL fetching failed.
11月 14 14:39:58 cm-pc google-chrome.desktop[1676]: [1669:1699:1114/143958.406243:ERROR:registration_request.cc(247)] Registration URL fetching failed.
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.4252] dhcp4 (wlp0s20f3): canceled DHCP transaction
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.4253] dhcp4 (wlp0s20f3): state changed bound -> terminated
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.4420] device (wlp0s20f3): set-hw-addr: set MAC address to 8E:8A:22:92:83:03 (scanning)
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.6456] device (wlp0s20f3): supplicant interface state: completed -> disconnected
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.6480] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.6480] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:39:58 cm-pc NetworkManager[352]: <info>  [1636871998.6641] device (wlp0s20f3): set-hw-addr: reset MAC address to 00:42:38:F7:AC:2E (unmanage)
11月 14 14:39:58 cm-pc gnome-shell[877]: An active wireless connection, in infrastructure mode, involves no access point?
11月 14 14:39:58 cm-pc gnome-shell[877]: st_widget_get_theme_node called on the widget [0x5610570de5c0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_extension_WindowList.bottom-panel solid "panel"] which is not in the stage.
11月 14 14:39:58 cm-pc gnome-shell[877]: Spurious clutter_actor_allocate called for actor 0x5610570de5c0/<panel>[<Gjs_window-list_gnome-shell-extensions_gcampax_github_com_extension_WindowList>:0x5610570de5c0] which isn't a descendent of the stage!
11月 14 14:39:58 cm-pc gnome-shell[877]: Spurious clutter_actor_allocate called for actor 0x5610570de5c0/<panel>[<Gjs_window-list_gnome-shell-extensions_gcampax_github_com_extension_WindowList>:0x5610570de5c0] which isn't a descendent of the stage!
11月 14 14:39:58 cm-pc gnome-shell[877]: Spurious clutter_actor_allocate called for actor 0x5610570de5c0/<panel>[<Gjs_window-list_gnome-shell-extensions_gcampax_github_com_extension_WindowList>:0x5610570de5c0] which isn't a descendent of the stage!
11月 14 14:39:58 cm-pc gnome-shell[877]: Spurious clutter_actor_allocate called for actor 0x5610570de5c0/<panel>[<Gjs_window-list_gnome-shell-extensions_gcampax_github_com_extension_WindowList>:0x5610570de5c0] which isn't a descendent of the stage!
11月 14 14:39:58 cm-pc wpa_supplicant[497]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
11月 14 14:39:59 cm-pc systemd[1]: Reached target Sleep.
░░ Subject: sleep.target 单元已结束启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ sleep.target 单元已结束启动。
░░ 
░░ 启动结果为“done”。
11月 14 14:39:59 cm-pc systemd[1]: Starting System Suspend...
░░ Subject: systemd-suspend.service 单元已开始启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ systemd-suspend.service 单元已开始启动。
11月 14 14:39:59 cm-pc systemd-sleep[4227]: Entering sleep state 'suspend'...
░░ Subject: 系统已进入 suspend 睡眠状态
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ 系统现已进入 suspend 睡眠状态。
11月 14 14:39:59 cm-pc kernel: PM: suspend entry (s2idle)
11月 14 14:39:59 cm-pc kernel: Filesystems sync: 0.013 seconds
11月 14 14:40:21 cm-pc kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
11月 14 14:40:21 cm-pc kernel: OOM killer disabled.
11月 14 14:40:21 cm-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
11月 14 14:40:21 cm-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
11月 14 14:40:21 cm-pc kernel: mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
11月 14 14:40:21 cm-pc kernel: mhi-pci-generic 0000:08:00.0: failed to suspend device: -5
11月 14 14:40:21 cm-pc kernel: PM: pci_pm_suspend(): mhi_pci_suspend+0x0/0x20 [mhi_pci_generic] returns -16
11月 14 14:40:21 cm-pc kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
11月 14 14:40:21 cm-pc kernel: mhi-pci-generic 0000:08:00.0: PM: failed to suspend async: error -16
11月 14 14:40:21 cm-pc kernel: PM: Some devices failed to suspend, or early wake event detected
11月 14 14:40:21 cm-pc kernel: nvme nvme0: 8/0/0 default/read/poll queues
11月 14 14:40:21 cm-pc kernel: OOM killer enabled.
11月 14 14:40:21 cm-pc kernel: Restarting tasks ... 
11月 14 14:40:21 cm-pc kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
11月 14 14:40:21 cm-pc rtkit-daemon[559]: The canary thread is apparently starving. Taking action.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Demoting known real-time threads.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1174 of process 949.
11月 14 14:40:21 cm-pc ntpd[364]: Deleting interface #10 wlp0s20f3, 192.168.50.2#123, interface stats: received=15, sent=16, dropped=0, active_time=264 secs
11月 14 14:40:21 cm-pc ntpd[364]: 5.79.108.34 local addr 192.168.50.2 -> <null>
11月 14 14:40:21 cm-pc ntpd[364]: 162.159.200.1 local addr 192.168.50.2 -> <null>
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1173 of process 949.
11月 14 14:40:21 cm-pc ntpd[364]: 195.186.4.101 local addr 192.168.50.2 -> <null>
11月 14 14:40:21 cm-pc ntpd[364]: 202.118.1.130 local addr 192.168.50.2 -> <null>
11月 14 14:40:21 cm-pc ntpd[364]: Deleting interface #11 wlp0s20f3, fe80::16f1:2de8:46c2:c410%2#123, interface stats: received=0, sent=0, dropped=0, active_time=264 secs
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1171 of process 949.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1170 of process 949.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1156 of process 949.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 1115 of process 949.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Successfully demoted thread 949 of process 949.
11月 14 14:40:21 cm-pc rtkit-daemon[559]: Demoted 7 threads.
11月 14 14:40:21 cm-pc kernel: done.
11月 14 14:40:21 cm-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:40:21 cm-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
11月 14 14:40:21 cm-pc kernel: audit: type=1131 audit(1636872021.531:211): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:40:21 cm-pc kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
11月 14 14:40:21 cm-pc google-chrome.desktop[1676]: [1669:1699:1114/144021.553855:ERROR:connection_factory_impl.cc(429)] Failed to connect to MCS endpoint with error -106
11月 14 14:40:21 cm-pc bluetoothd[453]: Controller resume with wake event 0x0
11月 14 14:40:21 cm-pc kernel: PM: suspend exit
11月 14 14:40:21 cm-pc kernel: PM: suspend entry (s2idle)
11月 14 14:40:21 cm-pc kernel: Filesystems sync: 0.001 seconds
11月 14 14:40:41 cm-pc kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
11月 14 14:40:41 cm-pc kernel: OOM killer disabled.
11月 14 14:40:41 cm-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
11月 14 14:40:41 cm-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
11月 14 14:40:41 cm-pc kernel: Bluetooth: hci0: command 0x0c1a tx timeout
11月 14 14:40:41 cm-pc kernel: Bluetooth: hci0: command 0xfc1e tx timeout
11月 14 14:40:41 cm-pc kernel: mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
11月 14 14:40:41 cm-pc kernel: mhi-pci-generic 0000:08:00.0: failed to suspend device: -5
11月 14 14:40:41 cm-pc kernel: PM: pci_pm_suspend(): mhi_pci_suspend+0x0/0x20 [mhi_pci_generic] returns -16
11月 14 14:40:41 cm-pc kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
11月 14 14:40:41 cm-pc kernel: mhi-pci-generic 0000:08:00.0: PM: failed to suspend async: error -16
11月 14 14:40:41 cm-pc kernel: PM: Some devices failed to suspend, or early wake event detected
11月 14 14:40:41 cm-pc kernel: nvme nvme0: 8/0/0 default/read/poll queues
11月 14 14:40:41 cm-pc kernel: OOM killer enabled.
11月 14 14:40:41 cm-pc kernel: Restarting tasks ... 
11月 14 14:40:41 cm-pc kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
11月 14 14:40:41 cm-pc kernel: done.
11月 14 14:40:41 cm-pc kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
11月 14 14:40:41 cm-pc rtkit-daemon[559]: The canary thread is apparently starving. Taking action.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Demoting known real-time threads.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1174 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1173 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1171 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1170 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1156 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 1115 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Successfully demoted thread 949 of process 949.
11月 14 14:40:41 cm-pc rtkit-daemon[559]: Demoted 7 threads.
11月 14 14:40:42 cm-pc systemd-sleep[4227]: Failed to put system to sleep. System resumed again: Device or resource busy
░░ Subject: 系统已离开 suspend 睡眠状态
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ 系统现已离开 suspend 睡眠状态。
11月 14 14:40:42 cm-pc bluetoothd[453]: Controller resume with wake event 0x0
11月 14 14:40:42 cm-pc systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit systemd-suspend.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
11月 14 14:40:42 cm-pc systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
11月 14 14:40:42 cm-pc systemd[1]: Failed to start System Suspend.
░░ Subject: systemd-suspend.service 单元已失败
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ systemd-suspend.service 单元已失败。
░░ 
░░ 结果为“failed”。
11月 14 14:40:42 cm-pc systemd[1]: Dependency failed for Suspend.
░░ Subject: suspend.target 单元已失败
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ suspend.target 单元已失败。
░░ 
░░ 结果为“dependency”。
11月 14 14:40:42 cm-pc systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
11月 14 14:40:42 cm-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
11月 14 14:40:42 cm-pc systemd[1]: Stopped target Sleep.
░░ Subject: sleep.target 单元已结束停止操作
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ sleep.target 单元已结束停止操作。
11月 14 14:40:42 cm-pc systemd-logind[353]: Operation 'sleep' finished.
11月 14 14:40:42 cm-pc kernel: PM: suspend exit
11月 14 14:40:42 cm-pc kernel: audit: type=1130 audit(1636872042.038:212): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
11月 14 14:40:42 cm-pc NetworkManager[352]: <info>  [1636872042.0416] manager: sleep: wake requested (sleeping: yes  enabled: yes)
11月 14 14:40:42 cm-pc NetworkManager[352]: <info>  [1636872042.0417] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
11月 14 14:40:42 cm-pc systemd-logind[353]: Suspending...
11月 14 14:40:42 cm-pc systemd[1]: Reached target Sleep.
░░ Subject: sleep.target 单元已结束启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ sleep.target 单元已结束启动。
░░ 
░░ 启动结果为“done”。
11月 14 14:40:42 cm-pc systemd[1]: Starting System Suspend...
░░ Subject: systemd-suspend.service 单元已开始启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ systemd-suspend.service 单元已开始启动。
11月 14 14:40:42 cm-pc systemd-sleep[4275]: Entering sleep state 'suspend'...
░░ Subject: 系统已进入 suspend 睡眠状态
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ 系统现已进入 suspend 睡眠状态。
11月 14 14:40:42 cm-pc kernel: PM: suspend entry (s2idle)
11月 14 14:40:42 cm-pc kernel: Filesystems sync: 0.001 seconds
11月 14 14:41:22 cm-pc kernel: Freezing user space processes ... (elapsed 0.162 seconds) done.
11月 14 14:41:22 cm-pc kernel: OOM killer disabled.
11月 14 14:41:22 cm-pc kernel: Freezing remaining freezable tasks ... 
11月 14 14:41:22 cm-pc kernel: mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
11月 14 14:41:22 cm-pc kernel: mhi-pci-generic 0000:08:00.0: failed to suspend device: -5
11月 14 14:41:22 cm-pc kernel: (elapsed 19.944 seconds) done.
11月 14 14:41:22 cm-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
11月 14 14:41:22 cm-pc kernel: mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
11月 14 14:41:22 cm-pc kernel: mhi-pci-generic 0000:08:00.0: failed to suspend device: -5
11月 14 14:41:22 cm-pc kernel: PM: pci_pm_suspend(): mhi_pci_suspend+0x0/0x20 [mhi_pci_generic] returns -16
11月 14 14:41:22 cm-pc kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
11月 14 14:41:22 cm-pc kernel: mhi-pci-generic 0000:08:00.0: PM: failed to suspend async: error -16
11月 14 14:41:22 cm-pc kernel: PM: Some devices failed to suspend, or early wake event detected
11月 14 14:41:22 cm-pc kernel: nvme nvme0: 8/0/0 default/read/poll queues
11月 14 14:41:22 cm-pc kernel: OOM killer enabled.
11月 14 14:41:22 cm-pc kernel: Restarting tasks ... 
11月 14 14:41:22 cm-pc kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
11月 14 14:41:22 cm-pc kernel: done.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: The canary thread is apparently starving. Taking action.
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9483] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Demoting known real-time threads.
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9486] manager: NetworkManager state is now DISCONNECTED
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1174 of process 949.
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9487] manager: sleep: sleep requested (sleeping: no  enabled: yes)
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1173 of process 949.
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9487] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1171 of process 949.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1170 of process 949.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1156 of process 949.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 1115 of process 949.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Successfully demoted thread 949 of process 949.
11月 14 14:41:22 cm-pc rtkit-daemon[559]: Demoted 7 threads.
11月 14 14:41:22 cm-pc google-chrome.desktop[1676]: [1669:1699:1114/144122.958253:ERROR:connection_factory_impl.cc(429)] Failed to connect to MCS endpoint with error -106
11月 14 14:41:22 cm-pc kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9652] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
11月 14 14:41:22 cm-pc NetworkManager[352]: <info>  [1636872082.9654] manager: NetworkManager state is now ASLEEP
11月 14 14:41:23 cm-pc bluetoothd[453]: Controller resume with wake event 0x0
11月 14 14:41:23 cm-pc kernel: PM: suspend exit
11月 14 14:41:23 cm-pc kernel: PM: suspend entry (s2idle)
11月 14 14:41:23 cm-pc kernel: Filesystems sync: 0.001 seconds
11月 14 14:41:45 cm-pc kernel: Freezing user space processes ... (elapsed 0.240 seconds) done.
11月 14 14:41:45 cm-pc kernel: OOM killer disabled.
11月 14 14:41:45 cm-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
11月 14 14:41:45 cm-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
11月 14 14:41:45 cm-pc kernel: mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
11月 14 14:41:45 cm-pc kernel: mhi-pci-generic 0000:08:00.0: failed to suspend device: -5
11月 14 14:41:45 cm-pc kernel: PM: pci_pm_suspend(): mhi_pci_suspend+0x0/0x20 [mhi_pci_generic] returns -16
11月 14 14:41:45 cm-pc kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
11月 14 14:41:45 cm-pc kernel: mhi-pci-generic 0000:08:00.0: PM: failed to suspend async: error -16
11月 14 14:41:45 cm-pc kernel: PM: Some devices failed to suspend, or early wake event detected
11月 14 14:41:45 cm-pc kernel: nvme nvme0: 8/0/0 default/read/poll queues
11月 14 14:41:45 cm-pc kernel: OOM killer enabled.
11月 14 14:41:45 cm-pc kernel: Restarting tasks ... 
11月 14 14:41:45 cm-pc kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
11月 14 14:41:45 cm-pc kernel: done.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: The canary thread is apparently starving. Taking action.
11月 14 14:41:45 cm-pc systemd-logind[353]: Lid opened.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Demoting known real-time threads.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1174 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1173 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1171 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1170 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1156 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 1115 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Successfully demoted thread 949 of process 949.
11月 14 14:41:45 cm-pc rtkit-daemon[559]: Demoted 7 threads.
11月 14 14:41:45 cm-pc wpa_supplicant[497]: nl80211: kernel reports: Attribute failed policy validation
11月 14 14:41:45 cm-pc wpa_supplicant[497]: Failed to create interface p2p-dev-wlp0s20f3: -22 (Invalid argument)
11月 14 14:41:45 cm-pc wpa_supplicant[497]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp0s20f3
11月 14 14:41:45 cm-pc wpa_supplicant[497]: P2P: Failed to enable P2P Device interface
11月 14 14:41:45 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
11月 14 14:41:45 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
11月 14 14:41:45 cm-pc systemd-sleep[4275]: Failed to put system to sleep. System resumed again: Device or resource busy
░░ Subject: 系统已离开 suspend 睡眠状态
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ 系统现已离开 suspend 睡眠状态。
11月 14 14:41:45 cm-pc bluetoothd[453]: Controller resume with wake event 0x0
11月 14 14:41:45 cm-pc systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit systemd-suspend.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
11月 14 14:41:45 cm-pc systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
11月 14 14:41:45 cm-pc systemd[1]: Failed to start System Suspend.
░░ Subject: systemd-suspend.service 单元已失败
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ systemd-suspend.service 单元已失败。
░░ 
░░ 结果为“failed”。
11月 14 14:41:45 cm-pc systemd[1]: Dependency failed for Suspend.
░░ Subject: suspend.target 单元已失败
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ suspend.target 单元已失败。
░░ 
░░ 结果为“dependency”。
11月 14 14:41:45 cm-pc systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
11月 14 14:41:45 cm-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
11月 14 14:41:45 cm-pc systemd[1]: systemd-suspend.service: Consumed 1.836s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-suspend.service completed and consumed the indicated resources.
11月 14 14:41:45 cm-pc systemd[1]: Stopped target Sleep.
░░ Subject: sleep.target 单元已结束停止操作
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ sleep.target 单元已结束停止操作。
11月 14 14:41:45 cm-pc systemd-logind[353]: Operation 'sleep' finished.
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4479] manager: sleep: wake requested (sleeping: yes  enabled: yes)
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4480] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
11月 14 14:41:45 cm-pc kernel: PM: suspend exit
11月 14 14:41:45 cm-pc kernel: audit: type=1130 audit(1636872105.444:213): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4491] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4495] manager: NetworkManager state is now DISCONNECTED
11月 14 14:41:45 cm-pc wpa_supplicant[497]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4521] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4522] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4526] Wi-Fi P2P device controlled by interface wlp0s20f3 created
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4527] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7)
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4529] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4533] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
11月 14 14:41:45 cm-pc NetworkManager[352]: <info>  [1636872105.4538] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:45 cm-pc gnome-shell[877]: Removing a network device that was not added
11月 14 14:41:48 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CN
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9683] policy: auto-activating connection 'ASUS_CM_FAST' (63d085c6-1779-4c0c-840c-16c3d3802ae9)
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9685] device (wlp0s20f3): Activation: starting connection 'ASUS_CM_FAST' (63d085c6-1779-4c0c-840c-16c3d3802ae9)
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9686] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9687] manager: NetworkManager state is now CONNECTING
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9688] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9690] device (wlp0s20f3): Activation: (wifi) access point 'ASUS_CM_FAST' has security, but secrets are required.
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9690] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9693] sup-iface[61f1b0a3f5809edc,6,wlp0s20f3]: wps: type pbc start...
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9704] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9706] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] device (wlp0s20f3): Activation: (wifi) connection 'ASUS_CM_FAST' has security, and secrets exist.  No new secrets needed.
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'ssid' value 'ASUS_CM_FAST'
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'scan_ssid' value '1'
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'bgscan' value 'simple:30:-70:86400'
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'auth_alg' value 'OPEN'
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9707] Config: added 'psk' value '<hidden>'
11月 14 14:41:48 cm-pc wpa_supplicant[497]: wlp0s20f3: SME: Trying to authenticate with fc:34:97:d7:21:28 (SSID='ASUS_CM_FAST' freq=5500 MHz)
11月 14 14:41:48 cm-pc kernel: wlp0s20f3: authenticate with fc:34:97:d7:21:28
11月 14 14:41:48 cm-pc kernel: wlp0s20f3: send auth to fc:34:97:d7:21:28 (try 1/3)
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9808] device (wlp0s20f3): supplicant interface state: disconnected -> authenticating
11月 14 14:41:48 cm-pc NetworkManager[352]: <info>  [1636872108.9809] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> authenticating
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: Trying to associate with fc:34:97:d7:21:28 (SSID='ASUS_CM_FAST' freq=5500 MHz)
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.0077] device (wlp0s20f3): supplicant interface state: authenticating -> associating
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.0077] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
11月 14 14:41:49 cm-pc kernel: wlp0s20f3: authenticated
11月 14 14:41:49 cm-pc kernel: wlp0s20f3: associate with fc:34:97:d7:21:28 (try 1/3)
11月 14 14:41:49 cm-pc kernel: wlp0s20f3: RX AssocResp from fc:34:97:d7:21:28 (capab=0x1011 status=0 aid=22)
11月 14 14:41:49 cm-pc kernel: iwlwifi 0000:00:14.3: Got NSS = 4 - trimming to 2
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: Associated with fc:34:97:d7:21:28
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
11月 14 14:41:49 cm-pc kernel: wlp0s20f3: associated
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: WPA: Key negotiation completed with fc:34:97:d7:21:28 [PTK=CCMP GTK=CCMP]
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to fc:34:97:d7:21:28 completed [id=0 id_str=]
11月 14 14:41:49 cm-pc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
11月 14 14:41:49 cm-pc kernel: wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:d7:21:28
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-46 noise=9999 txrate=490000
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1020] device (wlp0s20f3): supplicant interface state: associating -> completed
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1021] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "ASUS_CM_FAST"
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1021] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> completed
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1023] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-46 noise=9999 txrate=490000
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1029] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-46 noise=9999 txrate=490000
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1222] dhcp4 (wlp0s20f3): state changed unknown -> bound, address=192.168.50.2
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1248] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:49 cm-pc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1' (uid=0 pid=352 comm="/usr/bin/NetworkManager --no-daemon ")
11月 14 14:41:49 cm-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: NetworkManager-dispatcher.service 单元已开始启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ NetworkManager-dispatcher.service 单元已开始启动。
11月 14 14:41:49 cm-pc dbus-daemon[351]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
11月 14 14:41:49 cm-pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: NetworkManager-dispatcher.service 单元已结束启动
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ NetworkManager-dispatcher.service 单元已结束启动。
░░ 
░░ 启动结果为“done”。
11月 14 14:41:49 cm-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1413] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:49 cm-pc kernel: audit: type=1130 audit(1636872109.137:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1416] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1420] manager: NetworkManager state is now CONNECTED_LOCAL
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1428] manager: NetworkManager state is now CONNECTED_SITE
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1429] policy: set 'ASUS_CM_FAST' (wlp0s20f3) as default for IPv4 routing and DNS
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.1451] device (wlp0s20f3): Activation: successful, device activated.
11月 14 14:41:49 cm-pc wpa_supplicant[497]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-41 noise=9999 txrate=490000
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.6199] manager: NetworkManager state is now CONNECTED_GLOBAL
11月 14 14:41:49 cm-pc gdm-password][4296]: gkr-pam: unlocked login keyring
11月 14 14:41:49 cm-pc audit[4296]: USER_AUTH pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.136' (uid=0 pid=4296 comm="gdm-session-worker [pam/gdm-password] ")
11月 14 14:41:49 cm-pc dbus-daemon[351]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:41:49 cm-pc gdm-password][4296]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:41:49 cm-pc audit[4296]: USER_ACCT pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc audit[4296]: CRED_REFR pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc kernel: audit: type=1100 audit(1636872109.737:215): pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc kernel: audit: type=1101 audit(1636872109.737:216): pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc kernel: audit: type=1110 audit(1636872109.737:217): pid=4296 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="cm" exe="/usr/lib/gdm-session-worker" hostname=cm-pc addr=? terminal=/dev/tty1 res=success'
11月 14 14:41:49 cm-pc gnome-shell[877]: loading user theme: /home/cm/.themes/WhiteSur-light/gnome-shell/gnome-shell.css
11月 14 14:41:49 cm-pc gnome-shell[877]: Ignoring length property that isn't a number at line 2594, col 24
11月 14 14:41:49 cm-pc gnome-shell[877]: Ignoring length property that isn't a number at line 2594, col 24
11月 14 14:41:49 cm-pc gnome-shell[877]: Ignoring length property that isn't a number at line 2594, col 24
11月 14 14:41:49 cm-pc gnome-shell[877]: Ignoring length property that isn't a number at line 2594, col 24
11月 14 14:41:49 cm-pc NetworkManager[352]: <info>  [1636872109.9464] agent-manager: agent[993b702287940db8,:1.51/org.gnome.Shell.NetworkAgent/1000]: agent registered
11月 14 14:41:49 cm-pc gnome-shell[877]: Ignoring length property that isn't a number at line 2594, col 24
11月 14 14:41:52 cm-pc ntpd[364]: Listen normally on 12 wlp0s20f3 192.168.50.2:123
11月 14 14:41:52 cm-pc ntpd[364]: Listen normally on 13 wlp0s20f3 [fe80::16f1:2de8:46c2:c410%2]:123
11月 14 14:41:52 cm-pc ntpd[364]: new interface(s) found: waking up resolver
11月 14 14:41:57 cm-pc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.137' (uid=0 pid=4342 comm="sudo journalctl -xe ")
11月 14 14:41:57 cm-pc dbus-daemon[351]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:41:57 cm-pc sudo[4342]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:41:57 cm-pc audit[4342]: USER_ACCT pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc sudo[4342]:       cm : TTY=pts/0 ; PWD=/home/cm ; USER=root ; COMMAND=/usr/bin/journalctl -xe
11月 14 14:41:57 cm-pc audit[4342]: CRED_REFR pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc sudo[4342]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
11月 14 14:41:57 cm-pc audit[4342]: USER_START pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc kernel: audit: type=1101 audit(1636872117.646:218): pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc kernel: audit: type=1110 audit(1636872117.646:219): pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc kernel: audit: type=1105 audit(1636872117.646:220): pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc sudo[4342]: pam_unix(sudo:session): session closed for user root
11月 14 14:41:57 cm-pc audit[4342]: USER_END pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc audit[4342]: CRED_DISP pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc kernel: audit: type=1106 audit(1636872117.662:221): pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:57 cm-pc kernel: audit: type=1104 audit(1636872117.662:222): pid=4342 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:41:59 cm-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
11月 14 14:41:59 cm-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:41:59 cm-pc kernel: audit: type=1131 audit(1636872119.419:223): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
11月 14 14:42:06 cm-pc dbus-daemon[351]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.138' (uid=0 pid=4350 comm="sudo journalctl -xe ")
11月 14 14:42:06 cm-pc dbus-daemon[351]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:42:06 cm-pc sudo[4350]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
11月 14 14:42:06 cm-pc kernel: audit: type=1101 audit(1636872126.779:224): pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:42:06 cm-pc audit[4350]: USER_ACCT pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cm" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:42:06 cm-pc sudo[4350]:       cm : TTY=pts/0 ; PWD=/home/cm ; USER=root ; COMMAND=/usr/bin/journalctl -xe
11月 14 14:42:06 cm-pc audit[4350]: CRED_REFR pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:42:06 cm-pc audit[4350]: USER_START pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:42:06 cm-pc sudo[4350]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
11月 14 14:42:06 cm-pc kernel: audit: type=1110 audit(1636872126.782:225): pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
11月 14 14:42:06 cm-pc kernel: audit: type=1105 audit(1636872126.782:226): pid=4350 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

依云 · 2021-11-14 15:26:12

以后贴长日志请用 pastebin。复制起来太难了。
以后贴 journalctl 日志时不要加 -x 选项。噪音而已。文档有说

man journalctl 说：

Note: when attaching journalctl output to bug reports, please do not use -x.

你的 PCI 设备 0000:08:00.0 是什么？它阻止了挂起操作。

chen05_20 · 2021-11-14 16:28:03

依云说：

以后贴长日志请用 pastebin。复制起来太难了。
以后贴 journalctl 日志时不要加 -x 选项。噪音而已。文档有说
man journalctl 说：
Note: when attaching journalctl output to bug reports, please do not use -x.
你的 PCI 设备 0000:08:00.0 是什么？它阻止了挂起操作。

好的，以后注意,lspci 好像是一个无线设备。

$lspci
00:00.0 Host bridge: Intel Corporation Device 9a12 (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Device 9a40 (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 01)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #1 (rev 01)
00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #2 (rev 01)
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)
00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #1 (rev 01)
00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
00:15.3 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #3 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
00:1f.0 ISA bridge: Intel Corporation Device a087 (rev 20)
00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
04:00.0 Non-Volatile memory controller: Sandisk Corp Device 5008 (rev 01)
08:00.0 Wireless controller [0d40]: Foxconn International, Inc. Device e0ab

chen05_20 · 2021-11-15 14:13:41

依云说：

以后贴长日志请用 pastebin。复制起来太难了。
以后贴 journalctl 日志时不要加 -x 选项。噪音而已。文档有说
man journalctl 说：
Note: when attaching journalctl output to bug reports, please do not use -x.
你的 PCI 设备 0000:08:00.0 是什么？它阻止了挂起操作。

有没有可能是之前用过create_ap,有什么遗留的进程或者设置没关掉？

Arch Linux

#1 2021-11-13 22:59:08

笔记本最近没法进入睡眠模式了

#2 2021-11-14 12:47:49

Re: 笔记本最近没法进入睡眠模式了

#3 2021-11-14 14:46:12

Re: 笔记本最近没法进入睡眠模式了

#4 2021-11-14 15:26:12

Re: 笔记本最近没法进入睡眠模式了

#5 2021-11-14 16:28:03

Re: 笔记本最近没法进入睡眠模式了

#6 2021-11-15 14:13:41

Re: 笔记本最近没法进入睡眠模式了

页脚