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: 3177 bytes --]

New comment by TeusLollo on void-packages repository

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

Comment:
> Thanks so much. This is hugely helpful.
> 
> I followed your advice, and rebooted kernel 6.6 with the param `amdgpu.ppfeaturemask=0xffffffff`.
> 
> Then I open corectrl. My external GPU is card 0, and internal is card 1. For card 0, I see the GPU frequency constantly changing, but it remains fixed at 600 Mhz for card 1.
> Even with this, my system crashed.
> 
> Interestingly it only seems to happen when switching windows. If I use a single terminal window, the crash doesn't happen.

A few more things:

1) Remember that with `corectrl` you need to press the "Apply" button on top-right of the window for settings to be injected, and "Save" (Only appears after having pressed "Apply") for those to be remembered. Double check you did that just in case. 

2) With hardware this powerful, you probably don't need two GPUs working in tandem (Which they don't really work in tandem, most of the work is offloaded to the PCIe-located GPU regardless). You can disable your CPU-embedded GPU in BIOS/UEFI. It'll save you on CPU heat, power consumption, and lots of headaches in the future when configuration gets confused because there are two display adapters. Even on a dual or triple setup monitor, there really is not a need to keep the CPU-embedded GPU activated. You may want to retry and see if a 1-GPU setup does away with crashes. 

3) You shouldn't downgrade the `*-firmware` packages. They're just collecton of binaries provided by manufacturers. Normally, newer version just increase the amount of binaries container, but some ancient binaries may be dropped because of security concerns. Since you're using pretty much recent hardware, you're better staying on the latest firmware packages. 

4) You did not mention what window manager (WM) you are using. If you're on one of the typical desktop environments (DEs) (Like Gnome, KDE, XFCE and the like), each of those comes with its own WM. You should take a look at their documentation and see where the WM locates .log files. If you're using a custom WM, you may want to check the documentation of that WM to see where it stores .log files. Once you've found .log files, run a search into those, and see if you can find anything with "segfault" or "seg" or "segmentation". Remember for the search to be case-insensitive and NOT to look for whole words only. 

If not, than you're experiencing a different problem than the one we've been identifying here. If so, you may want to open a separate issue here on void-packages (Here it can be requested for a package downgrade assuming many are experiencing the same problem, or a patch commit if developers appear to have produced an hotfix somewhere). 
You may otherwise open an issue on the repository of the WM developers, or the repository of the `mesa` developers (On gitlab) if you're absolutely sure this happened when `mesa` was updated. They'll take it from there, since here it's mostly software packaging and distribution to be done, not software development of each of those software suits.