I’ve looked through most of the forum posts about system freezes, as mentioned in one of them, and most of them seem to occur on computers with dedicated Nvidia graphics cards. Each freeze happens without any warning, and the only way to recover is a hard reboot. I’ve tried SysRq, REISUB, which works fine when there’s no freeze to kill processes and reboot the computer. However, when a freeze occurs, SysRq becomes ineffective. SSH connections also fail, and the keyboard and mouse, along with all other functions, become unresponsive. In my previous post, I thought I had a restart due to a memory leak issue, but it doesn’t seem to be the case because I’ve already resolved the memory leak problem.
Since there are no logs left in the system after a freeze, it’s challenging to pinpoint the issue’s cause. However, I remember that I didn’t experience these freezes when I initially installed the system. If you need any information about my system, I’ll do my best to provide it. I hope there’s a solution out there that can help me resolve this problem. Thank you, everyone!
Just like all the symptoms mentioned in this post: random-system-freezes-intel-i5-nvidia-graphics , it seems that this issue has been going on for a long time without a solution. It’s frustrating, and this really makes it difficult for me to continue using Linux. The stability issues are just too problematic.
I’m going to be one hundred percent honest with you, this is in no way aimed at you, or means that I find you stupid or anything, but I highly doubt this. Log from after the crash is anyway not really important, IMHO. Logs from immediately just before the crash is more important. So that is what we’ll attempt to look for.
You mentioned you posted here previously, so I’ll not explain how to post terminal output. I’ll just as you to please provide the output of:
journalctl --boot=-1 --no-pager
Where:
The --boot=-1 is from the previous boot. Adjust this to be for the last bootup when a crash happened; and
--no-pager formats the output nicely for use here, on the forum.
Note:
I have left filters out for now so that the scope of the output is as broad as possible. We can refine it later.
However, if it didn’t happen from the beginning, I suspect failing hardware, most likely HDD (or possibly SSD.) But there is, as of how, no way for us to be sure.
Here is the log of a reboot that happened to my computer the last time I used vlc to watch a movie, it wasn’t a freeze, but I thought it might help. Also, I know that the log before the crash is useful, I mean the log before the crash without any errors, even the time on the screen when the freeze occurs is a minute or two later than the last entry in the log, when the freeze occurs again, I will upload it Log of the last startup.
Than you, but please, in the future when posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
# echo $XDG_SESSION_TYPE && glxinfo | grep server ✔
x11
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
I was having very similar issues on my system. I ran a memory test using a bootable USB drive and found all sorts of errors in the memory. Shutting down the system, removing the memory and reinstalling the memory fixed the issue.
May or may not help in your case, but you can try it and see what happens.
This sounds like an excellent plan. If you do, make sure that the contacts are clean.
Also, the log are spammed with:
ACPI group/action undefined: button/right / RIGHT
And I don’t know if it’ll make any difference, but at this time, I’m guessing you’re willing to try it, and it doesn’t seem like it could hurt. So try Disabling the key events as per below:
I’m also burning to use the latest, but forced to stick to 6.1, because my PC doesn’t wake fro suspend on anything newer. So I’ll continue to test newer versions, but I’m OK for now.
Thank you very much for your efforts to help me resolve my issue! I will try each of the solutions you provided.
I have now disabled ACPI’s recognition of the arrow keys. However, I haven’t been able to close qbittorrent yet. After that, I will try not using qbittorrent and see if the system still freezes.
Regarding the issue of downgrading the Linux kernel, I need to provide some additional information:
In fact, I installed Manjaro when it was version 22, and at that time, the kernel should have been 5.x (I’m sorry, I can’t remember the exact kernel version). There were no options for power configuration back then (if I remember correctly, there was no option to choose between performance or power-saving modes).
At that time, I also installed Optimus Manager to manage GPU switching because my laptop’s Type-C port is directly connected to the dedicated GPU. If I wanted to connect an external monitor, I had to use the dedicated GPU for video output. Since then, occasional freezes have occurred, but they were infrequent and rarely happened.
This time, I reinstalled Manjaro (completely wiping the system), and during the installation process, I did not encounter this issue. Even when I was configuring some system software and KDE, it did not occur.
Oh, I have a new discovery. This link mentions a bug related to the C6 state of AMD’s Ryzen processors that can lead to freezes. This might help me solve the problem, and I will give it a try.
I believe the issue should be resolved! When I disabled the C6 state of the Ryzen processor using this method, everything is working perfectly, and I feel incredibly comfortable. Just a day ago, I was even considering giving up on Linux! I’ll summarize the method as follows:
yay -S disable-c6-systemd
sudo modprobe msr
Then edit file: /etc/modules-load.d/modules.conf
sudo nano /etc/modules-load.d/modules.conf
Add the following line to the file:
msr
Then reboot your computer, input the following cmd:
If you see the following content in the Konsole output:
You should reinstall the software disable-c6-systemd
That all, hope this method can help you, who is tirelessly working in front of the screen!
This method comes from: Ryzen随机卡死问题 github for disable-c6
sounds like an excellent plan. If you do, make 
sure that the contacts are clean.
