Minecraft 26.1.2 crashes on CachyOS with AMD RX 9070 XT, amdgpu context lost

Hello,

I am having crashes in Minecraft on CachyOS. The game runs for a while and then crashes with exit status 6. The important part seems to be an AMDGPU / Mesa issue, not a normal Minecraft crash.

System information:

OS: CachyOS
Kernel: 7.0.11-1-cachyos
GPU: AMD Radeon RX 9070 XT
Mesa: 26.1.2-arch2.1
OpenGL: 4.6
Vulkan driver: RADV
CPU: AMD Ryzen 7 3700X
RAM: 32 GB
Launcher: Prism Launcher 11.0.2
Java: 25.0.1
Minecraft: 26.1.2 Fabric
Fabric Loader: 0.19.2

Mods:

Fabric API 0.151.0+26.1.2
Sodium 0.8.12+mc26.1.2
Iris 1.10.9+mc26.1.1
Xaero’s Minimap
Xaero’s World Map

The crash also happens with shaders disabled. In the latest log I can see:

Shaders are disabled because enableShaders is set to false in iris.properties

The game starts normally, joins the server and runs for a while. Later it crashes. In earlier logs and system logs I saw AMDGPU related messages like:

amdgpu: The CS has cancelled because the context is lost. This context is guilty of a hard recovery.

There was also an AMDGPU page fault mentioning the java process.

What I already tried:

Updated the system with pacman
Kernel changed from 7.0.10 to 7.0.11
Mesa changed from 26.1.1 to 26.1.2
Disabled shaders in Iris
Reduced Minecraft RAM to 6 GB
Checked OpenGL and Vulkan information

The flite / narrator error is also visible in the Minecraft log, but I do not think it is the cause, because Minecraft starts normally after that and crashes much later.

My question:

Is this a known issue with RX 9070 XT, Mesa 26.1.x, Sodium/Iris or CachyOS kernel 7.0.x?

What would be the best next test?

You disabled shaders, but I’d try running the vanilla version to see if one of the mods could be misbehaving. Offhand the maps seem like they’d be my first suspect, but I’d try a pure vanilla install to narrow it down and if it doesn’t break, slowly add the mods back in one at a time.

At least for me, on my 6800XT in games I got a similar crash which was pretty generic and I spent months playing with kernel flags. Turned out, I had similar on Windows (guess Linux made it more common as I went from a crash a month to one every hour) and I had to hunt down a VBIOS update. Unsure if that would apply here, but something worth keeping in mind.

Thanks for the suggestion. I will try that after my vacation and will keep this thread updated once I have tested it.