Sure, I checked. Here’s a screenshot from Gpu-Viewer:
And here’s a screenshot from Cyberpunk 2077:
Interesting… So not only a RADV issue…
1 Like
Are you guys able to get corectrl advanced options for 9070xt? I am not sure if it’s a problem with my local or lack of driver support.
Under advanced I have power limit, voltage offset and min / max memory clocks.
CoreCtrl version 1.4.3, kernel 6.13.6 and mesa 25.1.0 (git) linux-firmware-git
1 Like
I have had it running pretty well, i found that launching the game in a gamesope session fixed the no launch issue for me.
gamescope -e -f --prefer-vk-device=1002:7550 -- /usr/bin/steam -steamos
as a gdm session seems to work pretty well for me
Yeah, I was just lucky for a while, I am getting crashes again with the exact same error as you.
[ 318.946776] amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32799)
[ 318.946969] amdgpu 0000:0d:00.0: amdgpu: in process DD2.exe pid 20260 thread vkd3d_queue pid 21398)
[ 318.946972] amdgpu 0000:0d:00.0: amdgpu: in page starting at address 0x00001f3dc0111000 from client 10
[ 318.946975] amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
[ 318.946977] amdgpu 0000:0d:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
[ 318.946979] amdgpu 0000:0d:00.0: amdgpu: MORE_FAULTS: 0x1
[ 318.946980] amdgpu 0000:0d:00.0: amdgpu: WALKER_ERROR: 0x0
[ 318.946982] amdgpu 0000:0d:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 318.946983] amdgpu 0000:0d:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 318.946985] amdgpu 0000:0d:00.0: amdgpu: RW: 0x0
There’s issues opened with both amdvlk and mesa for this error, ranging across 6000 and 7000 cards as well. One potential workaround listed is setting power_dpm_force_performance_level to high. Gonna try that next.
I’m on arch trying to compile mesa-git, but when its pulling it gets a RPC error and wont continue, this also happens if I try to manually pull the package build without an aur helper.
mesa 1:25.0.1 is already available on Extra. So no need to use mesa-git from aur right now.
Bazzite finally has a stable release with the new newest mesa 25 drivers.
But can anyone confirm if this is the special firmware everyone is talking about?
20241210-1 
20250211-1
In STALKER 2, I’m getting the ring_0 gpu reset after about 15 - 20 minutes of play. The only game I’ve encountered this in so far.
I tried the RADV_DEBUG=nodcc,nohiz launch option but no effect.
Did you try latest git today? Mesa issue 12781 was just merged. I have not had a crash since the release, been doing maybe 1h of Cyberpunk 2077 + the bench, Ghostwire: Tokyo, Hogwarts Legacy, The Finals, CS2, on this branch before merge without any issues.
TL;DR
A fix was just merged on mesa main, i recommend trying it for anyone still having issues!
1 Like
I would like to give it a try. I’m on arch with mesa-git installed. Used yay to install it.
How might I update my mesa-git using yay? I tried simply yay mesa-git and it reports it wants to do this:
1 aur/mesa-git 25.0.0_devel.200442.bfa6b9b6551.d41d8cd-1 (+187 3.62) (Installed: 25.1.0_devel.203056.de2a65ade68.d41d8cd-1)
Is this right? Feels like it wants to downgrade it or something. I’m very new to Arch and it’s things.
This…doesn’t look great. Now my card is not drawing over 150W and my fps is spiking like crazy. Maybe it won’t crash anymore, but now it’s just completely unplayable.
I’m on Mesa 25.1.0-devel (git-f5c66e2d4a)
When using development packages, you need to use the “–devel” argument with yay. It will check those packages and install the latest commit on the default branch (main branch for mesa).
The bfa6b9b6551 part of the package version is the commit hash from the main branch, which you can check on their gitlab. Right now latest commit hash is 04e9431f4f0b3a08948b706f2c4b3ddccd4d1892.
On a side note, I managed to undervolt the card using corectrl like @synrgy87 said. I can’t go over -100mv without crashing any benchmark though which is far less than der8auer. What do you guys use for benchmarking and stress testing on Linux ? Occt doesn’t yet have a publicly available Linux version. I used 3dMark but some benchmarks don’t work with Proton.
1 Like
It’s very easy actually, if you want to update git packages just type
yay -Syu --devel
If you want yay to always update git packages add also --save 
1 Like
Thanks @Finderr & JuYawn & linde12 (i can only mention 2 users).
Unfortunately, the latest builds seem to be presenting a different issue now (progress?).
This was a hard ass crash. Had to hit the reset button on my case. Previously it just crashed to desktop with the ring 0 error in journal.
fyi @sebas my GPU isn’t have any power draw issues, the frames were smooth (on epic settings) in Stalker 2 prior to the crash.
This was just one attempt, and interestingly it happened the moment I died. I’ll give it another go but it’s past 11pm here and I’m sick so I will pack it in shortly.
Hmm, now that you mentioned it I did some more tests and it seems powerdraw issue is related to FSR. At least in Dragons Dogma 2, which I am testing,
You are right about the error changing, though now I am am getting something else:
mar 14 23:28:05 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: Dumping IP State
mar 14 23:28:05 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: Dumping IP State Completed
mar 14 23:28:05 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=773014, emitted seq=773016
mar 14 23:28:05 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: Process information: process DD2.exe pid 99218 thread vkd3d_queue pid 99318
mar 14 23:28:05 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: Starting gfx_0.0.0 ring reset
mar 14 23:28:07 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: Ring gfx_0.0.0 reset failure
mar 14 23:28:07 SHODAN kernel: amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
mar 14 23:28:10 SHODAN kernel: [drm:gfx_v12_0_hw_fini [amdgpu]] ERROR failed to halt cp gfx
I wanted to run a benchmark in Cyberpunk 2077. The game launched, but the benchmark crashed.
After finding this thread, I installed the mesa-git and linux-firmware-git packages, and the Cyberpunk 2077 benchmark ran, but the result was disappointing. It was almost 30 FPS lower than in Windows.
Arch Linux, Heroic Launcher (GoG version), GE-Proton9-26 (also tried earlier versions).
Other game performances looks ok for me so far.
Looking for help on this.
I’d like to revert back to before I did these updates, but when I do I get the following;
resolving dependencies...
looking for conflicting packages...
:: lib32-mesa-1:25.0.1-2 and lib32-mesa-git-25.1.0_devel.203168.b2a2d197f99.d41d8cd-1 are in conflict. Remove lib32-mesa-git? [y/N] y
:: mesa-1:25.0.1-3 and mesa-git-25.1.0_devel.203128.91feef40db0.d41d8cd-1 are in conflict (libva-mesa-driver). Remove mesa-git? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing mesa-git breaks dependency 'opencl-rusticl-mesa' required by lib32-opencl-rusticl-mesa
:: removing mesa-git breaks dependency 'vulkan-driver' required by steam
:: removing lib32-mesa-git breaks dependency 'lib32-vulkan-driver' required by steam
:: removing mesa-git breaks dependency 'vulkan-driver' required by steam-native-runtime
:: removing lib32-mesa-git breaks dependency 'lib32-vulkan-driver' required by steam-native-runtime
type or paste code here
-Sdd to skip all dependency checks. Not normally something you want to do, but in this case the packages are equivalent.