https://bugs.freedesktop.org/show_bug.cgi?id=107655
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org |org Status|RESOLVED |REOPENED QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org |org Component|Drivers/Gallium/r300 |Drivers/Gallium/swr Resolution|NOTOURBUG |---
--- Comment #5 from Michel Dänzer michel@daenzer.net --- (In reply to Sergey Kondakov from comment #4)
I don't know the actual reason of the crash but the guys there figured out that the crash was coming from AVX instruction in Mesa's SWR code. The affected machine does not support any kind of AVX, so it threw out the error. But it's unclear why SWR even been trying to initialize during the load of r300_dri.
I think it's the combination of two things:
* All Gallium drivers are linked into a single binary (so-called mega-driver)
* SWR is compiled with AVX support and has initializers which are automatically executed when the above binary is dlopen()ed.
Until there's a solution for this, SWR cannot be enabled in a build which has to run on non-AVX capable CPUs.