Arch Linux

tomsk

Member

Registered: 2016-12-17

Posts: 224

[SOLVED] Frequent freezes

Hello, I started experiencing few days ago random freezing of my desktop, suddenly my desktop will freeze and I cannot do anything, even I cannot move mouse, only solution is hard restart of PC.

CPU & GPU temps are in normal, and I use GNOME with Wayland, I use this setup several years now and never had issue. I tried to open GNOME Logs application but it looks like it keeps logs only for current session, but I need logs from previous session, where could I find logs about that freeze?

It looks like pretty random, its sometimes after 20 minutes 3 times in a row, and other time it freezes after like 4 hours.

Last edited by tomsk (2025-03-13 11:31:12)

---

I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint

kinghol

Member

Registered: 2014-02-28

Posts: 24

Re: [SOLVED] Frequent freezes

Do you use any Flatpaks?

injiniero

Member

Registered: 2022-04-26

Posts: 34

Re: [SOLVED] Frequent freezes

With journalctl -b you can see the current boot log.
journalctl -b -1 show the previous boot and so on.

---

I was a precocious child at 50

tomsk

Member

Registered: 2016-12-17

Posts: 224

Re: [SOLVED] Frequent freezes

With journalctl -b you can see the current boot log.
journalctl -b -1 show the previous boot and so on.

Thanks, I found crash:

Mar 09 12:24:58 tomsk-PC kernel:  ? rcu_note_context_switch+0x575/0x5d0
Mar 09 12:24:58 tomsk-PC kernel:  ? report_bug+0xe7/0x210
Mar 09 12:24:58 tomsk-PC kernel:  ? handle_bug+0x58/0x90
Mar 09 12:24:58 tomsk-PC kernel:  ? exc_invalid_op+0x19/0xc0
Mar 09 12:24:58 tomsk-PC kernel:  ? asm_exc_invalid_op+0x1a/0x20
Mar 09 12:24:58 tomsk-PC kernel:  ? rcu_note_context_switch+0x575/0x5d0
Mar 09 12:24:58 tomsk-PC kernel:  ? rcu_note_context_switch+0x575/0x5d0
Mar 09 12:24:58 tomsk-PC kernel:  __schedule+0xb8/0x1f70
Mar 09 12:24:58 tomsk-PC kernel:  ? srso_return_thunk+0x5/0x5f
Mar 09 12:24:58 tomsk-PC kernel:  ? update_cfs_rq_load_avg+0x29/0x1c0
Mar 09 12:24:58 tomsk-PC kernel:  ? srso_return_thunk+0x5/0x5f
Mar 09 12:24:58 tomsk-PC kernel:  ? psi_group_change+0x177/0x390
Mar 09 12:24:58 tomsk-PC kernel:  ? srso_return_thunk+0x5/0x5f
Mar 09 12:24:58 tomsk-PC kernel:  schedule+0x27/0xf0
Mar 09 12:24:58 tomsk-PC kernel:  schedule_timeout+0xbf/0x100
Mar 09 12:24:58 tomsk-PC kernel:  wait_for_completion+0x86/0x170
Mar 09 12:24:58 tomsk-PC kernel:  _raw_q_flush+0xc5/0x100 [nvidia_drm bcf5fd5c57890e2c1d8915179326f061159455e8]
Mar 09 12:24:58 tomsk-PC kernel:  ? __pfx__q_flush_function+0x10/0x10 [nvidia_drm bcf5fd5c57890e2c1d8915179326f061159455e8]
Mar 09 12:24:58 tomsk-PC kernel:  ? __put_partials+0xbf/0x120
Mar 09 12:24:58 tomsk-PC kernel:  ? srso_return_thunk+0x5/0x5f
Mar 09 12:24:58 tomsk-PC kernel:  nv_kthread_q_stop+0x20/0xf0 [nvidia_drm bcf5fd5c57890e2c1d8915179326f061159455e8]
Mar 09 12:24:58 tomsk-PC kernel:  __nv_drm_semsurf_fence_ctx_destroy+0x2d/0x220 [nvidia_drm bcf5fd5c57890e2c1d8915179326f061159455e8]
Mar 09 12:24:58 tomsk-PC kernel:  drm_gem_object_release_handle+0xef/0x130
Mar 09 12:24:58 tomsk-PC kernel:  ? __pfx_drm_gem_object_release_handle+0x10/0x10
Mar 09 12:24:58 tomsk-PC kernel:  idr_for_each+0x72/0xf0
Mar 09 12:24:58 tomsk-PC kernel:  drm_gem_release+0x20/0x30
Mar 09 12:24:58 tomsk-PC kernel:  drm_file_free+0x203/0x280
Mar 09 12:24:58 tomsk-PC kernel:  drm_release+0xc1/0x130
Mar 09 12:24:58 tomsk-PC kernel:  __fput+0xe0/0x2b0
Mar 09 12:24:58 tomsk-PC kernel:  task_work_run+0x5c/0x90
Mar 09 12:24:58 tomsk-PC kernel:  do_exit+0x31e/0xb60
Mar 09 12:24:58 tomsk-PC kernel:  make_task_dead+0x90/0x90
Mar 09 12:24:58 tomsk-PC kernel:  rewind_stack_and_make_dead+0x16/0x20
Mar 09 12:24:58 tomsk-PC kernel: RIP: 0033:0x7b74ca03de56
Mar 09 12:24:58 tomsk-PC kernel: Code: Unable to access opcode bytes at 0x7b74ca03de2c.
Mar 09 12:24:58 tomsk-PC kernel: RSP: 002b:00007ffcba751910 EFLAGS: 00000202 ORIG_RAX: 000000000000002e
Mar 09 12:24:58 tomsk-PC kernel: RAX: ffffffffffffffda RBX: 00007b74c95819c0 RCX: 00007b74ca03de56
Mar 09 12:24:58 tomsk-PC kernel: RDX: 0000000000004040 RSI: 00007ffcba751990 RDI: 0000000000000003
Mar 09 12:24:58 tomsk-PC kernel: RBP: 00007ffcba751920 R08: 0000000000000000 R09: 0000000000000000
Mar 09 12:24:58 tomsk-PC kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000070
Mar 09 12:24:58 tomsk-PC kernel: R13: 00007ffcba751990 R14: 00005e46a6488c00 R15: ffffffffffffffff
Mar 09 12:24:58 tomsk-PC kernel:  </TASK>
Mar 09 12:24:58 tomsk-PC kernel: ---[ end trace 0000000000000000 ]---
Mar 09 12:24:58 tomsk-PC kernel: BUG: kernel NULL pointer dereference, address: 00000000000000ca
Mar 09 12:24:58 tomsk-PC kernel: #PF: supervisor instruction fetch in kernel mode
Mar 09 12:24:58 tomsk-PC kernel: #PF: error_code(0x0010) - not-present page

I use some flatpaks bot not often.

---

I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint

tomsk

Member

Registered: 2016-12-17

Posts: 224

Re: [SOLVED] Frequent freezes

New type of crash, happened during work, just VS Code and Android Studio open.

Mar 10 13:23:32 tomsk-PC kernel: CR2: ffffffffc0b14600 CR3: 0000000100ce4000 CR4: 0000000000350ef0
Mar 10 13:23:32 tomsk-PC kernel: note: ThreadPoolForeg[95548] exited with irqs disabled
Mar 10 13:23:32 tomsk-PC kernel: ------------[ cut here ]------------
Mar 10 13:23:32 tomsk-PC kernel: WARNING: CPU: 2 PID: 95548 at kernel/exit.c:885 do_exit+0x912/0xb60
Mar 10 13:23:32 tomsk-PC kernel: Modules linked in: tun uas usb_storage rfcomm snd_seq_dummy snd_hrtimer snd_seq nf_conntrack_netlink xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE xt_set ip_set xt_addrtype xfrm_interface xf>
Mar 10 13:23:32 tomsk-PC kernel:  sha512_ssse3 snd_hda_codec_generic snd_hda_scodec_component sha256_ssse3 snd_hda_codec_hdmi sha1_ssse3 eeepc_wmi aesni_intel snd_hda_intel asus_wmi gf128mul crypto_simd platform_profile snd_in>
Mar 10 13:23:32 tomsk-PC kernel: Unloaded tainted modules: binder_linux(OE):1
Mar 10 13:23:32 tomsk-PC kernel: CPU: 2 UID: 1000 PID: 95548 Comm: ThreadPoolForeg Tainted: P    B D W  OE      6.13.2-zen1-1-zen #1 393e73ceb395152ed6f22a9b3e01961614175574
Mar 10 13:23:32 tomsk-PC kernel: Tainted: [P]=PROPRIETARY_MODULE, [B]=BAD_PAGE, [D]=DIE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Mar 10 13:23:32 tomsk-PC kernel: Hardware name: ASUS System Product Name/TUF GAMING B450M-PRO II, BIOS 4002 02/24/2023
Mar 10 13:23:32 tomsk-PC kernel: RIP: 0010:do_exit+0x912/0xb60
Mar 10 13:23:32 tomsk-PC kernel: Code: 89 a3 20 0b 00 00 48 89 7c 24 08 48 8b 83 40 0d 00 00 e9 6e fd ff ff 48 8b bb 00 0b 00 00 31 f6 e8 d3 e0 ff ff e9 f7 fc ff ff <0f> 0b e9 62 f7 ff ff 48 89 df e8 9f b8 17 00 e9 f5 f8 ff ff>
Mar 10 13:23:32 tomsk-PC kernel: RSP: 0000:ffffb8cf50027ed0 EFLAGS: 00010286
Mar 10 13:23:32 tomsk-PC kernel: RAX: 0000000000000000 RBX: ffff9a8ab26a8000 RCX: 0000000000000000
Mar 10 13:23:32 tomsk-PC kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: ffff9a8a06b1c200
Mar 10 13:23:32 tomsk-PC kernel: RBP: ffff9a904b571200 R08: ffffffff99ab5888 R09: 00000000ffffefff
Mar 10 13:23:32 tomsk-PC kernel: R10: 0000000000000003 R11: 6854203a65746f6e R12: 0000000000000009
Mar 10 13:23:32 tomsk-PC kernel: R13: ffff9a8a06b1c200 R14: 0000000000000000 R15: 0000000000000001
Mar 10 13:23:32 tomsk-PC kernel: FS:  00007cb9fa3fe6c0(0000) GS:ffff9a910df00000(0000) knlGS:0000000000000000
Mar 10 13:23:32 tomsk-PC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 10 13:23:32 tomsk-PC kernel: CR2: ffffffffc0b14600 CR3: 0000000100ce4000 CR4: 0000000000350ef0
Mar 10 13:23:32 tomsk-PC kernel: Call Trace:
Mar 10 13:23:32 tomsk-PC kernel:  <TASK>
Mar 10 13:23:32 tomsk-PC kernel:  ? do_exit+0x912/0xb60
Mar 10 13:23:32 tomsk-PC kernel:  ? __warn.cold+0x93/0xed
Mar 10 13:23:32 tomsk-PC kernel:  ? do_exit+0x912/0xb60
Mar 10 13:23:32 tomsk-PC kernel:  ? report_bug+0xe7/0x210
Mar 10 13:23:32 tomsk-PC kernel:  ? handle_bug+0x58/0x90
Mar 10 13:23:32 tomsk-PC kernel:  ? exc_invalid_op+0x19/0xc0
Mar 10 13:23:32 tomsk-PC kernel:  ? asm_exc_invalid_op+0x1a/0x20
Mar 10 13:23:32 tomsk-PC kernel:  ? do_exit+0x912/0xb60
Mar 10 13:23:32 tomsk-PC kernel:  make_task_dead+0x90/0x90
Mar 10 13:23:32 tomsk-PC kernel:  rewind_stack_and_make_dead+0x16/0x20
Mar 10 13:23:32 tomsk-PC kernel: RIP: 0033:0x63cbed2bc821
Mar 10 13:23:32 tomsk-PC kernel: Code: ff 0f 00 00 0f 86 b9 01 00 00 4c 89 e2 48 81 c2 00 10 00 00 48 89 57 10 49 39 c9 0f 84 28 9e 01 00 4d 85 ed 0f 84 30 07 01 00 <4d> 89 65 00 49 8d 55 08 48 89 95 70 ff ff ff 4c 8b 65 c0 49>
Mar 10 13:23:32 tomsk-PC kernel: RSP: 002b:00007cb9fa3fb740 EFLAGS: 00010206
Mar 10 13:23:32 tomsk-PC kernel: RAX: 00007cb9fa3fba48 RBX: 000020e804584ce8 RCX: 0000000000000008
Mar 10 13:23:32 tomsk-PC kernel: RDX: 000020e804585cf0 RSI: 000020e804584cf0 RDI: 000020e800ab0ac0
Mar 10 13:23:32 tomsk-PC kernel: RBP: 00007cb9fa3fb950 R08: 0000000000000000 R09: 0000000000000000
Mar 10 13:23:32 tomsk-PC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 000020e804584cf0
Mar 10 13:23:32 tomsk-PC kernel: R13: 000020e804584ce8 R14: 00007cb9fa3fba28 R15: 000020e804584cf0
Mar 10 13:23:32 tomsk-PC kernel:  </TASK>
Mar 10 13:23:32 tomsk-PC kernel: ---[ end trace 0000000000000000 ]---
Mar 10 13:23:32 tomsk-PC kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 1000)
Mar 10 13:23:32 tomsk-PC kernel: BUG: unable to handle page fault for address: ffffffffc0b14600
Mar 10 13:23:32 tomsk-PC kernel: #PF: supervisor instruction fetch in kernel mode
Mar 10 13:23:32 tomsk-PC kernel: #PF: error_code(0x0011) - permissions violation
lines 12297-12358/12358 (END)

EDIT:
I have 32 GB of RAM and 32 GB of SWAP on m2 SSD, I was nowhere near 100% RAM usage, I had like 60% of RAM usage when it happened.

Installed nohang with uresourced --> didnt help

Downgraded kernel --> didnt help

Installed Nobara kernel --> didnt help

I ran memtest86 v11 for 3 passes, no errors found.

Now I uninstalled "binder_linux-dkms", we will see if it helps.

UPDATE: It was 3 days since uninstalling "binder_linux-dkms" and not a single crash since then, so looks like these kernel crashes were caused by "binder_linux-dkms", I installed it because I wanted to use Waydroid on my system

Last edited by tomsk (2025-03-13 11:08:27)

---

I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint

beanlord

Member

Registered: 2025-03-20

Posts: 1

Re: [SOLVED] Frequent freezes

thank you so much Tomsk, I made an account just to post this. been trying to find the culprit of these crashes for over a week now, and was lucky enough to come across your post.

for me, the latest update to the binder_linux-dkms package was the culprit causing frequent kernel panics. however, uninstalling it did not stop them. in order to fix the issue I had to
1. remove 'binder_linux-dkms' package
2. rebuild DKMS modules using

sudo dkms autoinstall

3. regenerate initramfs: I have dracut so I used

sudo dracut-rebuild

if you're using mkinitcpio, try

sudo mkinitcpio -P

if for someone simply removing binder_linux-dkms doesn't work, try that.