Today I had a pretty serious error, the software crashed while I was using it and started to blink the Caps Lock key, I had to do a forced shutdown and when I turned it on it took longer than expected, here I show some records of the moment it happened:
May 08 07:14:26 aaa-80e1 systemd[1]: Starting Network Manager Script Dispatcher Service...
May 08 07:14:26 aaa-80e1 systemd[1]: Started Network Manager Script Dispatcher Service.
May 08 07:14:36 aaa-80e1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 08 07:30:06 aaa-80e1 unix_chkpwd[26969]: password check failed for user (aaa)
May 08 07:30:06 aaa-80e1 i3lock[24898]: pam_unix(i3lock:auth): authentication failure; logname=aaa uid=1000 euid=1000 tty=:0 ruser= rhost= user=aaa
May 08 07:30:19 aaa-80e1 pkexec[27019]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 07:30:19 aaa-80e1 pkexec[27019]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 07:30:19 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'display-brightness-symbolic'
May 08 07:30:19 aaa-80e1 dunst[1079]: CRITICAL: Source ID 41 was not found when attempting to remove it
May 08 07:30:19 aaa-80e1 pkexec[27029]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 07:30:19 aaa-80e1 pkexec[27029]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 07:30:20 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'display-brightness-symbolic'
May 08 07:30:20 aaa-80e1 pkexec[27046]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 07:30:20 aaa-80e1 pkexec[27046]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 07:30:20 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'display-brightness-symbolic'
May 08 07:30:21 aaa-80e1 pkexec[27062]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 07:30:21 aaa-80e1 pkexec[27062]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 07:30:21 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'display-brightness-symbolic'
May 08 07:40:50 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'battery-level-100-charged-symbolic'
May 08 07:40:50 aaa-80e1 dunst[1079]: CRITICAL: Source ID 51 was not found when attempting to remove it
May 08 07:44:25 aaa-80e1 NetworkManager[585]: <info> [1715172265.2833] dhcp4 (wlp1s0): state changed new lease, address=192.168.142.140
May 08 07:44:25 aaa-80e1 systemd[1]: Starting Network Manager Script Dispatcher Service...
May 08 07:44:25 aaa-80e1 systemd[1]: Started Network Manager Script Dispatcher Service.
May 08 07:44:35 aaa-80e1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 08 07:47:44 aaa-80e1 systemd[938]: Starting Virtual filesystem metadata service...
May 08 07:47:44 aaa-80e1 systemd[938]: Started Virtual filesystem metadata service.
May 08 08:14:24 aaa-80e1 NetworkManager[585]: <info> [1715174064.4527] dhcp4 (wlp1s0): state changed new lease, address=192.168.142.140
May 08 08:14:24 aaa-80e1 systemd[1]: Starting Network Manager Script Dispatcher Service...
May 08 08:14:24 aaa-80e1 systemd[1]: Started Network Manager Script Dispatcher Service.
May 08 08:14:34 aaa-80e1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 08 08:29:57 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:29:58 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:30:08 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'battery-level-100-symbolic'
May 08 08:30:08 aaa-80e1 dunst[1079]: CRITICAL: Source ID 389 was not found when attempting to remove it
May 08 08:30:23 aaa-80e1 pkexec[42569]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 08:30:23 aaa-80e1 pkexec[42569]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 08:30:24 aaa-80e1 dunst[1079]: WARNING: No icon found in path: 'display-brightness-symbolic'
May 08 08:30:24 aaa-80e1 dunst[1079]: CRITICAL: Source ID 392 was not found when attempting to remove it
May 08 08:32:46 aaa-80e1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 08 08:32:46 aaa-80e1 kernel: sd 0:0:0:0: [sda] Stopping disk
May 08 08:32:46 aaa-80e1 kernel: ata1.00: Entering standby power mode
May 08 08:32:48 aaa-80e1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 08 08:32:48 aaa-80e1 kernel: ata1.00: Entering active power mode
May 08 08:32:48 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/1:0/0x7fffffff/15285
last function: ata_scsi_dev_rescan
May 08 08:32:48 aaa-80e1 kernel: CPU: 1 PID: 15285 Comm: kworker/1:0 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:32:48 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:32:48 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:32:48 aaa-80e1 kernel: Call Trace:
May 08 08:32:48 aaa-80e1 kernel: <TASK>
May 08 08:32:48 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:32:48 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:32:48 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: </TASK>
May 08 08:32:48 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/1:0/15285/0x00000000
May 08 08:32:48 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:32:48 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:32:48 aaa-80e1 kernel: CPU: 1 PID: 15285 Comm: kworker/1:0 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:32:48 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:32:48 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:32:48 aaa-80e1 kernel: Call Trace:
May 08 08:32:48 aaa-80e1 kernel: <TASK>
May 08 08:32:48 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:32:48 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:32:48 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:32:48 aaa-80e1 kernel: ? ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:32:48 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:32:48 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: </TASK>
May 08 08:32:48 aaa-80e1 kernel: ata1.00: configured for UDMA/133
May 08 08:32:48 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/1:0/0x7fffffff/15285
last function: ata_scsi_dev_rescan
May 08 08:32:48 aaa-80e1 kernel: CPU: 1 PID: 15285 Comm: kworker/1:0 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:32:48 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:32:48 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:32:48 aaa-80e1 kernel: Call Trace:
May 08 08:32:48 aaa-80e1 kernel: <TASK>
May 08 08:32:48 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:32:48 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:32:48 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: </TASK>
May 08 08:32:48 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/1:0/15285/0x00000000
May 08 08:32:48 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:32:48 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:32:48 aaa-80e1 kernel: CPU: 1 PID: 15285 Comm: kworker/1:0 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:32:48 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:32:48 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:32:48 aaa-80e1 kernel: Call Trace:
May 08 08:32:48 aaa-80e1 kernel: <TASK>
May 08 08:32:48 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:32:48 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:32:48 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:32:48 aaa-80e1 kernel: ? ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:32:48 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:32:48 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:32:48 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:32:48 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:32:48 aaa-80e1 kernel: </TASK>
May 08 08:32:48 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:32:48 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:32:48 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:34:06 aaa-80e1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 08 08:34:06 aaa-80e1 kernel: sd 0:0:0:0: [sda] Stopping disk
May 08 08:34:06 aaa-80e1 kernel: ata1.00: Entering standby power mode
May 08 08:34:08 aaa-80e1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 08 08:34:08 aaa-80e1 kernel: ata1.00: Entering active power mode
May 08 08:34:08 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/0:1/0x7fffffff/41525
last function: ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/0:1/41525/0x00000000
May 08 08:34:08 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:34:08 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:34:08 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:34:08 aaa-80e1 kernel: ? ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:34:08 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: ata1.00: configured for UDMA/133
May 08 08:34:08 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/0:1/0x7fffffff/41525
last function: ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/0:1/41525/0x00000000
May 08 08:34:08 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:34:08 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:34:08 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:34:08 aaa-80e1 kernel: ? ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:34:08 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:34:08 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/0:1/0x7fffffff/41525
last function: ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/0:1/41525/0x00000000
May 08 08:34:08 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:34:08 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:34:08 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x57/0x60
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:34:08 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:34:08 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/0:1/0x7fffffff/41525
last function: ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: events ata_scsi_dev_rescan
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: process_one_work+0x300/0x340
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x27b/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/0:1/41525/0x00000000
May 08 08:34:08 aaa-80e1 kernel: Modules linked in: ccm cmac algif_hash algif_skcipher af_alg bnep amdgpu drm_exec amdxcp drm_buddy gpu_sched uvcvideo>
May 08 08:34:08 aaa-80e1 kernel: ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 vivaldi_fmap sdhci_pci crc32c_intel>
May 08 08:34:08 aaa-80e1 kernel: CPU: 0 PID: 41525 Comm: kworker/0:1 Tainted: G W OE 6.6.26-1-MANJARO #1 810ec2d1597099b697461fea57746cd5>
May 08 08:34:08 aaa-80e1 kernel: Hardware name: LENOVO 80E1/Lancer 4B2, BIOS A2CN34WW(V2.02) 02/28/2015
May 08 08:34:08 aaa-80e1 kernel: Workqueue: 0x0 (events)
May 08 08:34:08 aaa-80e1 kernel: Call Trace:
May 08 08:34:08 aaa-80e1 kernel: <TASK>
May 08 08:34:08 aaa-80e1 kernel: dump_stack_lvl+0x47/0x60
May 08 08:34:08 aaa-80e1 kernel: __schedule_bug+0x56/0x70
May 08 08:34:08 aaa-80e1 kernel: __schedule+0x103c/0x1410
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x57/0x60
May 08 08:34:08 aaa-80e1 kernel: ? dump_stack_lvl+0x4c/0x60
May 08 08:34:08 aaa-80e1 kernel: schedule+0x5e/0xd0
May 08 08:34:08 aaa-80e1 kernel: worker_thread+0x19d/0x3a0
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_worker_thread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: kthread+0xe8/0x120
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork+0x34/0x50
May 08 08:34:08 aaa-80e1 kernel: ? __pfx_kthread+0x10/0x10
May 08 08:34:08 aaa-80e1 kernel: ret_from_fork_asm+0x1b/0x30
May 08 08:34:08 aaa-80e1 kernel: </TASK>
May 08 08:34:08 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:34:08 aaa-80e1 kernel: sd 0:0:0:0: [sda] Starting disk
May 08 08:34:53 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:34:53 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:35:02 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:35:02 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:35:06 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:35:06 aaa-80e1 rtkit-daemon[1287]: Supervising 1 threads of 1 processes of 1 users.
May 08 08:35:18 aaa-80e1 pkexec[43920]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 08:35:18 aaa-80e1 pkexec[43920]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
May 08 08:36:24 aaa-80e1 pkexec[44209]: pam_unix(polkit-1:session): session opened for user root(uid=0) by aaa(uid=1000)
May 08 08:36:24 aaa-80e1 pkexec[44209]: aaa: Executing command [USER=root] [TTY=unknown] [CWD=/home/aaa] [COMMAND=/usr/bin/xfpm-power-backlight-helper>
-- Boot dc4234db2b154c46b7c56ef6ab9c7cd8 --
May 08 14:34:16 aaa-80e1 kernel: Linux version 6.6.26-1-MANJARO (builduser@fv-az839-403) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 >
May 08 14:34:16 aaa-80e1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64 root=UUID=e1dcd096-1707-4bc3-b652-365351f808f8 rw quiet apparmor=1 >
May 08 14:34:16 aaa-80e1 kernel: BIOS-provided physical RAM map:
May 08 14:34:16 aaa-80e1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
May 08 14:34:16 aaa-80e1 kernel: BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff] reserved
May 08 14:34:16 aaa-80e1 kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
May 08 14:34:16 aaa-80e1 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000009a0bbfff] usable
I’m pretty sure it indicates a kernel panic at least.
This can be tied to a hardware fault of some kind, but it does not necessarily equate to one. I might even say that actually failing hardware is less likely on the whole when compared to simple misconfiguration.
Intresting how many people all had this error, but didn’t responded to my Topic… i would bet that 30-40% of the community would had this error messages, but never checked their journals.
While, as you said, we really need @AAA_AAA to post the output of inxi -Fazy, I don’t think it’s an Intel CPU. Searching for LENOVO 80E1/Lancer 4B2 (from the logs) suggests an AMD CPU - quite an old one, at that.
Also for @AAA_AAA: As well as inxi -Fazy, it may also be worth the output from smartctl --all /dev/sda (or your actual disk drive if it’s not at /dev/sda).
So your workload wasn’t unique and you didn’t update your system recently?
Your Kernel version looks like the stable release to me, so normally the last kernel update was 1month ago in early april.
If there was no unique workload or updates… the first problem’s could be temps check them while you doing your task’s but for sure it could also be disk problem’s.
Can you describe with more details, what you mentioned about the slowed boot progress after you had to shutdown your Laptop?
Longer blackscreen or did it stuck for a while on the Bios Logo?Around the Hardware Initialisation Screen where you see your Bios date.
Edit: You can remove your double inxi post, one time is enough
Did you use inxi while your system is idle? Because 58° on CPU/GPU looks pretty hot for a idle system. The Summer time just started… maybe you need to refresh the Heatpaste or Clean the Dust for better cooling.
Given the symptoms, it’s likely to be running an fsck of some description (i.e. a crash in a drive related function).
@AAA_AAA Well, I did rather assume that you would install the smartmontools package, home of smartctl, before running the command. It’s a tool for interrogating the SMART diagnostic info on drives, which may be relevant to what you have. Although I would agree with @Kobold that if your system is idling at 58°, that’s too hot. Given the age of the system, it may be worth checking the thermal paste on the CPU and reapplying if necessary.
I check for updates almost every day.
I use those applications all week for over a month, I had put it in hibernation, but I do it many times, today I was just using vscode and firefox when the error happened, everything froze at 8:34 a.m., I waited an hour and it did not respond and I turned it off.
After 2 p.m. I turned it on and first the lenovo logo appeared, it stayed there for a while and then the forced shutdown recovery appeared, the location of the disk /dev/sda appears… and then it started normally.
So since you on stable there should be no updates for a long time now, if you didn’t modify your system… it should be hardware related and no Linux problem.
FSCK Filesystem scan, best way in Lifeboot:
sudo fsck -f -y /dev/sdXX (-f Forcescan -y always yes to all questions) (sdXX Replace XX with your unmounted drive that needs to be scanned)
Edit: I also recommend to check your system error’s from time to time, specially after a bigger release update.
systemctl --failed journalctl -p 3 -xb
I also recommend to activate the bootchecklist from Linux, when you remove quiet from grub. Don’t forget sudo update grub after your changes
sudo smartctl --all /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.26-1-MANJARO] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Phison Driven SSDs
Device Model: PNY CS900 480GB SSD
Serial Number: PNY4920229810040DEBD
LU WWN Device Id: 5 f8db4c 49200debd
Firmware Version: CS900KA3
User Capacity: 480,103,981,056 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed May 8 17:35:27 2024 -05
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (65535) seconds.
Offline data collection
capabilities: (0x79) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 30) minutes.
Conveyance self-test routine
recommended polling time: ( 6) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 2175
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 1040
168 SATA_Phy_Error_Count 0x0012 100 100 000 Old_age Always - 0
170 Bad_Blk_Ct_Lat/Erl 0x0003 091 091 010 Pre-fail Always - 0/92
173 MaxAvgErase_Ct 0x0012 100 100 000 Old_age Always - 55 (Average 44)
192 Unsafe_Shutdown_Count 0x0012 100 100 000 Old_age Always - 442
194 Temperature_Celsius 0x0023 067 067 000 Pre-fail Always - 33 (Min/Max 33/33)
218 CRC_Error_Count 0x000b 100 100 050 Pre-fail Always - 0
231 SSD_Life_Left 0x0013 100 100 000 Pre-fail Always - 95
241 Lifetime_Writes_GiB 0x0012 100 100 000 Old_age Always - 5440
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
The above only provides legacy SMART information - try 'smartctl -x' for more
systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
journalctl -p 3 -xb
May 08 16:12:10 aaa-80e1 kernel: __common_interrupt: 1.55 No irq handler for vector
May 08 16:12:13 aaa-80e1 kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
May 08 16:12:19 aaa-80e1 kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 0
May 08 16:12:22 aaa-80e1 bluetoothd[590]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to clear UUIDs: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to set mode: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:35 aaa-80e1 bluetoothd[590]: Failed to add UUID: Failed (0x03)
May 08 16:12:41 aaa-80e1 dbus-broker-launch[829]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share/dbus-1/services/>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
May 08 16:13:45 aaa-80e1 lightdm[899]: gkr-pam: unable to locate daemon control file
May 08 16:13:47 aaa-80e1 dbus-broker-launch[940]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share/dbus-1/services/>
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░
░░ A service file is a ini-type configuration file.
░░
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
May 08 16:15:21 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/1:3/0x7fffffff/115
last function: ata_scsi_dev_rescan
May 08 16:15:21 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/1:3/115/0x00000000
May 08 16:15:21 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/1:3/0x7fffffff/115
last function: ata_scsi_dev_rescan
May 08 16:15:21 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/1:3/115/0x00000000
May 08 16:15:21 aaa-80e1 kernel: BUG: workqueue leaked lock or atomic: kworker/1:3/0x7fffffff/115
last function: ata_scsi_dev_rescan
May 08 16:15:21 aaa-80e1 kernel: BUG: scheduling while atomic: kworker/1:3/115/0x00000000
May 08 16:27:58 aaa-80e1 systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)!
May 08 16:28:27 aaa-80e1 kernel: INFO: task systemd-udevd:193 blocked for more than 122 seconds.
May 08 16:28:27 aaa-80e1 kernel: Tainted: G W OE 6.6.26-1-MANJARO #1
May 08 16:28:27 aaa-80e1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 08 16:30:30 aaa-80e1 kernel: INFO: task systemd-udevd:193 blocked for more than 245 seconds.
May 08 16:30:30 aaa-80e1 kernel: Tainted: G W OE 6.6.26-1-MANJARO #1
May 08 16:30:30 aaa-80e1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 08 16:32:33 aaa-80e1 kernel: INFO: task systemd-udevd:193 blocked for more than 368 seconds.
May 08 16:32:33 aaa-80e1 kernel: Tainted: G W OE 6.6.26-1-MANJARO #1
May 08 16:32:33 aaa-80e1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 08 16:34:36 aaa-80e1 kernel: INFO: task systemd-udevd:193 blocked for more than 491 seconds.
May 08 16:34:36 aaa-80e1 kernel: Tainted: G W OE 6.6.26-1-MANJARO #1
May 08 16:34:36 aaa-80e1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 08 16:36:39 aaa-80e1 kernel: INFO: task systemd-udevd:193 blocked for more than 614 seconds.
May 08 16:36:39 aaa-80e1 kernel: Tainted: G W OE 6.6.26-1-MANJARO #1
May 08 16:36:39 aaa-80e1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
sudo fsck -f -y/dev/sda1
fsck from util-linux 2.39.2
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 787307 extent tree (at level 1) could be shorter. Optimize? yes
Inode 18351013 extent tree (at level 1) could be narrower. Optimize? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
dev/sda1: 595298/28729344 files (1.0% non-contiguous), 17239502/114905124 blocks
/ manjaro@manjaro-13 ~]$
I don’t think the sensors are a problem, I used to reach temperatures of 80°, 90° and even 100° but I found the problem was Chromium. But I will check the thermal paste
There is no way it should be operating at 100° - that’s at “hazard” levels if it’s in a laptop (i.e. near a battery and human hands, neither of which appreciate being near something at boiling temperatures). I can’t find a definitive source for the hard limit, but a somewhat squishy source suggests a max operating temperature of 90° - which is still, frankly, far too high for a laptop. Some old reviews mention laptops with the same processor maxing out at a temperature of 60°.
So either a faulty temperature sensor or an urgent check of the cooling solution is required.
Cooling, or lack thereof, seems to be a factor. Is the machine well ventilated while it’s operational? Using it on a flat surface, for example, has been known to severely limit airflow; especially for older laptops with vents primarily situated on the underside of the machine. As you might imagine, using a laptop on a blanket (as an example) is not a great idea.
There are stands available; designed to increase airflow; perhaps this is an option to consider. Another often ignored possibility is that the fan(s) might need some cleaning.
I’m guessing here, and haven’t looked up the specs, however, shutdown temperatures can sometimes be adjusted in BIOS. Is it possible the BIOS has reset recently?
Perhaps the sensors are bad, perhaps not - I’d probably lean towards not (those sensors should be on the CPU die itself, and that’s less likely to be bad, I think).
That being said, I’m sure you’ll enjoy the laptop experience when you have more than one physical core . Kudos on keeping the machine going this long.