This issue is a long time coming. I got a mini pc (Asrock Deskmini h110, i5-6400, 16gb) that I have used for a long time with Kubuntu/Kde Neon, and most of its life, it worked great. Some years ago, it started freezing, especially at Graphic intensive workload, so I thought some hardware issue and converted it into a NAS and it worked absolutely fine as well for a couple of years there too. Recently my wife needed a Windows PC to do some work, and since I had upgraded my NAS, I repurposed the same PC and installed Windows on it, and it worked absolutely fine for her too. Then I decided to check some Graphics intensive workload, like 3d benchmarking stuff, and it didn’t freeze once. I was delighted, and thought maybe I didn’t investigated the issue the first time, and the PC was fine all along. So I reinstalled Debian 13, and lo behold, the issue came back. I found out while I was using IKEA’s 3d kitchen planner. So I replaced distros, and it froze on Ubuntu and CachyOS as well. I tried switching between Wayland and X11, switched browsers, but PC freezes seconds logging into IKEA’s kitchen planner (as soon as 3d graphics are loaded). I reinstalled windows, and my wife has been designing a kitchen in IKEA’s 3d kitchen planner for over an hour now, and it hasn’t frozen once. What’s going on? How do I even investigate this?
I have reinstalled Linux and had sudo dmesg -w running, but no logs are captured before it’s frozen. I have reproduced the issue multiple times now on Linux, and not once it froze on Windows. I have also done memtests, and tried multiple disks both nvme and sata. Also have tried multiple browsers with apt and flatpaks. I really need Lemmy’s collective intelligence to help me here.
SSH in from another machine, and
sudo dmesg -w. If the graphics die, it can’t display new logs on the screen. If the rest of the system is fine, an open SSH session should give you more info (and allow you to troubleshoot further).You can also check if the kernel is still functional by using a keyboard with a caps-lock LED. If the LED starts flashing after the “freeze”, it’s actually a kernel panic. You’ll have to figure out a way to obtain the kernel panic information (like using tty1).
After the “freeze”, try pressing the caps-lock key. If the LED turns on when pressing caps-lock, the Linux kernel is still functional. If the caps-lock key/LED does not work, the entire computer is frozen, and you are most likely looking at a hardware fault.
From there, you basically need to make educated guesses of what to attempt in order to narrow down the issue and obtain more information. For example, try something like
glxgearsorvkgearsto see if it happens with only one of those, or both (or neither).Well I did dmesg locally and via ssh, and neither showed any message before freezing. Similarly I did journalctl at next boot and no errors there either.
Capslock doesn’t work, neither can I ping the host. The system is completely frozen and can only be reset with physical power button.
Surprisingly glxgears worked fine and didn’t led to any freeze.
Sorry for the duplicate replies. Lemmy server drama…
That’s a tricky one if you’re getting no info from the kernel. I think the reply above about system instability under load sounds promising. Throttling things down to test seems like a good idea.