weird freeze during login or just after

miyoku157 · 2025-03-08 11:37:15

Hi,
I post here because I don't know if my issue come from hardware/kernel due to old hard or something else.
My computer is about 5-6 years old with this configuration
Cpu: AMD Ryzen 5 3600X @4.41Ghz
GPU:AMD Radeon RX 5700 XT
GPU driver : amdgpu through mesa
kernel: 6.13.5-zen1-1-zen

For the beginning I was on archlinux using hyprland (which work fine), but I already had one issue, I had to replace the CMOS Battery. (Otherwise I had to boot three time to have a correct boot)
So i wanted to try endeavour personally. I did install it graphically and installed hyprland. But I immediately got weird error, freezing at boot. Constant crash of Firefox tabs.
Due to that I switch back to archlinux ( with arch install)and set back hyprland . But I still have these problem.
To be more precise, I can boot 3-4 time and my PC freeze unable to do anything, sometime on login screen. Sometime just when hyprland is launching. And another time I can play during few hour and nothing happens.

So what I already tried:
Tried to switch to linux LTS but it didn't really make any difference
I did a memtest which didn't find any error.
I found that my GPU fan controller act weird. Like when I'm playing it doesn't increase the fan in automatic mode. So I've switch to a curve mode.

I've reduce some of my crash during game (which were certainly due to GPU) but now I I'm quite lost for the crash at boot. And don't find anything useful in journalctl
Do you have any idea where it could come?

Last edited by miyoku157 (2025-03-08 12:10:17)

seth · 2025-03-08 17:02:10

https://wiki.archlinux.org/title/Ryzen#Troubleshooting

Otherwise, how hard is the freeze?
Can you still switch the VT or reboot the system using the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ?

I did a memtest which didn't find any error.

nb that meaningful memtest runs are measured in days, not hours.

And don't find anything useful in journalctl

If you reboot by holding the power button, the journal is lost.
At best MCE errrors will be carried over and logged at the beginning of the subsequent boot.

miyoku157 · 2025-03-08 21:10:06

So when it freeze, i don't have access to the sysrq keys. (I verify before the freeze that it was correctly activated)
There is different case:
1.Sometimes, it's an application that crash (firefox, a tab in firefox, kitty, Vlc) completely randomly
2. My user session crash and go back to the login session (Hyprland crash)
3. Complete freeze of the computer, nothing respond anymore. The touch sysrq don't respon in that case.I've to shutdown manually.

For the first two, i got the dmesg and the journalctl in this gist: https://gist.github.com/miyoku157/5d6f6 … 4f651d731e
There is two file, the dmesg is for the First case, the journalctl is for the second one.
For when it freeze entirely, i don't really know what to do.

seth · 2025-03-08 21:33:55

mars 08 22:02:45 miyoku157 kernel: traps: nvim[42607] general protection fault ip:77989088742b sp:7ffe24e732f8 error:0 in libc.so.6[16c42b,77989073f000+171000]
mars 08 22:02:45 miyoku157 kernel: Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
mars 08 22:02:45 miyoku157 kernel: CPU: 7 UID: 1000 PID: 42607 Comm: nvim Not tainted 6.13.5-zen1-1-zen #1 5b84b501dacca2ec77360cdb30ab6a14f8685ecd
mars 08 22:02:45 miyoku157 kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C37/MPG X570 GAMING EDGE WIFI (MS-7C37), BIOS 1.Q1 08/30/2024
mars 08 22:02:45 miyoku157 kernel: RIP: 0010:elf_core_dump+0x76e/0x11a0
mars 08 22:02:45 miyoku157 kernel: Code: 48 01 b3 ff 4c 8b 44 24 68 31 d2 48 89 df be 03 00 00 00 41 89 40 20 e8 30 01 b3 ff 4c 8b 44 24 68 41 89 40 24 8b 43 18 85 c0 <07> 85 b1 05 00 00 41 c6 00 00 31 d2 b8 52 00 00 00 41 88 50 02 48
mars 08 22:02:45 miyoku157 kernel: RSP: 0018:ffffb0eb16c079d0 EFLAGS: 00010246
mars 08 22:02:45 miyoku157 kernel: RAX: 0000000000000000 RBX: ffff95e8f1cd8000 RCX: 000000000000004f
mars 08 22:02:45 miyoku157 kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffff95e8f1cd8000
mars 08 22:02:45 miyoku157 kernel: RBP: ffffb0eb16c07be8 R08: ffff95e8f1e6f000 R09: 00007ffe24e75531
mars 08 22:02:45 miyoku157 kernel: R10: ffff95e85d38fa40 R11: 0000000000000002 R12: ffff95e8f1e6f038
mars 08 22:02:45 miyoku157 kernel: R13: ffffb0eb16c07ce0 R14: 00007ffe24e754e1 R15: 000000000000004f
mars 08 22:02:45 miyoku157 kernel: FS:  00007798906e8780(0000) GS:ffff95eb1ef80000(0000) knlGS:0000000000000000
mars 08 22:02:45 miyoku157 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
mars 08 22:02:45 miyoku157 kernel: CR2: 000064428a244598 CR3: 000000023398e000 CR4: 0000000000350ef0
mars 08 22:02:45 miyoku157 kernel: Call Trace:
mars 08 22:02:45 miyoku157 kernel:  <TASK>
mars 08 22:02:45 miyoku157 kernel:  ? __die_body.cold+0x8/0x12
mars 08 22:02:45 miyoku157 kernel:  ? die+0x2e/0x50
mars 08 22:02:45 miyoku157 kernel:  ? do_trap+0xca/0x110
mars 08 22:02:45 miyoku157 kernel:  ? elf_core_dump+0x76e/0x11a0
mars 08 22:02:45 miyoku157 kernel:  ? exc_invalid_op+0x92/0xc0
mars 08 22:02:45 miyoku157 kernel:  ? elf_core_dump+0x76e/0x11a0
mars 08 22:02:45 miyoku157 kernel:  ? asm_exc_invalid_op+0x1a/0x20
mars 08 22:02:45 miyoku157 kernel:  ? elf_core_dump+0x76e/0x11a0
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  ? finish_task_switch.isra.0+0x99/0x2e0
mars 08 22:02:45 miyoku157 kernel:  do_coredump+0x1659/0x1ec0
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  ? __memcg_slab_free_hook+0xf7/0x140
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  ? kmem_cache_free+0x3fd/0x450
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  get_signal+0x896/0x8e0
mars 08 22:02:45 miyoku157 kernel:  ? srso_return_thunk+0x5/0x5f
mars 08 22:02:45 miyoku157 kernel:  ? do_compat_epoll_pwait.part.0+0xf7/0x140
mars 08 22:02:45 miyoku157 kernel:  arch_do_signal_or_restart+0x3f/0x260
mars 08 22:02:45 miyoku157 kernel:  irqentry_exit_to_user_mode+0x14b/0x200
mars 08 22:02:45 miyoku157 kernel:  asm_exc_general_protection+0x26/0x30
mars 08 22:02:45 miyoku157 kernel: RIP: 0033:0x77989088742b

Make sure your RAM isn't overclocked (XMP etc) and see the ryzen troubleshooting page
In doubt try the non-zen or lts kernel

miyoku157 · 2025-03-10 10:51:05

Hi,
I've try to follow some of the troubleshoot for ryzen with no great result.
I tried the linux-LTS but it doesn't work either.
I tried to remove one of my RAM (think it could come from a corrupt ram). And it work lot better. But still got one freeze this morning. which is weird.
In fact i wonder if it's not the mother board and not the RAM the issue. But i don't think it's the kernel

seth · 2025-03-10 16:44:05

I've try to follow some of the troubleshoot

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What *specifically* did you "try"?

I tried to remove one of my RAM (think it could come from a corrupt ram). And it work lot better. But still got one freeze this morning. which is weird.

seth wrote:

Make sure your RAM isn't overclocked (XMP etc)

Configure the most conservative clocks and timings possible, see whether memtest86+ reports errors (during at least a 16h run, running one cycle is meaningless) with the original configuration to confirm your theory that it's the RAM.

Arch Linux

#1 2025-03-08 11:37:15

weird freeze during login or just after

#2 2025-03-08 17:02:10

Re: weird freeze during login or just after

#3 2025-03-08 21:10:06

Re: weird freeze during login or just after

#4 2025-03-08 21:33:55

Re: weird freeze during login or just after

#5 2025-03-10 10:51:05

Re: weird freeze during login or just after

#6 2025-03-10 16:44:05

Re: weird freeze during login or just after

Board footer