All versions of >media-libs/mesa-21.1.7 crash with "free(): invalid pointer". I haven't had time to troubleshoot other than trying to rebuild with various CFLAGS, which didn't help. I've been hoping it would magically get fixed in an update (which has happened before). Reproducible on all 4 of my AMD computers. Reproducible: Always Steps to Reproduce: 1. Attempt to start X/Attempt to start Wayland Actual Results: Crash Expected Results: Not Crash
Created attachment 767131 [details] lxdm log log from an lxde X11 computer attempting to run mesa-22.0.0 line 22: "free(): invalid pointer"
Created attachment 767132 [details] xorg log xorg log from lxde x11 computer
Created attachment 767133 [details] dmesg from the crash dmesg recovered from /var/log/dmesg After mesa/x11 crashes I have to ctrl-f2 and type blindly (since the screen no longer works) to get it to shutdown.
Created attachment 767134 [details] emerge info emerge --info from the laptop of the Excavator "twins" (this machine has ">media-libs/mesa-21.1.7" added to package.mask, other than that the config is identical and it is a binpkg consumer of the machine that generated the other logs.
Please file an issue upstream (at https://gitlab.freedesktop.org/mesa/mesa/) and link it here. Thanks!
Reported upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/6164
This has been fixed for me. I'll leave closing this to someone else because I'm not sure what to select (FIXED/INVALID). Turns out llvm-13+ with lto enabled doesn't actually work. After rebuilding without lto it works again. Older versions of mesa had LLVM_MAX_SLOT set to 12 so they did not use the newer broken llvm leading me to believe that it was mesa that was the problem.
I'm running stable mesa, but for me the linux-firmware-20220310 update started crashing X. Downgrading to 20220209 helped. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=4a597a3fd2a023203e6ebe9ebbb788be15de7def this is what happened in-between these version releases. So people with problems out there, check your linux-firmware too.