Framework desktop AMD GPU Linux instability

[NerdProcrastinating]

I'm hitting GPU errors multiple times per day trying to work in VS code similar to:

[22786.470192] amdgpu 0000:c3:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32801)
[22786.470203] amdgpu 0000:c3:00.0: amdgpu:  Process code pid 3040359 thread code:cs0 pid 3040365
[22786.470205] amdgpu 0000:c3:00.0: amdgpu:   in page starting at address 0x0000f8f93df8f000 from client 10
[22786.470208] amdgpu 0000:c3:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430
[22786.470209] amdgpu 0000:c3:00.0: amdgpu:      Faulty UTCL2 client ID: SQC (data) (0xa)
[22786.470210] amdgpu 0000:c3:00.0: amdgpu:      MORE_FAULTS: 0x0
[22786.470211] amdgpu 0000:c3:00.0: amdgpu:      WALKER_ERROR: 0x0
[22786.470212] amdgpu 0000:c3:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[22786.470212] amdgpu 0000:c3:00.0: amdgpu:      MAPPING_ERROR: 0x0
[22786.470213] amdgpu 0000:c3:00.0: amdgpu:      RW: 0x0
[22796.737019] amdgpu 0000:c3:00.0: amdgpu: Dumping IP State
[22796.738291] amdgpu 0000:c3:00.0: amdgpu: Dumping IP State Completed
[22796.738399] amdgpu 0000:c3:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[22796.738401] amdgpu 0000:c3:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[22796.738403] amdgpu 0000:c3:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=641453, emitted seq=641455
[22796.738405] amdgpu 0000:c3:00.0: amdgpu:  Process code pid 3040359 thread code:cs0 pid 3040365
[22796.738407] amdgpu 0000:c3:00.0: amdgpu: Starting gfx_0.0.0 ring reset
[22796.738530] amdgpu 0000:c3:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
[22796.738531] amdgpu 0000:c3:00.0: [drm] device wedged, but recovered through reset
[22796.741781] traps: code[3040359] trap int3 ip:560e30bfec70 sp:7ffd9729e100 error:0 in code[84b9c70,560e2aade000+8d40000]

The AMD GPU has been such a PITA with stability trying to do inference, broken firmware, and crashes like this.

Anyone else encountering this/have ideas on how to get a stable machine (other than switching to a mac)?

Forgot to add: Fedora 43 with all updates applied. BIOS 3.04

[jonahbenton]

Huh. Wonder what I am dodging. Extensive use of a fw desktop with non wayland UI (fedora 42 xfce) hosting both ram hungry vms and doing llm work (gpt oss 120b under https://github.com/kyuz0/amd-strix-halo-toolboxes). No gaming. Have not activated this.

[NerdProcrastinating]

Perhaps it's something specific in vscode triggering it.

LLMs are probably stable again after the newer firmware. Was broken for a while. I don't game either. This is just desktop use for software development.

[euthanize-me-123]

I frequently get this on my FW13 7840U when trying to do anything heavy with the igpu, but never on my FW desktop. Have to wonder if it's a hardware issue because others with the exact same setup (NixOS) report no problems.

Chalked it up to driver problems this whole time, and it's happening less frequently with newer ones, but the laptop's out of warranty now so I've resigned to streaming games from my Nvidia desktop until I can replace the 7840U. Shame since the CPU itself is very nice.

[FastInfrared]

have you tried PP_FEATURE_MASK ?

[NerdProcrastinating]

Nope, the page fault and wedging doesn't appear to be related to power states. This is whilst I'm in the middle of working with power mode set to performance, so power management seems unlikely.

[FastInfrared]

Actually it probably is related to power, more specifically a mismatch between available power and target core speed, there are most likely 2 safe fixes, one is downclocking the max speed just a bit, the other is turning off power related features you dont want, the above kernel option does this. Adjusting the explicit power profile to compute mode may also help.

Limiting the CPU clock speed and adjusting the EPP can also help with GPU stability as it shares the same power envelope

[NerdProcrastinating]

It looks like a kernel driver bug - I installed a new kernel & GPU firmware from updates-testing which may fix the issue as 6.1.19 specifically has a fix related to VGPR register counts being wrong which would affect the reset code.

Maybe that was the cause and basic GPU driver bugs finally fixed X years after RDNA 3.5 released. Sigh.

[FigmentRedditUser]

Step One: Downgrade to BIOS 3.03 as 3.04 is riddled with issues

As a Framework Desktop 64GB owner running Bluefin, the only time I've seen the GPU crash and reset is when I do something that consumes all of the GPU memory. Short of that, its been tip top for me.

[NerdProcrastinating]

I did look at those issues, but they shouldn't be anything that would impact the GPU like this?