Hi,
A few hours ago, I had the following problem for the first time: I closed my laptop, stowed it in my bag, and 4 hours later, I realized that it was warm, that it hadn’t gone to standby 
.
For the moment, I have the impression that my Thinkpad T14s Gen3 AMD is fine, nothing damaged .
Here’s what I see in the logs:
$ sudo journalctl
oct. 13 18:03:00 t14s kernel: OOM killer enabled.
oct. 13 18:03:00 t14s NetworkManager[1993]: <info> [1697212980.2868] manager: NetworkManager state is now ASLEEP
oct. 13 18:03:00 t14s kernel: Restarting tasks ... done.
oct. 13 18:03:00 t14s kernel: random: crng reseeded on system resumption
oct. 13 18:03:00 t14s systemd[1]: run-docker-runtime\x2drunc-moby-9e421e872f9a49f59edd78ffdb2f63ded46d1bb6126256f9bfc55766c14b7dca-runc.7CrdJu.mount: Deactivated successfully.
oct. 13 18:03:00 t14s bluetoothd[1722]: Controller resume with wake event 0x0
oct. 13 18:03:00 t14s kernel: PM: suspend exit
oct. 13 18:03:00 t14s kernel: PM: suspend entry (s2idle)
oct. 13 18:03:00 t14s kernel: Filesystems sync: 0.016 seconds
oct. 13 18:03:20 t14s kernel: Freezing user space processes
oct. 13 18:03:20 t14s kernel: Freezing user space processes failed after 20.000 seconds (2 tasks refusing to freeze, wq_busy=0):
oct. 13 18:03:20 t14s kernel: task:alsactl state:D stack:0 pid:1927 ppid:1 flags:0x00000006
oct. 13 18:03:20 t14s kernel: Call Trace:
oct. 13 18:03:20 t14s kernel: <TASK>
oct. 13 18:03:20 t14s kernel: __schedule+0x3ee/0x14c0
oct. 13 18:03:20 t14s kernel: schedule+0x5e/0xd0
oct. 13 18:03:20 t14s kernel: snd_power_ref_and_wait+0xde/0x130 [snd]
oct. 13 18:03:20 t14s kernel: ? __pfx_autoremove_wake_function+0x10/0x10
oct. 13 18:03:20 t14s kernel: snd_ctl_elem_info+0x48/0x190 [snd]
oct. 13 18:03:20 t14s kernel: snd_ctl_elem_info_user+0x54/0xb0 [snd]
oct. 13 18:03:20 t14s kernel: snd_ctl_ioctl+0x2bf/0x800 [snd]
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: __x64_sys_ioctl+0x97/0xd0
oct. 13 18:03:20 t14s kernel: do_syscall_64+0x60/0x90
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? syscall_exit_to_user_mode+0x2b/0x40
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? syscall_exit_to_user_mode+0x2b/0x40
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
oct. 13 18:03:20 t14s kernel: RIP: 0033:0x7f7626388ecd
oct. 13 18:03:20 t14s kernel: RSP: 002b:00007ffdb3ae9960 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
oct. 13 18:03:20 t14s kernel: RAX: ffffffffffffffda RBX: 00007ffdb3aea2c0 RCX: 00007f7626388ecd
oct. 13 18:03:20 t14s kernel: RDX: 00007ffdb3ae99d0 RSI: 00000000c1105511 RDI: 0000000000000009
oct. 13 18:03:20 t14s kernel: RBP: 00007ffdb3ae99b0 R08: 0000000000000190 R09: 0000000000000001
oct. 13 18:03:20 t14s kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000555d74d56f40
oct. 13 18:03:20 t14s kernel: R13: 00007ffdb3ae99d0 R14: 0000555d74d5a480 R15: 0000000000000110
oct. 13 18:03:20 t14s kernel: </TASK>
oct. 13 18:03:20 t14s kernel: task:wireplumber state:D stack:0 pid:3686 ppid:3489 flags:0x00000006
oct. 13 18:03:20 t14s kernel: Call Trace:
oct. 13 18:03:20 t14s kernel: <TASK>
oct. 13 18:03:20 t14s kernel: __schedule+0x3ee/0x14c0
oct. 13 18:03:20 t14s kernel: ? inotify_handle_inode_event+0x150/0x230
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: schedule+0x5e/0xd0
oct. 13 18:03:20 t14s kernel: schedule_preempt_disabled+0x15/0x30
oct. 13 18:03:20 t14s kernel: rwsem_down_write_slowpath+0x1f3/0x640
oct. 13 18:03:20 t14s kernel: down_write+0x5b/0x60
oct. 13 18:03:20 t14s kernel: snd_ctl_release+0x8a/0x130 [snd]
oct. 13 18:03:20 t14s kernel: __fput+0xf5/0x2a0
oct. 13 18:03:20 t14s kernel: task_work_run+0x5d/0x90
oct. 13 18:03:20 t14s kernel: exit_to_user_mode_prepare+0x1eb/0x1f0
oct. 13 18:03:20 t14s kernel: syscall_exit_to_user_mode+0x1b/0x40
oct. 13 18:03:20 t14s kernel: do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? syscall_exit_to_user_mode+0x2b/0x40
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? srso_alias_return_thunk+0x5/0x7f
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: ? do_syscall_64+0x6c/0x90
oct. 13 18:03:20 t14s kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
oct. 13 18:03:20 t14s kernel: RIP: 0033:0x7f85c31ef85c
oct. 13 18:03:20 t14s kernel: RSP: 002b:00007ffeae80a090 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
oct. 13 18:03:20 t14s kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f85c31ef85c
oct. 13 18:03:20 t14s kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000002f
oct. 13 18:03:20 t14s kernel: RBP: 00007ffeae80a0a0 R08: 000055ecbdf2fe50 R09: 0000000000000000
oct. 13 18:03:20 t14s kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000055ecbde63240
oct. 13 18:03:20 t14s kernel: R13: 000055ecbdf8d800 R14: 000055ecbdf8d790 R15: 000055ecbdf312d0
oct. 13 18:03:20 t14s kernel: </TASK>
oct. 13 18:03:20 t14s kernel: OOM killer enabled.
oct. 13 18:03:20 t14s rtkit-daemon[1747]: The canary thread is apparently starving. Taking action.
oct. 13 18:03:20 t14s rtkit-daemon[1747]: Demoting known real-time threads.
oct. 13 18:03:20 t14s rtkit-daemon[1747]: Demoted 0 threads.
oct. 13 18:03:20 t14s kernel: Restarting tasks ... done.
oct. 13 18:03:20 t14s kernel: random: crng reseeded on system resumption
oct. 13 18:03:21 t14s bluetoothd[1722]: Controller resume with wake event 0x0
oct. 13 18:03:21 t14s kernel: PM: suspend exit
oct. 13 18:03:21 t14s systemd-sleep[1121211]: Failed to put system to sleep. System resumed again: Device or resource busy
oct. 13 18:03:21 t14s systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
oct. 13 18:03:21 t14s systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
oct. 13 18:03:21 t14s systemd[1]: Failed to start systemd-suspend.service - System Suspend.
oct. 13 18:03:21 t14s systemd[1]: Dependency failed for suspend.target - Suspend.
Here are the details of my configuration: inxi_2023-03-26.txt · GitHub
stephane@t14s
-------------
OS: Fedora Linux 38 (Workstation Edition) x86_64
Host: 21CQCTO1WW ThinkPad T14s Gen 3
Kernel: 6.5.6-200.fc38.x86_64
Uptime: 38 mins
Packages: 3021 (rpm), 44 (flatpak)
Shell: zsh 5.9
Resolution: 1920x1200
DE: GNOME 44.5
WM: Mutter
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: tmux
CPU: AMD Ryzen 7 PRO 6850U with Radeon Graphics (16) @ 4.768GHz
GPU: AMD ATI Radeon 680M
Memory: 5385MiB / 30836MiB
Do you have any idea why this might be?
Best regards,
Stéphane