New comment by TeusLollo on void-packages repository

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

Comment:
> I try to downgrade mesa, but it says I need to downgrade libglapi. I try to downgrade libglapi, but it says I need to downgrade mesa.

You can add multiple arguments in succession. Thus, `xdowngrade /var/cache/xbps/mesa-24.2.7_1.x86_64.xbps  /var/cache/xbps/libglapi-24.2.7_1.x86_64.xbps` (All in the same line at the same time) and so on. 
There is no hard limit to the number of arguments you can assign to a command. 
That should fix it, although you will probably have to downgrade more packages than `mesa` & `libglapi`, but it should be easy enough (`xbps` will tell you). 
This downgrade failsafe is in place because `mesa` packages of differing version may not play nicely together, although results may vary. 

> TBH I think void should just downgrade mesa/amdgpu. There's something very clearly massively broken in this latest release. People are reporting their systems just freezing and requiring a hard reboot.
> 
> https://gitlab.freedesktop.org/drm/amd/-/issues

We, in fact, have already downgraded. We were on `mesa-24.3.*` and that's when I and other users noticed the great segfaults cascade. If you can confirm, after downgrading, that the issue is gone, and can manage to get the output of whatever wayland-based window manager you are using (It depends on the window manager, each and everyone are a bit different, use `man` to access their built-in manual), you will can see your yourself if it's a segfault error, or something else entirely. 

BTW, keep in mind that AMD-based GPUs have an history of hard-freezes that is not related to `mesa`, it goes back and forth with each release and major updates on the kernel-level AMD driver (Which is not handled by `mesa` developers), and it may be related to `linux-firmware-amd` (Which is closed-source) not playing very nicely with such driver updates. A good approach is to use a tool like `corectrl` to block GPU performance to a fixed level (Low, high performance modes, or other approaches were you select a given GPU frequency and block it from downscaling or upscaling), which on my systems has avoided those entirely. 

https://gitlab.freedesktop.org/drm/amd/-/issues/960
https://bugs.archlinux.org/task/68396
https://bugs.archlinux.org/task/68424
https://bugs.archlinux.org/task/68402
https://gitlab.freedesktop.org/drm/amd/-/issues/716

Also, ensure that `linux-firmware-amd` is up-to-date