Re: Mesa 24.3.1 Update Causing Segmentation Faults On Several-Vendors GPU Architectures

[TeusLollo <TeusLollo@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/53434#issuecomment-2564577075

Comment:
> Thank you so much, that's very helpful.
> 
> I had these lock up issues a year ago, but then they went away.
> 
> When they were happening, they would happen maybe every 8+ hours. This reoccurrence is now more quicker like 30 mins or so.
> 
> Unfortunately I tried downgrading but it didn't go away. The system still freezes. I tried these combos:

Every time the AMDGPU kernel driver is worked upon (Usually to add support for newer GPUs), something like this happens. It comes and goes, and it's been like this for years. Remember that the AMDGPU driver is shared by many GPU adapters (Like, tens of those), thus one bug will affacted multi-generation adapters.

> ~# cd /sys/class/drm/card0/device
> /sys/class/drm/card0/device# echo low > power_dpm_force_performance_level 
> /sys/class/drm/card0/device# echo balanced > power_dpm_state 
> /sys/class/drm/card0/device# cd ../../card1/device
> /sys/class/drm/card1/device# echo low > power_dpm_force_performance_level 
> /sys/class/drm/card1/device# echo balanced > power_dpm_state 
> ```
> 
> https://wiki.gentoo.org/wiki/AMDGPU#Frequent_and_Sporadic_Crashes
> 
> Still got the crash though.

I did not to say to attempt any undervolting (Which should not be attempted unless you really know what you're doing). Also, the commands you're listing here are not about undervolting, but about indexing available GPU power states (Again, avoid attempting underclocking). 
Remember also that kernel parameters are needed at boot for (Most of) these to work, otherwise the GPU will just ignore those, but won't output that they're being ignored, and you'll be thinking it's working while it's not. 

No, I was writing about doing this: 

https://linuxreviews.org/HOWTO_undervolt_the_AMD_RX_4XX_and_RX_5XX_GPUs

But not the undervolting part, the "The Quick And Easy Way To Manually "Undervolt" AMD GPUs" (Which, again, is not "undervolting", but fixing GPU clock states, that's why they put it in the ""). 
Basically, look at the section for "HOWTO Limit The GPU To A Certain Set Of GPU Clock States" (But remember that you'll need to inject kernel parameters for this to work). 
Then, limit the GPU clock state to ONE specific clock state (It's all in the guide). It's critical for it to be ONE clock state, for whatever reason, that black screen is triggered by the GPU switching clock states on the fly. 

Again, much easier to just get `corectrl` and do it from there. It'll also let you see quite clearly if you've injected kernel paramters correctly.