I think I ran into a problem with the kernel itself, and I don't know how to proceed

[justAneewb]

Hello, Linux newbie here. I ran into a disk failure, and so had to install an OS again. I decided to try OM Rome, but the live boot system simply crashes merely seconds after initialising plasma. The screen goes black, then seemingly random pixels fill it, then, after quite some time, I’m thrown back to the user log in screen.
Even bigger of a problem is the fact that other distributions exhibit the very same behaviour, with the very same error logs.
The log bellow was extracted using dmesg -l err

[qui jan 16 22:04:51 2025] systemd[1]: systemd-importd.socket: Socket service systemd-importd.service not loaded, refusing.
[qui jan 16 22:04:51 2025] systemd[1]: Failed to listen on systemd-importd.socket - Disk Image Download Service Socket.
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, signaled seq=3151, emitted seq=3153
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: amdgpu: Process information: process calamares pid 2010 thread calamares:cs0 pid 2075
[qui jan 16 22:05:40 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring kiq_0.2.1.0 test failed (-110)
[qui jan 16 22:05:40 2025] [drm:gfx_v8_0_hw_fini.llvm.10992183699379143067 [amdgpu]] ERROR KCQ disable failed
[qui jan 16 22:05:40 2025] amdgpu: cp is busy, skip halt cp
[qui jan 16 22:05:40 2025] amdgpu: rlc is busy, skip halt rlc
[qui jan 16 22:05:41 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring comp_1.0.3 test failed (-110)
[qui jan 16 22:05:41 2025] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring comp_1.0.5 test failed (-110)
[qui jan 16 22:05:41 2025] [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!
[qui jan 16 22:05:52 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:02 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:12 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:22 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:33 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:43 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:06:53 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:03 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:14 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:24 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered
[qui jan 16 22:07:34 2025] amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, but soft recovered

The only difference between any of them is the process that triggers it. It’s often calamares (installing is the first thing I try), but when the crash occurs before I even manage to open the installer, dmesg will blame Wayland itself.
Even if the issue cannot be solved here, I would like at least some information on where and how to forward this. Also, I apologise if any relevant info is missing (newb, don’t even know where to start) and will provide more if prompted. I just want my machine to work again

[ben79 (Ben Bullard)]

Welcome @justAneewb to OpenMandriva and our forum. This forum is for users of OpenMandriva Linux operating systems.

OpenMandriva Forums are primarily users helping other users.

You are welcome to talk to our developers at OpenMandriva Chat.

Users with a problem need to read How to get better results when posting about problems before reporting any issue or problem. The article is not too long and Do Read.

When a new user has an issue please look in the documentation for OMLx. OpenMandriva wiki, Forum Resources guide and the “Search” function of the forum.

If you don’t find what you are looking for, try an Internet search. One can find out a lot from documentation or forum posts at other Linux distros. If user finds something written for another distro but you have some doubt ask at OpenMandriva Chat.

For serious technical issues and package/feature requests please file a bug report here.

Note: We are a small group. All the contributors and developers here are unpaid volunteers.
You can make OpenMandriva grow and improve by getting involved

Any help with testing would be appreciated whether one is technically proficient or a very non-technical user. The more people and more hardware we can get involved the better we can make OMLx releases and packaging. We do a lot of testing in VM’s as well. Developers tend to use Qemu, most user level testers use VirtualBox.

Some hopefully helpful suggestions:

We request that problems reported in forum or in a bug report be limited to one problem per thread or report.

We suggest that if your problem reported in the forum or on OM-Chat is not resolved in a few days to please file a proper bug report.

If you have not already done so scroll thru the “Big Fat Warning” at the top of this page and read the information or use the links provided.

Before reporting any problem please read this.

We are simply and respectfully trying to get people to be aware that as a very small group we are volunteering, unpaid, our time, knowledge, ect, to help you.

[eepardaku]

I kinda had an issue like this with an HP EliteDesk one time. The solution was to disable secure boot and disable legacy boot in BIOS. My issue wasn’t precisely like yours, but my HP EliteDesk had an AMD Ryzen 5 CPU and the boot sequence was getting messed up when it was trying to initialize the onboard graphics.