System shuts down abruptly without warning

Quite recently, on the 19th of December to be exact, my system started to randomly, or abruptly, shut down. No warning is given.

I ran sensors immediately after reboot, but no values where out of range.

Checking journalctl I discovered that in the logs it said that the power button was pressed (even though I had not pressed it).

$ journalctl --since "1 hour ago"
ec 22 12:53:26 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.101.74 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=24576 PROTO=2 
Dec 22 12:57:07 tuxwarrior NetworkManager[1773]: <info>  [1703267827.1820] dhcp4 (wlp68s0): state changed new lease, address=192.168.99.219
Dec 22 12:57:07 tuxwarrior dbus-daemon[1733]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=1773 comm="/usr/bin/Netwo>
Dec 22 12:57:07 tuxwarrior systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 22 12:57:07 tuxwarrior dbus-daemon[1733]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 22 12:57:07 tuxwarrior systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 22 12:57:17 tuxwarrior systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 22 12:59:46 tuxwarrior rtkit-daemon[2601]: Supervising 7 threads of 5 processes of 1 users.
Dec 22 12:59:46 tuxwarrior rtkit-daemon[2601]: Supervising 7 threads of 5 processes of 1 users.
Dec 22 13:00:30 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.101.74 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=6174 PROTO=2 
Dec 22 13:00:58 tuxwarrior systemd-logind[1739]: Power key pressed short.
Dec 22 13:00:58 tuxwarrior systemd-logind[1739]: The system will power off now!
Dec 22 13:00:58 tuxwarrior systemd-logind[1739]: System is powering down.
-- Boot b46eae99fa1e4aaf84a84430ef197be1 --
Dec 22 13:03:22 tuxwarrior kernel: microcode: updated early: 0xca -> 0xf8, date = 2023-02-23
Dec 22 13:03:22 tuxwarrior kernel: Linux version 6.6.7-4-MANJARO (builduser@fv-az563-733) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Mon Dec 18 03:58:56 UTC 2023
Dec 22 13:03:22 tuxwarrior kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64 root=UUID=74458dbb-feb8-4898-8716-c7bc82302328 rw amd_iommu=on iommu=pt quiet cryptdevice=UUID=22c33ed5-bf14-4137-947e-ea101ee86678:luks-22c33ed5>
Dec 22 13:03:22 tuxwarrior kernel: BIOS-provided physical RAM map:

Two more times the same thing happened:

$ journalctl | grep 'Power key'
Dec 19 19:09:15 tuxwarrior systemd-logind[1735]: Power key pressed short.
Dec 22 11:27:34 tuxwarrior systemd-logind[1734]: Power key pressed short.
Dec 22 13:00:58 tuxwarrior systemd-logind[1739]: Power key pressed short.

I decided to disable the power button in xfce4-power-manager-settings:

Unfortunately, the problem did not get solved. The power button is lo longer “pressed”, but the system keeps shutting down. Below are some outputs from the journal. I also tried booting using kernel 6.5.13 instead of 6.6.8. That did not do any difference either.

$ journalctl --since "1 hour ago"
Dec 24 16:32:33 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=8792 PROTO=2 
Dec 24 16:33:45 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=28002 PROTO=2 
Dec 24 16:35:31 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40765 PROTO=2 
Dec 24 16:35:50 tuxwarrior kernel: gdbus[1200122]: segfault at 26 ip 00007fbc15ecb7a4 sp 00007fbc0fffe538 error 4 in libc.so.6[7fbc15d9a000+15a000] likely on CPU 18 (core 8, socket 0)
Dec 24 16:35:50 tuxwarrior kernel: Code: 00 00 00 0f 1f 00 f3 0f 1e fa 48 85 d2 74 54 c5 f9 6e c6 c4 e2 7d 78 c0 89 f8 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 3c 02 00 00 <c5> fd 74 0f c5 fd d7 c1 48 83 fa 20 76 0e 85 c0 74 5a 0f bc c0>
Dec 24 16:36:33 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=11081 PROTO=2 
Dec 24 16:41:22 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:62:50:a8:19:bc:c9:08:00 SRC=192.168.108.192 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=53400 PROTO=2 
Dec 24 16:42:37 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=59603 PROTO=2 
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:42:51 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:43:04 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=60147 PROTO=2 
Dec 24 16:43:38 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=52000 PROTO=2 
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Supervising 7 threads of 5 processes of 1 users.
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Successfully made thread 1213703 of process 1150748 owned by '1000' RT at priority 10.
Dec 24 16:43:46 tuxwarrior rtkit-daemon[2477]: Supervising 8 threads of 6 processes of 1 users.
Dec 24 16:44:13 tuxwarrior kernel: snd_hda_intel 0000:00:1f.3: Unstable LPIB (261592 >= 8192); disabling LPIB delay counting
Dec 24 16:45:26 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:62:50:a8:19:bc:c9:08:00 SRC=192.168.108.192 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=7508 PROTO=2 
Dec 24 16:45:53 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=62017 PROTO=2 
Dec 24 16:47:46 tuxwarrior NetworkManager[1770]: <info>  [1703454466.9261] dhcp4 (wlp68s0): state changed new lease, address=192.168.99.219
Dec 24 16:47:46 tuxwarrior dbus-daemon[1728]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1770 comm="/usr/bin/Networ>
Dec 24 16:47:46 tuxwarrior systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 24 16:47:46 tuxwarrior dbus-daemon[1728]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 24 16:47:46 tuxwarrior systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 24 16:47:56 tuxwarrior systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 24 16:48:16 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=34001 PROTO=2 
Dec 24 16:49:50 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=2321 PROTO=2 
Dec 24 16:49:59 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=60053 PROTO=2 
Dec 24 16:50:29 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=47022 PROTO=2 
Dec 24 16:51:43 tuxwarrior rtkit-daemon[2477]: Supervising 8 threads of 6 processes of 1 users.
Dec 24 16:51:43 tuxwarrior rtkit-daemon[2477]: Supervising 8 threads of 6 processes of 1 users.
Dec 24 16:52:13 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.103.107 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=7186 PROTO=2 
Dec 24 16:52:36 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:22:de:b7:46:0b:97:08:00 SRC=192.168.98.67 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4686 PROTO=2 
Dec 24 16:52:36 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=63773 PROTO=2 
-- Boot 99fd771e0fc748d3a97658390e1f43d5 --
Dec 24 17:24:50 tuxwarrior kernel: microcode: updated early: 0xca -> 0xf8, date = 2023-02-23
Dec 24 17:24:50 tuxwarrior kernel: Linux version 6.5.13-6-MANJARO (builduser@fv-az526-674) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Mon Dec 18 03:57:17 UTC 2023
Dec 24 17:24:50 tuxwarrior kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5-x86_64 root=UUID=74458dbb-feb8-4898-8716-c7bc82302328 rw amd_iommu=on iommu=pt quiet cryptdevice=UUID=22c33ed5-bf14-4137-947e-ea101ee86678:luks-22c33ed5->
Dec 24 17:24:50 tuxwarrior kernel: BIOS-provided physical RAM map:
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x0000000040400000-0x000000006b200fff] usable
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b201000-0x000000006b201fff] ACPI NVS
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b202000-0x000000006b232fff] usable
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b233000-0x000000006b233fff] reserved
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b234000-0x000000006e558fff] usable
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006e559000-0x000000006ee58fff] reserved
Dec 24 17:24:50 tuxwarrior kernel: BIOS-e820: [mem 0x000000006ee59000-0x000000007d06efff] usable
$ journalctl --since "1 hour ago"
Dec 27 07:24:43 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:d2:51:97:61:d6:1b:08:00 SRC=192.168.104.248 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=843 PROTO=2 
Dec 27 07:25:23 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.105.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=7802 PROTO=2 
Dec 27 07:26:30 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:86:63:64:3d:01:bb:08:00 SRC=192.168.104.255 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=45329 PROTO=2 
Dec 27 07:28:21 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:5e:77:28:a9:e1:41:08:00 SRC=192.168.104.42 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=62007 PROTO=2 
Dec 27 07:29:38 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.105.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=48332 PROTO=2 
Dec 27 07:29:51 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=62399 PROTO=2 
Dec 27 07:31:33 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=13470 PROTO=2 
Dec 27 07:33:04 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=29350 PROTO=2 
Dec 27 07:33:29 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:10:9f:41:b4:72:0a:08:00 SRC=192.168.98.73 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=32230 PROTO=2 
Dec 27 07:33:33 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.105.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=5177 PROTO=2 
Dec 27 07:34:45 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:d2:51:97:61:d6:1b:08:00 SRC=192.168.104.248 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=8411 PROTO=2 
Dec 27 07:35:34 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:d2:51:97:61:d6:1b:08:00 SRC=192.168.104.248 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=8816 PROTO=2 
Dec 27 07:36:02 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:d2:51:97:61:d6:1b:08:00 SRC=192.168.104.248 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=13164 PROTO=2 
Dec 27 07:42:15 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:86:63:64:3d:01:bb:08:00 SRC=192.168.104.255 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=47288 PROTO=2 
Dec 27 07:42:23 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=61873 PROTO=2 
Dec 27 07:43:14 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:86:63:64:3d:01:bb:08:00 SRC=192.168.104.255 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=30467 PROTO=2 
Dec 27 07:43:38 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:86:63:64:3d:01:bb:08:00 SRC=192.168.104.255 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=45280 PROTO=2 
Dec 27 07:44:21 tuxwarrior NetworkManager[1808]: <info>  [1703681061.6162] dhcp4 (wlp68s0): state changed new lease, address=192.168.99.219
Dec 27 07:44:21 tuxwarrior dbus-daemon[1767]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=1808 comm="/usr/bin/Networ>
Dec 27 07:44:21 tuxwarrior systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 27 07:44:21 tuxwarrior dbus-daemon[1767]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 27 07:44:21 tuxwarrior systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 27 07:44:31 tuxwarrior systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 27 07:44:45 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=65219 PROTO=2 
Dec 27 07:44:46 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:d2:51:97:61:d6:1b:08:00 SRC=192.168.104.248 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=53410 PROTO=2 
Dec 27 07:45:27 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:86:63:64:3d:01:bb:08:00 SRC=192.168.104.255 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=56252 PROTO=2 
Dec 27 07:45:45 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:e2:23:77:8b:2f:dc:08:00 SRC=192.168.105.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=13967 PROTO=2 
Dec 27 07:47:21 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=253 PROTO=2 
Dec 27 07:47:46 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=7703 PROTO=2 
Dec 27 07:48:02 tuxwarrior kernel: [UFW BLOCK] IN=wlp68s0 OUT= MAC=01:00:5e:00:00:fb:2a:ca:46:16:e8:26:08:00 SRC=192.168.105.109 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=43044 PROTO=2 
-- Boot 9e866e57655046c780a0a719a6c7a2ee --
Dec 27 08:08:33 tuxwarrior kernel: microcode: updated early: 0xca -> 0xf8, date = 2023-02-23
Dec 27 08:08:33 tuxwarrior kernel: Linux version 6.6.8-2-MANJARO (builduser@fv-az913-981) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Thu Dec 21 16:21:45 UTC 2023
Dec 27 08:08:33 tuxwarrior kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64 root=UUID=74458dbb-feb8-4898-8716-c7bc82302328 rw amd_iommu=on iommu=pt quiet cryptdevice=UUID=22c33ed5-bf14-4137-947e-ea101ee86678:luks-22c33ed5->
Dec 27 08:08:33 tuxwarrior kernel: BIOS-provided physical RAM map:
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x0000000040400000-0x000000006b200fff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b201000-0x000000006b201fff] ACPI NVS
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b202000-0x000000006b232fff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b233000-0x000000006b233fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006b234000-0x000000006e558fff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006e559000-0x000000006ee58fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000006ee59000-0x000000007d06efff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000007d06f000-0x000000007d43efff] type 20
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000007d43f000-0x000000007f28efff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000007f28f000-0x000000007ff7efff] ACPI NVS
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000007ff7f000-0x000000007fffefff] ACPI data
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x000000007ffff000-0x000000007fffffff] usable
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x0000000080000000-0x00000000efffffff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fc800000-0x00000000fe7fffff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dec 27 08:08:33 tuxwarrior kernel: BIOS-e820: [mem 0x00000000ff400000-0x00000000ffffffff] reserved

If anyone has ideas to how to further debug this, or solve this issue, it would make me happy!

Can you try memtest? Stress testing - ArchWiki

1 Like

I see microcode load when you start your system and while I have no idea what is creating your issue - the first thing I would try is moving the ucode.img from /boot to a backup location - then run

sudo mkinitcpio -P
sudo grub-mkconfig -o /boot/grub/grub.cfg

Reboot see if it goes away.

2 Likes

Hello @mzuniga :wink:

Well, doubt that this is a software problem. If it “crash”, no error was logged and you see the power key was pressed, then I suppose the physical power key is quite worn out.

Anyway you can disable the key as workaround like this:

sudo mkdir -p /etc/systemd/logind.conf.d/
sudo bash -c 'echo -e "[Login]\nHandlePowerKey=ignore" >  /etc/systemd/logind.conf.d/overwrite.conf'

If it is not the power key, then I would suspect a defect of the power delivery or capacitors of the mainboard are damaged.

2 Likes

Are you wearing any jewellery?

I’m not sure of all of your physical space and whatnot … but I have noticed, for example, many laptops can be given the equivalent of a ‘short press’ of the power button if a weak magnet is passed over certain areas (often near the power button, such as initiating a latch). I have seen it accidentally engaged with rechargeable nicotine vaporizers in hand passing over that area.

Just a thought.

1 Like

@eugen-b @linux-aarhus @megavolt @cscs

Thanks a lot for your feedback. I appreciate your help!

I decided to start with a memtest, something that has taken me several hours today (created a bootable usb using Memtest86+ v6).

During the first run, after about 20% completion, the system once more abruptly shut down. I assumed that it was a memory error that did lead to this. So, I tried again. This time the memtest completed without any errors or shutdowns. So I maybe your assumption, @megavolt, about a defect power delivery, is the most likely one (since I am not vaping nor wearing jewlery, @cscs :smiley: ).

I earlier had some issue with my battery, as it never would recharge. I had to physically remove it from my PC, let it sit for a minute, before I put it back in the machine. I have no idea if that issue is related. But, I have now removed the battery completely. Just want to check if that will making any difference at all.

Regarding the microcode, maybe it still might be the source of this problem? I assume that the microcode is executed even before I boot into memtest. Or, am I wrong about this?

$ sudo ls -al /boot/*ucode*
-rw-r--r-- 1 root root 7368704 Nov 14 11:33 /boot/intel-ucode.img

Found some info about intel-ucode.img here.

Can I safely move intel-ucode.img to another location, run the above commands, and the system will reboot normally?

1 Like

At first glance this seems to indicate a short in the power key, as the line suggests, but a shutdown could also be triggered as a result of overheating (though usually without elegance). How is the ventilation?

Yes you can. There may be a errors shown, but booting would continue. Make sure to replace it later.

1 Like

Thank you, @soundofthunder.

How is the ventilation?

The ventilation is good, and I have checked that the fans are clean.

Make sure to replace it later.

When I have tested this, and moved it back into /boot/, can I then run the same commands, to enable this again?

sudo mkinitcpio -P
sudo grub-mkconfig -o /boot/grub/grub.cfg

Yes, you can do that.

Could you also provide the output of:

inxi --admin --verbosity=7 --filter --no-host --width

It may be helpful to know more about your system. This command will print useful data while filtering out any personal information.

2 Likes
$ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=74458dbb-feb8-4898-8716-c7bc82302328 rw amd_iommu=on iommu=pt
    quiet
    cryptdevice=UUID=22c33ed5-bf14-4137-947e-ea101ee86678:luks-22c33ed5-bf14-4137-947e-ea101ee86678
    root=/dev/mapper/luks-22c33ed5-bf14-4137-947e-ea101ee86678
    udev.log_priority=3
  Desktop: i3 v: 4.23 info: i3bar vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: TUXEDO product: TUXEDO Book XUX7 Gen11 v: N/A
    serial: <superuser required> Chassis: Notebook type: 10
    serial: <superuser required>
  Mobo: TUXEDO model: X170SM serial: <superuser required> UEFI: INSYDE
    v: 1.07.03RTR1 date: 07/03/2020
Battery:
  ID-1: BAT0 charge: 92.1 Wh (100.0%) condition: 92.1/96.5 Wh (95.5%)
    volts: 16.3 min: 14.4 model: Notebook BAT type: Li-ion serial: <filter>
    status: full
Memory:
  System RAM: total: 128 GiB available: 125.57 GiB used: 7.45 GiB (5.9%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i9-10900K bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA5 (165) stepping: 5 microcode: 0xF8
  Topology: cpus: 1x cores: 10 tpc: 2 threads: 20 smt: enabled cache:
    L1: 640 KiB desc: d-10x32 KiB; i-10x32 KiB L2: 2.5 MiB desc: 10x256 KiB
    L3: 20 MiB desc: 1x20 MiB
  Speed (MHz): avg: 3573 high: 5300 min/max: 800/5300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1387 2: 1406 3: 3769
    4: 5300 5: 4901 6: 5300 7: 5300 8: 1272 9: 1090 10: 5300 11: 5300 12: 5300
    13: 1387 14: 4874 15: 5300 16: 5300 17: 5300 18: 1958 19: 802 20: 930
    bogomips: 148040
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
    ibrs_enhanced ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq
    pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdrand rdseed
    rdtscp rep_good sdbg sep sgx sgx_lc smap smep smx ss ssbd sse sse2 sse4_1
    sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
    tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional,
    RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU104BM [GeForce RTX 2080 SUPER Mobile / Max-Q]
    vendor: CLEVO/KAPOK driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm
    non-free: 545.xx+ status: current (as of 2023-11; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
    bus-ID: 01:00.0 chip-ID: 10de:1ed3 class-ID: 0300
  Device-2: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:5 chip-ID: 04f2:b685
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.10 compositor: Compton driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 256 s-size: 254x140mm (10.00x5.51")
    s-diag: 290mm (11.42")
  Monitor-1: Unknown-1 mapped: DP-2 res: 2560x1440 hz: 60 dpi: 171
    size: 381x214mm (15x8.43") modes: 3840x2160
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 44:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp68s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
  IP v6: <filter> type: noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-2: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> virtual: stable-privacy proto kernel_ll scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Logical:
  Message: No logical block device data found.
  Device-1: luks-22c33ed5-bf14-4137-947e-ea101ee86678 maj-min: 254:0
    type: LUKS dm: dm-0 size: 232.59 GiB
  Components:
  p-1: nvme2n1p2 maj-min: 259:2 size: 232.59 GiB
  Device-2: drive2 maj-min: 254:1 type: LUKS dm: dm-1 size: 1.82 TiB
  Components:
  p-1: nvme0n1 maj-min: 259:3 size: 1.82 TiB
  Device-3: drive3 maj-min: 254:2 type: LUKS dm: dm-2 size: 1.82 TiB
  Components:
  p-1: nvme1n1 maj-min: 259:4 size: 1.82 TiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.88 TiB used: 1.16 TiB (29.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 70.8 C
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 69.8 C
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B2QGXA7 temp: 65.8 C
    scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Kingston model: DataTraveler 3.0
    size: 14.44 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.0
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: PMAP scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 232.59 GiB size: 227.88 GiB (97.98%)
    used: 114.68 GiB (50.3%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-22c33ed5-bf14-4137-947e-ea101ee86678 label: N/A
    uuid: 74458dbb-feb8-4898-8716-c7bc82302328
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 480 KiB (0.2%) fs: vfat dev: /dev/nvme2n1p1 maj-min: 259:1 label: N/A
    uuid: 1F06-F175
  ID-3: /media/drive2 raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 850.86 GiB (46.4%) fs: ext4 dev: /dev/dm-1 maj-min: 254:1
    mapped: drive2 label: N/A uuid: N/A
  ID-4: /media/drive3 raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 218.72 GiB (11.9%) fs: ext4 dev: /dev/dm-2 maj-min: 254:2
    mapped: drive3 label: N/A uuid: N/A
  ID-5: /media/nas raw-size: N/A size: 12.21 TiB used: 6.59 TiB (54.0%)
    fs: cifs dev: /dev/fro
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 1.6 MiB fs: iso9660
  ID-2: /dev/sda2 maj-min: 8:2 size: 4 MiB fs: vfat label: MEMTEST-ESP
    uuid: C4EB-B66B
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-4:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-4.1:4 info: Holtek Keyboard type: keyboard,mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 04d9:0169 class-ID: 0301
  Device-2: 1-4.2:6 info: Logitech G PRO Gaming Mouse type: mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 300mA chip-ID: 046d:c08c class-ID: 0300
    serial: <filter>
  Device-3: 1-4.3:11 info: Canon PIXMA MG2500 Series type: printer
    driver: usblp interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 2mA chip-ID: 04a9:176d class-ID: 0701 serial: <filter>
  Device-4: 1-5:3 info: Integrated Express ITE Device(829x) type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:8910 class-ID: 0300
  Device-5: 1-8:5 info: Chicony USB2.0 Camera type: video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b685 class-ID: 0e02
  Device-6: 1-9:7 info: Integrated Express IT8297 RGB LED Controller
    type: keyboard driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 048d:8297 class-ID: 0301
  Device-7: 1-10:8 info: Synaptics type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 06cb:00a8 class-ID: ff00 serial: <filter>
  Device-8: 1-14:10 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-3: 2-0:1 info: super-speed hub ports: 10 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-1:3 info: Kingston DataTraveler 100 G3/G4/SE9 G2/50 Kyson
    type: mass storage driver: usb-storage interfaces: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 504mA
    chip-ID: 0951:1666 class-ID: 0806 serial: <filter>
  Hub-4: 2-4:2 info: Realtek Hub ports: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-10: 8-0:1 info: super-speed hub ports: 1 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 68.0 C pch: 97.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 427 Uptime: 5h 32m wakeups: 0 Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1457 libs: 390 tools: pamac,yay Shell: Bash
  v: 5.2.21 running-in: urxvtd inxi: 3.3.31

You don’t seem to have a swap partition defined. That can possibly contribute to random shutdowns. In this instance, it’s unlikely, considering you have 128GB of RAM.

Once again, I think this points to hardware, rather than Manjaro. It might be best to have a local computer repair shop look at it.

1 Like

All your drive temperatures are rather in the higher range of what is being acceptable.

2 Likes

You might consider re-evaluating whatever cooling you have. Perhaps use more chassis fans better positioned to cool the drives. Overheating will cause shutdowns randomly, depending on how hard you’re cooking the computer at any given time.

Playing intensive games (for example) can drive temperatures to the point that the CPU can no longer cope; and the system shuts down. If it’s a particularly good computer, shutdown will be triggered before damage can occur.

1 Like

@Wollie @soundofthunder

All your drive temperatures are rather in the higher range of what is being acceptable.

Good point. I have now put the notebook on a stand, to lift it off the table. I guess it will help some.

You might consider re-evaluating whatever cooling you have. Perhaps use more chassis fans better positioned to cool the drives.

It is not easy to do much with the internal fans, as it is a notebook. But it unfortunately gets quite hot. I hope the stand will help.

I think this points to hardware, rather than Manjaro. It might be best to have a local computer repair shop look at it.

Yes, you might be right. Luckily the system is still under warranty, so I will contact support. I will report back here with the findings.

I appreciate all inputs!

Yes, a momentary lapse of reason (thinking it a desktop) :). Possibly the internal fans could be replaced (again, by your local repairer), or at least cleaned thoroughly, if you can’t reach them yourself.

I dare say it will. Blocking the air intake is one of the more common reasons for laptop overheating (running it flat on a table, the floor, a bed, or on a cushion).

The stand you describe can certainly help in most cases. Be sure to let us know the outcome. Cheers.

1 Like

Yes, you are right. After having put the computer on a stand instead of directly on the table, the drive temperatures seems to have dropped around 20 degrees, from around 70 to 50 C. I should have done that before!

  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 53.9 C
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 50.9 C
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B2QGXA7 temp: 47.9 C
    scheme: GPT

When I have more info I will report back to HQ :smiley:

1 Like

This is a powerful Clevo gaming laptop sold with a linux os option, (Tuxedo and Schenker are 2 of their German brands) and they are getting hot quickly and need regular clean-outs. On the plus side they offer very easy access and allow opening the case without losing warranty.

Those laptops have decent support and get a fair amount of ec/bios updates (always do ec first) when they are new, so check for updates on the Tuxedo site. You do not need windows to upgrade them.
Once you’re up-to-date check your bios for any performance options and try if any changes there might help your issue. Warning: Unfortunately there are problems with Comet Lake U CPUs and Undervolting. It may happen that the system “freezes” with activated Undervolting.

3 Likes

Thank you for the info, @6x12! Tuxedo support have asked my to update the Samsung SSD Firmware, to see if that helps. So far I have been unable to create a bootable USB drive, as the Samsung iso seems a bit problematic. However, I shall try another USB drive, to see if that makes any difference.

The temperatures also is a lot healthier after I put the notebook on a stand. I will check if I can easily clean the fans on the inside (from the outside things look clean), to make sure the air flows even better. And, I have ordered an external fan that I will try to use to see if it helps keeping the system even a tad cooler.

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +62.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +56.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +54.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +62.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:        +55.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:        +56.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:        +55.0°C  (high = +82.0°C, crit = +100.0°C)

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +86.0°C  

nvme-pci-0700
Adapter: PCI adapter
Composite:    +52.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +52.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          16.27 V  
curr1:         0.00 A  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +56.0°C  

nvme-pci-0600
Adapter: PCI adapter
Composite:    +55.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +55.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-4300
Adapter: PCI adapter
Composite:    +49.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +49.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +50.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +57.0°C  

These temperatures appear to be perfectly OK. :+1:

1 Like

Hi again @mzuniga

I’d strongly recommend using a Ventoy USB. It might be easier to create the USB in Windows; following directions from the Ventoy site.

The beauty of a Ventoy USB, is that all that’s needed to boot an ISO file is to copy it to a folder on the Ventoy USB. When you boot the Ventoy USB, any ISOs are automatically listed in the Ventoy menu, and can be booted directly.

I recommend at least an 8GB USB; preferably 16GB or greater, to give you ample space to store several ISOs of your choice.

Copy the appropriate Samsung ISO to the Ventoy USB, and you should be able to boot that directly from the Ventoy menu as well.

I hope this helps. Cheers.

1 Like