AMD GPU crashes with segfault at random

Question

AMD GPU crashes with segfault at random

SaphireLattice opened this issue 10 months ago · 7 comments

SaphireLattice commented 10 months ago

Nothing relevant in the game logs, probably because it gets violently killed by the system before anything can come up. End up with the entire X session resetting and getting thrown to the login screen. So GPU is fine after, just, yeah.

Also, Iris is uninstalled. The shaders fail to compile on another modpack and that exception is not caught for some reason so, yeah, preemptively threw it out.

dmesg output:

[339846.028749] amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32811, for process java pid 658486 thread java:cs0 pid 658716)
[339846.028757] amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[339846.028760] amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430
[339846.028762] amdgpu 0000:0b:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (data) (0xa)
[339846.028764] amdgpu 0000:0b:00.0: amdgpu:     MORE_FAULTS: 0x0
[339846.028766] amdgpu 0000:0b:00.0: amdgpu:     WALKER_ERROR: 0x0
[339846.028768] amdgpu 0000:0b:00.0: amdgpu:     PERMISSION_FAULTS: 0x3
[339846.028769] amdgpu 0000:0b:00.0: amdgpu:     MAPPING_ERROR: 0x0
[339846.028771] amdgpu 0000:0b:00.0: amdgpu:     RW: 0x0
[339856.060146] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=24673070, emitted seq=24673072
[339856.060436] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process java pid 658486 thread java:cs0 pid 658716

Info:

AOF6 1.10.1 with removed Iris
GPU: AMD RX 6800 XT
OS: Archlinux
Kernel: Linux cinnabar 6.5.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Oct 2023 22:52:14 +0000 x86_64 GNU/Linux
Launcher: Prism Launcher 7.2
LWJGL: Both on 3.3.1 and 3.3.2 - with or without native GLFW (3.3.8)
Java 17 and 21, either one

From glxinfo -B:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6800 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.8-arch1-1) (0x73bf)
    Version: 23.2.1
    Accelerated: yes
    Video memory: 16384MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

SubordinalBlue · Answer 1 · 2024-02-26T20:17:09.000Z

GLFW and LWJGL are the two main libs MC uses that have caused Linux-only problems in the past. I'd suggest updating to the newest possible version of them.

guskikalola · Answer 2 · 2023-12-17T01:27:32.000Z

Im also having the same issue on Linux using a 6700 XT

For now what I've done is setting Minecraft so that it uses integrated graphics, so far so good ( been playing for 10h )

From glxinfo -B:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.6.7-zen1-1-zen) (0x73df)
    Version: 23.2.1
    Accelerated: yes
    Video memory: 12288MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

MickTheRus · Answer 3 · 2024-02-02T13:34:06.000Z

I have regrettably befallen upon the same issue.
From glxinfo -B

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 16.0.6, DRM 3.56, 6.7.2-zen1-2-zen) (0x73df)
    Version: 23.3.5
    Accelerated: yes
    Video memory: 12288MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

Have either of you used shaders by any chance? I do wonder if that could be possibly causing the issue, I guess I'll have to try it myslef.

MickTheRus · Answer 4 · 2024-02-02T16:10:59.000Z

So I played for 2 hours exploring and shit and it seems fine. I also gave it 32 gigs but that's over the top, not let's see if I crash with shaders on default

SaphireLattice · Answer 5 · 2024-02-02T17:11:20.000Z

So I played for 2 hours exploring and shit and it seems fine. I also gave it 32 gigs but that's over the top, not let's see if I crash with shaders on default

I sincerely doubt that it has anything to do with system RAM. Please make sure that there is at least something similar in dmesg. This is not just a game crash but a full graphical system mess.

MickTheRus · Answer 6 · 2024-02-02T21:09:16.000Z

dmesg.log
Unless I'm missing something seems to similar issue as yours.

MickTheRus · Answer 7 · 2024-02-04T14:44:10.000Z

After disabling resize bar I have not had any crashes since, if I'm reading correctly it might be an issue with GLFW.

crash_report.txt

Share to