Random freezes, how to troubleshoot

The problem

I’ve been using Manjaro KDE for a few months and from time to time I still experience random freezes.
Sometimes it happens as I am using the system, for example the browser and suddenly it gets stuck, can’t move the mouse, no keyboard response and I have to reset the PC.
And sometimes it happens while the PC is sleeping (PC still on, just the screen turned off automatically after some minutes).

What I have tried so far

Logs

So first I tried looking at the logs with:
journalctl -b -1
Next time I boot after a freeze.
But I don’t see anything interesting. I’ve tried a couple times and from the dates and the error messages it seems like the error is not saving anything to the log file.

REISUB

Next thing I tried was enabling something in the Grub to be able to Alt+PrintScreen REISUB next time it happens, hoping this would allow me to get to a terminal instead of hard resetting.
It didn’t work. I mean the command works, but not when the system freezes.

Kernel update

I tried also to update and use a new Kernel with the GUI utility, just to see if that would help, but the other day it happened again so no luck.
Now using 5.15.2-2 (5.13.19-2 before)

What else should I try?

Are there any other logs I can check? Do I have to enable more verbose logs maybe? Is it normal that the REISUB command doesn’t work?
I have no swap configured, should I create a swap file?

Also let me know if I can provide any useful information.

Thank you!!!

I’ve created a 4GB swap partition just in case.
Will see if it crashes again in the next few days or weeks.

It just happened again. At 11:36:22 the UI froze. I could still move the mouse surprisingly, for a few more seconds, although nothing was responsive really. It then got stuck too.
I was just browsing the internet, Firefox was the only application running.
The logs:

dic 10 11:35:41 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:35:41 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:36:06 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:36:06 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:36:08 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:36:08 thebronx rtkit-daemon[1581]: Supervising 10 threads of 7 processes of 1 users.
dic 10 11:36:28 thebronx kernel: [drm] Fence fallback timer expired on ring sdma0
dic 10 11:36:29 thebronx rtkit-daemon[1581]: The canary thread is apparently starving. Taking action.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Demoting known real-time threads.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 5192 of process 3047.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 5128 of process 4782.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 3955 of process 2185.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 3949 of process 2082.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 3792 of process 3452.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 1941 of process 1736.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 1675 of process 1535.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 1663 of process 1535.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 1648 of process 1535.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Successfully demoted thread 1535 of process 1535.
dic 10 11:36:29 thebronx rtkit-daemon[1581]: Demoted 10 threads.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: The canary thread is apparently starving. Taking action.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Demoting known real-time threads.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 5192 of process 3047.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 5128 of process 4782.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 3955 of process 2185.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 3949 of process 2082.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 3792 of process 3452.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 1941 of process 1736.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 1675 of process 1535.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 1663 of process 1535.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 1648 of process 1535.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Successfully demoted thread 1535 of process 1535.
dic 10 11:36:39 thebronx rtkit-daemon[1581]: Demoted 10 threads.
dic 10 11:36:42 thebronx kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
dic 10 11:36:42 thebronx kernel: [drm:drm_atomic_helper_wait_for_flip_done] *ERROR* [CRTC:77:crtc-0] flip_done timed out
dic 10 11:36:49 thebronx rtkit-daemon[1581]: The canary thread is apparently starving. Taking action.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Demoting known real-time threads.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 5192 of process 3047.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 5128 of process 4782.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 3955 of process 2185.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 3949 of process 2082.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 3792 of process 3452.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 1941 of process 1736.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 1675 of process 1535.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 1663 of process 1535.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 1648 of process 1535.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Successfully demoted thread 1535 of process 1535.
dic 10 11:36:49 thebronx rtkit-daemon[1581]: Demoted 10 threads.
dic 10 11:36:50 thebronx kernel: sysrq: Keyboard mode set to system default
dic 10 11:36:50 thebronx systemd-journald[337]: Journal stopped

Looks like I am not alone: System frequently crashing after GPU drivers update
And the bug report: [5.2/5.3][drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted! (#934) · Issues · drm / amd

Unfortunately that bug was reported 2 years ago and the only workaround is to downgrade linux-firmware to 20210818.c46b8c3-1 with:

sudo downgrade --ala-only linux-firmware

If you don’t have downgrade installed: Downgrading packages - Manjaro

I am sad, but I guess I will have to try and downgrade, hopefully nothing breaks.

Currently using:

$ pacman -Qs linux-firmware
local/linux-firmware 20211027.1d00989-1
    Firmware files for Linux
1 Like

It crashed again after downgrading linux-firmware.
Using 20210818 version:

pacman -Qs linux-firmware
local/linux-firmware 20210818.c46b8c3-1
    Firmware files for Linux

The log shows nothing from the crash (it happened at 00:00:22 while using Firefox again), I don’t see anything relevant:

dic 14 23:26:14 thebronx kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7750, resource id: 60817467, major code: 18 (ChangeProperty), minor code: 0
dic 14 23:43:24 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:24 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:55 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:55 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:55 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:55 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:43:56 thebronx rtkit-daemon[1617]: Successfully made thread 11475 of process 10206 owned by '1000' RT at priority 10.
dic 14 23:43:56 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:43:56 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:43:56 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:56:06 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:06 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:11 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:11 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:17 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:17 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Supervising 13 threads of 8 processes of 1 users.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Successfully made thread 11792 of process 11481 owned by '1000' RT at priority 10.
dic 14 23:56:39 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:59:36 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:59:36 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:59:39 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.
dic 14 23:59:39 thebronx rtkit-daemon[1617]: Supervising 14 threads of 9 processes of 1 users.

So, back to where I started I guess, still no clue what is going on and no idea how to troubleshoot this. It is starting to annoy me.

I have removed the linux-firmware ignore line from /etc/pacman.conf and updated again to revert the downgrade as that was completely useless.

New crash, the one that leaves the cursor “working” while everything else is frozen and then in like 30 seconds the cursor gets stuck too:

dic 18 12:22:48 thebronx systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
dic 18 12:22:48 thebronx systemd[1]: Finished Cleanup of Temporary Directories.
dic 18 12:22:48 thebronx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 18 12:22:48 thebronx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 18 12:22:48 thebronx kernel: audit: type=1130 audit(1639826568.100:166): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 18 12:22:48 thebronx kernel: audit: type=1131 audit(1639826568.103:167): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 18 12:23:53 thebronx kernel: watchdog: BUG: soft lockup - CPU#7 stuck for 26s! [TaskCon~ller #3:1810]
dic 18 12:23:53 thebronx kernel: Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc overlay snd_usb_audio uvcvideo videobuf2_vmalloc videobuf2_memops >
dic 18 12:23:53 thebronx kernel:  soundcore vfat rfkill fat wmi mac_hid gpio_amdpt pinctrl_amd gpio_generic acpi_cpufreq squashfs uinput loop ipmi_devintf ipmi_msghandler sg fuse crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 crc32c_intel xhci_pci
dic 18 12:23:53 thebronx kernel: CPU: 7 PID: 1810 Comm: TaskCon~ller #3 Tainted: G           OE     5.15.7-1-MANJARO #1 89d91431fe07b9fd339e5f86d7a009210c48fcc6
dic 18 12:23:53 thebronx kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350 Pro4, BIOS P4.90 06/14/2018
dic 18 12:23:53 thebronx kernel: RIP: 0010:smp_call_function_many_cond+0x127/0x300
dic 18 12:23:53 thebronx kernel: Code: e8 ee 1e 43 00 3b 05 fc 98 ca 01 89 c7 73 22 48 63 c7 49 8b 4d 00 48 03 0c c5 c0 9a b6 bc 8b 41 08 a8 01 74 0a f3 90 8b 51 08 <83> e2 01 75 f6 eb cc 48 83 c4 48 5b 5d 41 5c 41 5d 41 5e 41 5f 31
dic 18 12:23:53 thebronx kernel: RSP: 0018:ffffae12c23dfb98 EFLAGS: 00000202
dic 18 12:23:53 thebronx kernel: RAX: 0000000000000011 RBX: 0000000000000001 RCX: ffff9e464ee38a20
dic 18 12:23:53 thebronx kernel: RDX: 0000000000000011 RSI: 0000000000000000 RDI: 0000000000000000
dic 18 12:23:53 thebronx kernel: RBP: ffff9e464eff2888 R08: 0000000000000000 R09: 0000000000000000
dic 18 12:23:53 thebronx kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9e464eff10c0
dic 18 12:23:53 thebronx kernel: R13: ffff9e464eff2880 R14: ffff9e464eff2880 R15: ffff9e464eff2888
dic 18 12:23:53 thebronx kernel: FS:  00007fb366c18640(0000) GS:ffff9e464efc0000(0000) knlGS:0000000000000000
dic 18 12:23:53 thebronx kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
dic 18 12:23:53 thebronx kernel: CR2: 00007fb36e1d1b60 CR3: 00000001520fc000 CR4: 00000000003506e0
dic 18 12:23:53 thebronx kernel: Call Trace:
dic 18 12:23:53 thebronx kernel:  <TASK>
dic 18 12:23:53 thebronx kernel:  ? switch_mm+0x40/0x40
dic 18 12:23:53 thebronx kernel:  on_each_cpu_cond_mask+0x20/0x50
dic 18 12:23:53 thebronx kernel:  flush_tlb_mm_range+0xe8/0x130
dic 18 12:23:53 thebronx kernel:  tlb_finish_mmu+0x120/0x1b0
dic 18 12:23:53 thebronx kernel:  unmap_region+0xe8/0x130
dic 18 12:23:53 thebronx kernel:  __do_munmap+0x200/0x4f0
dic 18 12:23:53 thebronx kernel:  mmap_region+0x2e7/0x640
dic 18 12:23:53 thebronx kernel:  do_mmap+0x370/0x560
dic 18 12:23:53 thebronx kernel:  ? security_mmap_file+0x81/0xc0
dic 18 12:23:53 thebronx kernel:  vm_mmap_pgoff+0xf0/0x190
dic 18 12:23:53 thebronx kernel:  ksys_mmap_pgoff+0x5f/0x240
dic 18 12:23:53 thebronx kernel:  do_syscall_64+0x5c/0x90
dic 18 12:23:53 thebronx kernel:  ? syscall_exit_to_user_mode+0x23/0x50
dic 18 12:23:53 thebronx kernel:  ? do_syscall_64+0x69/0x90
dic 18 12:23:53 thebronx kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
dic 18 12:23:53 thebronx kernel: RIP: 0033:0x7fb38cf9218d
dic 18 12:23:53 thebronx kernel: Code: b4 0c 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 6c 0c 00 f7 d8 64 89 01 48
dic 18 12:23:53 thebronx kernel: RSP: 002b:00007fb366c179d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
dic 18 12:23:53 thebronx kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb38cf9218d
dic 18 12:23:53 thebronx kernel: RDX: 0000000000000000 RSI: 0000000000500000 RDI: 00007fb30d000000
dic 18 12:23:53 thebronx kernel: RBP: 0000000000000029 R08: 00000000ffffffff R09: 0000000000000000
dic 18 12:23:53 thebronx kernel: R10: 0000000000000032 R11: 0000000000000246 R12: 00007fb30d000000
dic 18 12:23:53 thebronx kernel: R13: 0000000000000002 R14: 0000000000500000 R15: 0000000000000003
dic 18 12:23:53 thebronx kernel:  </TASK>
dic 18 12:24:21 thebronx kernel: watchdog: BUG: soft lockup - CPU#7 stuck for 52s! [TaskCon~ller #3:1810]

Great, two crashes today, at 20:01:09 the screen froze:

dic 18 20:01:01 thebronx CROND[15749]: (root) CMD (run-parts /etc/cron.hourly)
dic 18 20:01:01 thebronx CROND[15748]: (root) CMDEND (run-parts /etc/cron.hourly)
dic 18 20:01:16 thebronx rtkit-daemon[1635]: The canary thread is apparently starving. Taking action.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Demoting known real-time threads.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 14865 of process 14558.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 14812 of process 14555.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 14293 of process 13207.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 13749 of process 13175.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 12582 of process 11579.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 12570 of process 11642.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 11450 of process 11256.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 9019 of process 9016.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 9016 of process 9016.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 9018 of process 9017.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 9017 of process 9017.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 8971 of process 1583.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 1720 of process 1583.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 1711 of process 1583.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Successfully demoted thread 1583 of process 1583.
dic 18 20:01:16 thebronx rtkit-daemon[1635]: Demoted 15 threads.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: The canary thread is apparently starving. Taking action.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Demoting known real-time threads.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 14865 of process 14558.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 14812 of process 14555.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 14293 of process 13207.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 13749 of process 13175.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 12582 of process 11579.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 12570 of process 11642.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 11450 of process 11256.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 9019 of process 9016.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 9016 of process 9016.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 9018 of process 9017.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 9017 of process 9017.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 8971 of process 1583.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 1720 of process 1583.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 1711 of process 1583.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Successfully demoted thread 1583 of process 1583.
dic 18 20:01:26 thebronx rtkit-daemon[1635]: Demoted 15 threads.
dic 18 20:01:31 thebronx kernel: sysrq: Keyboard mode set to system default
dic 18 20:01:32 thebronx systemd-journald[371]: Journal stopped

What about trying a different kernel (older LTS) like 5.10 ?
This is the most stable kernel i had in a long time.

1 Like

I will try 5.10.84-1, since that is the one that the Kernel UI has listed and it is pretty easy to switch to.

It crashed again, while using the LTS kernel.
This time I wasn’t even using the PC, I left it there and when I came back it was stuck in the login screen, with the time stuck at 14:54
The log when that happened:

dic 21 14:35:48 thebronx anacron[850]: Job `cron.daily' started
dic 21 14:35:48 thebronx anacron[850]: Job `cron.daily' terminated
dic 21 14:35:48 thebronx anacron[850]: Normal exit (1 job run)
dic 21 14:55:31 thebronx systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)!
dic 21 14:55:31 thebronx kernel: audit: type=1701 audit(1640094931.765:170): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=491 comm="systemd-logind" exe="/usr/lib/systemd/systemd-logind" sig=6 res=1
dic 21 14:55:31 thebronx audit[491]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=491 comm="systemd-logind" exe="/usr/lib/systemd/systemd-logind" sig=6 res=1
dic 21 14:55:31 thebronx systemd[1]: systemd-logind.service: Killing process 491 (systemd-logind) with signal SIGABRT.
dic 21 14:55:31 thebronx systemd[1]: Created slice Slice /system/systemd-coredump.
dic 21 14:55:57 thebronx kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd:1]
dic 21 14:55:57 thebronx kernel: Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc overlay uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2>
dic 21 14:55:57 thebronx kernel:  snd_pcm cec crypto_simd cryptd snd_timer syscopyarea glue_helper sysfillrect r8168(OE) sp5100_tco rfkill sysimgblt rapl snd k10temp fb_sys_fops i2c_piix4 soundcore libarc4 pcspkr wmi pinctrl_amd squashfs gpio_amdpt gpio_generic mac_hid acpi_cpufreq uinput loop drm ipmi_devint>
dic 21 14:55:57 thebronx kernel: CPU: 2 PID: 1 Comm: systemd Tainted: G           OE     5.10.84-1-MANJARO #1
dic 21 14:55:57 thebronx kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350 Pro4, BIOS P4.90 06/14/2018
dic 21 14:55:57 thebronx kernel: RIP: 0010:smp_call_function_many_cond+0x295/0x2e0
dic 21 14:55:57 thebronx kernel: Code: 89 fe e8 3e 6e 3d 00 3b 05 fc 5e ac 01 89 c7 0f 83 fd fd ff ff 48 63 c7 49 8b 0e 48 03 0c c5 00 69 03 9b 8b 41 08 a8 01 74 0a <f3> 90 8b 51 08 83 e2 01 75 f6 eb c9 48 c7 c2 e0 b5 7f 9b 4c 89 ee
dic 21 14:55:57 thebronx kernel: RSP: 0018:ffffa87440037af8 EFLAGS: 00000202
dic 21 14:55:57 thebronx kernel: RAX: 0000000000000011 RBX: ffff95d84ecb5270 RCX: ffff95d84ed3b1a0
dic 21 14:55:57 thebronx kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000004
dic 21 14:55:57 thebronx kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000004
dic 21 14:55:57 thebronx kernel: R10: ffff95d84ecb5248 R11: 0000000000000005 R12: 0000000000000000
dic 21 14:55:57 thebronx kernel: R13: 0000000000000140 R14: ffff95d84ecb5240 R15: ffff95d84ecb5248
dic 21 14:55:57 thebronx kernel: FS:  00007fe9e15b9380(0000) GS:ffff95d84ec80000(0000) knlGS:0000000000000000
dic 21 14:55:57 thebronx kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
dic 21 14:55:57 thebronx kernel: CR2: 000055de0054f000 CR3: 0000000106716000 CR4: 00000000003506e0
dic 21 14:55:57 thebronx kernel: Call Trace:
dic 21 14:55:57 thebronx kernel:  ? __flush_tlb_all+0x40/0x40
dic 21 14:55:57 thebronx kernel:  ? __flush_tlb_all+0x40/0x40
dic 21 14:55:57 thebronx kernel:  on_each_cpu+0x39/0x90

And then for around half an hour there is a lot of errors like “CPU#X stuck”:

dic 21 14:56:25 thebronx kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [systemd:1]
...
dic 21 14:56:31 thebronx kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
dic 21 14:56:31 thebronx kernel: rcu:         2-....: (17999 ticks this GP) idle=cde/1/0x4000000000000000 softirq=62944/62944 fqs=5989 last_accelerate: aecc/f521 dyntick_enabled: 1
...
dic 21 14:56:57 thebronx kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd:1]
...
...
...
dic 21 15:27:53 thebronx kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:3:1317]

And as I was writing this message it froze again:

dic 21 18:12:22 thebronx systemd[1318]: Started Firefox - Navegador web.
dic 21 18:12:22 thebronx plasmashell[1466]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:377: Unable to assign [undefined] to QString
dic 21 18:12:22 thebronx dbus-daemon[1341]: [session uid=1000 pid=1341] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.51' (uid=1000 pid=2009 comm="/usr/lib/firefox/firefox ")
dic 21 18:12:22 thebronx systemd[1318]: Starting Accessibility services bus...
dic 21 18:12:22 thebronx dbus-daemon[1341]: [session uid=1000 pid=1341] Successfully activated service 'org.a11y.Bus'
dic 21 18:12:22 thebronx systemd[1318]: Started Accessibility services bus.
dic 21 18:12:22 thebronx at-spi-bus-launcher[2153]: dbus-daemon[2153]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1331 comm="/usr/bin/kwalletd5 --pam-login 7 8 ")
dic 21 18:12:22 thebronx at-spi-bus-launcher[2153]: dbus-daemon[2153]: Successfully activated service 'org.a11y.atspi.Registry'
dic 21 18:12:22 thebronx at-spi-bus-launcher[2155]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 4 threads of 1 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Successfully made thread 2203 of process 2009 owned by '1000' RT at priority 10.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx kwin_x11[1401]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28417, resource id: 16783069, major code: 3 (GetWindowAttributes), minor code: 0
dic 21 18:12:23 thebronx kwin_x11[1401]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28418, resource id: 16783069, major code: 14 (GetGeometry), minor code: 0
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:23 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:24 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:25 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:25 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:27 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:27 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:28 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:28 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:31 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:31 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:31 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:31 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Supervising 5 threads of 2 processes of 1 users.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Successfully made thread 2820 of process 2659 owned by '1000' RT at priority 10.
dic 21 18:12:35 thebronx rtkit-daemon[1549]: Supervising 6 threads of 3 processes of 1 users.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: The canary thread is apparently starving. Taking action.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Demoting known real-time threads.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 2820 of process 2659.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 2203 of process 2009.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 1631 of process 1518.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 1630 of process 1518.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 1628 of process 1518.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Successfully demoted thread 1518 of process 1518.
dic 21 18:13:20 thebronx rtkit-daemon[1549]: Demoted 6 threads.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: The canary thread is apparently starving. Taking action.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Demoting known real-time threads.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 2820 of process 2659.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 2203 of process 2009.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 1631 of process 1518.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 1630 of process 1518.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 1628 of process 1518.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Successfully demoted thread 1518 of process 1518.
dic 21 18:13:30 thebronx rtkit-daemon[1549]: Demoted 6 threads.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: The canary thread is apparently starving. Taking action.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Demoting known real-time threads.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 2820 of process 2659.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 2203 of process 2009.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 1631 of process 1518.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 1630 of process 1518.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 1628 of process 1518.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Successfully demoted thread 1518 of process 1518.
dic 21 18:13:40 thebronx rtkit-daemon[1549]: Demoted 6 threads.
dic 21 18:13:40 thebronx kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [TaskCon~ller #6:2068]
dic 21 18:13:40 thebronx kernel: Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc overlay uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2>
dic 21 18:13:40 thebronx kernel:  cryptd syscopyarea vfat glue_helper sysfillrect cfg80211 fat rapl ccp snd sp5100_tco sysimgblt r8168(OE) rfkill pcspkr k10temp soundcore i2c_piix4 rng_core fb_sys_fops libarc4 wmi squashfs pinctrl_amd gpio_amdpt mac_hid gpio_generic acpi_cpufreq uinput loop drm ipmi_devintf i>
dic 21 18:13:40 thebronx kernel: CPU: 4 PID: 2068 Comm: TaskCon~ller #6 Tainted: G           OE     5.10.84-1-MANJARO #1
dic 21 18:13:40 thebronx kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350 Pro4, BIOS P4.90 06/14/2018
dic 21 18:13:40 thebronx kernel: RIP: 0010:smp_call_function_many_cond+0x295/0x2e0
dic 21 18:13:40 thebronx kernel: Code: 89 fe e8 3e 6e 3d 00 3b 05 fc 5e ac 01 89 c7 0f 83 fd fd ff ff 48 63 c7 49 8b 0e 48 03 0c c5 00 69 c3 b6 8b 41 08 a8 01 74 0a <f3> 90 8b 51 08 83 e2 01 75 f6 eb c9 48 c7 c2 e0 b5 3f b7 4c 89 ee
dic 21 18:13:40 thebronx kernel: RSP: 0018:ffffb6b20808fc40 EFLAGS: 00000202
dic 21 18:13:40 thebronx kernel: RAX: 0000000000000011 RBX: ffff9b7f4ed35270 RCX: ffff9b7f4ec3b1e0
dic 21 18:13:40 thebronx kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000000
dic 21 18:13:40 thebronx kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
dic 21 18:13:40 thebronx kernel: R10: ffff9b7f4ed35248 R11: 0000000000000005 R12: ffff9b7f4ed33b80
dic 21 18:13:40 thebronx kernel: R13: 0000000000000140 R14: ffff9b7f4ed35240 R15: ffff9b7f4ed35248
dic 21 18:13:40 thebronx kernel: FS:  00007f50eb51b640(0000) GS:ffff9b7f4ed00000(0000) knlGS:0000000000000000
dic 21 18:13:40 thebronx kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
dic 21 18:13:40 thebronx kernel: CR2: 00007fc1497f1000 CR3: 000000017af28000 CR4: 00000000003506e0
dic 21 18:13:40 thebronx kernel: Call Trace:
dic 21 18:13:40 thebronx kernel:  ? flush_tlb_func_common.constprop.0+0x260/0x260
dic 21 18:13:40 thebronx kernel:  flush_tlb_mm_range+0xe7/0x120
dic 21 18:13:40 thebronx kernel:  tlb_finish_mmu+0x113/0x1d0
dic 21 18:13:40 thebronx kernel:  unmap_region+0xde/0x110
dic 21 18:13:40 thebronx kernel:  __do_munmap+0x278/0x4e0
dic 21 18:13:40 thebronx kernel:  mmap_region+0x2d6/0x6a0
dic 21 18:13:40 thebronx kernel:  do_mmap+0x45c/0x570
dic 21 18:13:40 thebronx kernel:  ? security_mmap_file+0x81/0xb0
dic 21 18:13:40 thebronx kernel:  vm_mmap_pgoff+0xd3/0x120
dic 21 18:13:40 thebronx kernel:  do_syscall_64+0x33/0x40
dic 21 18:13:40 thebronx kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
dic 21 18:13:40 thebronx kernel: RIP: 0033:0x7f5111dec18d
dic 21 18:13:40 thebronx kernel: Code: b4 0c 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 6c 0c 00 f7 d8 64 89 01 48
dic 21 18:13:40 thebronx kernel: RSP: 002b:00007f50eb51a9d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
dic 21 18:13:40 thebronx kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f5111dec18d
dic 21 18:13:40 thebronx kernel: RDX: 0000000000000000 RSI: 0000000000300000 RDI: 00007f50cca00000
dic 21 18:13:40 thebronx kernel: RBP: 0000000000000029 R08: 00000000ffffffff R09: 0000000000000000
dic 21 18:13:40 thebronx kernel: R10: 0000000000000032 R11: 0000000000000246 R12: 00007f50cca00000
dic 21 18:13:40 thebronx kernel: R13: 0000000000000001 R14: 0000000000300000 R15: 0000000000000003
dic 21 18:13:50 thebronx rtkit-daemon[1549]: The canary thread is apparently starving. Taking action.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Demoting known real-time threads.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 2820 of process 2659.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 2203 of process 2009.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 1631 of process 1518.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 1630 of process 1518.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 1628 of process 1518.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Successfully demoted thread 1518 of process 1518.
dic 21 18:13:50 thebronx rtkit-daemon[1549]: Demoted 6 threads.

I went back to the latest kernel but I think I will have to switch to a different distro or something, this is pretty unstable.

Greetings. Being a newbie to Linux myself there’s little I can do to directly address your problem. But seeing how little reaction you’ve gotten makes me wonder if there’s just not enough info for folks to go on to be of meaningful assistance.

Can you share info about your hardware system and configuration? Perhaps an inxi -Fazy dump?

Have you had similar crashes with other operating systems using this same hardware? Alternatively, is this the only Manjaro installation you have? … if not, are you experiencing crashes on your other installations?

Since most of us (almost all?) are not constantly crashing, there’s certainly something unique going on with your hardware as it reacts to the Manjaro software - and whatever it is, it isn’t widespread enough to provide a readily identifiable conflict (yet).

:vulcan_salute:

1 Like

Hey, thank you @SomeGuy for the help! Yeah, I mostly wanted to know if there was a way to get more details about the crashes, cause even though I am no expert the logs had very little or no info at all.
So I knew it was not going to be easy.

But regarding your questions, I had used Ubuntu before, can’t remember exactly but probably 20.04 LTS. I tried Kubuntu too, cause I prefer KDE but that was really buggy. So mostly Ubuntu and it crashed sometimes but way less frequently. To the point I never really cared that much.
Hardware was almost identical. Only difference is the KVM USB switch that I have now. Everything else I had already. Mouse has changed but yesterday it was being used by the laptop, not the PC when it crashed so…
Graphics card has been upgraded recently, but Manjaro was crashing with the old one too so I don’t think that was the problem.

I do have Windows installed too, mostly for gaming but I don’t use it that much. But when I use it it’s fine, or as fine as windows can be hehe. So, no crashes.

I will paste the output from inxi -Fazy at the end. Most of the hardware is pretty normal I would say. And the things that could be a bit special like a bluetooth usb and the network card are disabled all the time. They are connected but wifi is disabled, bluetooth is disabled. I have removed the bluetooth thingy for now anyways, see how long it takes before the next crash.
Also I have removed all the plasmoids? widgets? that I had on the desktop with the CPU/GPU/network/disk usage graphs. Would be surprising if those actually could freeze the entire system I guess, but at this point I am just getting rid of everything I can think of before I give up on Manjaro.

I could try and physically remove the network card too, as I don’t use it.
And also the KVM USB switch but that would be a pain in the ass, having to connect keyboard, mouse and webcam to the laptop and back every single day…

System:
  Kernel: 5.15.7-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=63a90eaa-1325-4dae-8428-9feb978e9dbd rw quiet apparmor=1
    security=apparmor udev.log_priority=3 sysrq_always_enabled=1
  Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: AB350 Pro4 serial: <superuser required>
    UEFI: American Megatrends v: P4.90 date: 06/14/2018
CPU:
  Info: model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen
    family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001137
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1671 high: 3383 min/max: 1550/3200 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1376 2: 1445
    3: 3383 4: 2878 5: 1356 6: 1392 7: 1374 8: 1372 9: 1373 10: 1371 11: 1373
    12: 1369 bogomips: 76668
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
    disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Gigabyte
    driver: amdgpu v: kernel bus-ID: 28:00.0 chip-ID: 1002:73bf class-ID: 0300
  Device-2: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 3-4.1:3 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org 1.21.1.2 compositor: kwin_x11 driver:
    loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0")
    s-diag: 777mm (30.6")
  Monitor-1: DisplayPort-0 res: 2560x1440 dpi: 93
    size: 697x392mm (27.4x15.4") diag: 800mm (31.5")
  OpenGL: renderer: AMD Radeon RX 6800 XT (SIENNA_CICHLID DRM 3.42.0
    5.15.7-1-MANJARO LLVM 13.0.0)
    v: 4.6 Mesa 21.2.5 direct render: Yes
Audio:
  Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
    driver: snd_hda_intel v: kernel bus-ID: 28:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel bus-ID: 2a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 3-4.1:3 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.15.7-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.40 running: no
Network:
  Device-1: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter
    vendor: ASUSTeK driver: rtl8821ae v: kernel port: e000 bus-ID: 23:00.0
    chip-ID: 10ec:8812 class-ID: 0280
  IF: wlp35s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8168 v: 8.049.02-NAPI modules: r8169 port: c000
    bus-ID: 25:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp37s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 931.51 GiB used: 57.2 GiB (6.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 45.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 93.13 GiB size: 91.11 GiB (97.83%) used: 57.17 GiB (62.7%)
    fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 33.9 MiB (35.3%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p7 maj-min: 259:7
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 46.0 C mem: 48.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
  Processes: 300 Uptime: 2h 37m wakeups: 0 Memory: 15.62 GiB
  used: 3.62 GiB (23.2%) Init: systemd v: 249 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: 1371 pacman: 1369 lib: 361 flatpak: 0 snap: 2
  Shell: Zsh v: 5.8 default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.11

@TheBronx Well, again, I’m no expert so take this with a grain of salt…

I do notice that your system’s primary (only) drive is solid state SSD. You also have a swap file set up. That’s typically not a good combination inasmuch as the life of the SSD will deteriorate to the extent the swap file gets used regularly. (SSD drives have a more limited read/write cycle life than HDD).

Since you also appear to have 16gig of system memory, there’s a good chance you’re not really using the swap file anyhow - so it’s not likely causing your crashing.

But related to SSD drives, are you using TRIM (e.g., fstrim)? If so there are problems reported if it’s setup to clean garbage areas on a continuous basis - as opposed to periodic (typically weekly). The continuous setting can cause freezing up … which in turn perhaps is contributing to crashes in your situation if this is the case?

Hopefully the real experts will step up after reviewing your inxi dump above and offer some more helpful insights.

Either way, I would suggest disabling/removing your swap file and making sure you’re (1) using trim and (2) doing it only periodically on a timer rather than continuously.

Cheers.

1 Like

I didn’t have swap configured at first, but I thought if the system was unstable and maybe there was some kind of memory leak having an extra 4GB of swap could help. I enabled it 16 days ago, second post of this thread.

Regarding the SSD, I have not enabled anything special:

$ systemctl status fstrim.timer                                                                                                                                        ✔ 
○ fstrim.timer - Discard unused blocks once a week
     Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; disabled; vendor preset: disabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● fstrim.service
       Docs: man:fstrim

And /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=BC22-A3D2                            /boot/efi      vfat    umask=0077 0 2
UUID=63a90eaa-1325-4dae-8428-9feb978e9dbd /              ext4    defaults,noatime 0 1

Not sure if that answers your question completely.

Also, if this helps, I remember reading about the disk LED indicator and crashes/freezes so I’ve paid attention to it the last couple times: the LED was mostly off when the system crashed. Just blinking every few seconds but definitely not busy.

Thank you again!

1 Like

Okay, sorry - I misunderstood this following section you’d shared…

Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p7 maj-min: 259:7

So although you do have a swap partition (4 gig) you are not currently using it (it’s not mounted).

With an SSD and 16 gig of onboard RAM, you neither need a swap file nor would it be advisable for the life of your SSD drive. :ok_hand:

As for trim status, yes indeed, as you show above, the service is loaded and available – but it’s not active. With an SSD drive it is advisable to use “garbage collection” to clean up the orphan bytes left behind - and fstrim set to (weekly) timer is a great tool to handle this automatically for you.

To enable it:
systemctl enable fstrim.timer

and to start it up in the current session:
systemctl start fstrim.timer

Still being a newbie myself, I encourage anyone with greater expertise to correct anything I’ve misstated or confused. Meanwhile, I haven’t made a dent in your freeze/crash problem … :roll_eyes:

1 Like

For the record, cause at this point I am starting to loose track of the changes:
Haven’t changed anything since yesterday and it crashed again. This time the bluetooth USB receiver was not plugged in. Also no plasma widgets at all. So that was not it.
Next I am removing the USB infrared receiver and probably during the weekend try to plug keyboard and mouse directly instead of through the KVM switch. Also I will take the wireless network card out.
Confidence level that will do anything? Extremely low, but that’s all the hardware I can unplug basically.

Do you have a persistent live manjaro on USB (ALMA) ?
This was the way i found my problems.

  • I did boot from USB, and the problem was gone.
  • Then i did compare my USB-install step by step with my real manjaro
  • And i installed / changed the usb-install step by step until it had the same problem
  • the last step was leading me to the solution :wink:

This way i found a config file making all the trouble.

I could, the problem is that the crashes are completely random.
It might crash twice a day, but it might as well not crash in days.
Random + no logs, great combination hehe. ■■■■ my life.

BTW I removed the wireless network card. I wasn’t using it, but in the past when I needed it I had problems connecting to 5Ghz networks on linux (only 2.4Ghz worked fine). So who knows, fingers crossed.

That was fast, crashed again. It was not the network card.
Next step getting rid of the KVM USB switch
woops, another crash while I was writing this :laughing:

KVM switch disconnected, let’s see.

check if you have any unnecessary service running in the background. might be a cause of this.