[Mesa-dev] [Bug 107655] X segfaults on startup in r300_dri.so, making system unusable

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107655

GitLab Migration User  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |MOVED

--- Comment #8 from GitLab Migration User  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/197.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 107655] X segfaults on startup in r300_dri.so, making system unusable

2018-08-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107655

Michal Srb  changed:

   What|Removed |Added

 CC||michal...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107655] X segfaults on startup in r300_dri.so, making system unusable

2018-08-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107655

--- Comment #7 from mirh  ---
(In reply to Ilia Mirkin from comment #6)
> The intention (and original function) was that this would be safe -- swr
> would check for AVX support and load the relevant library (libAVX/libAVX2),
> or bail on load.
> 
> Something must have regressed in there and no one noticed since AVX has
> become fairly common.

Or, I mean, more easily it might be a problem with its special build root?
AVX might be common nowadays, but not *that* much (especially considering all
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mesa-git#n48

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107655] X segfaults on startup in r300_dri.so, making system unusable

2018-08-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107655

--- Comment #6 from Ilia Mirkin  ---
The intention (and original function) was that this would be safe -- swr would
check for AVX support and load the relevant library (libAVX/libAVX2), or bail
on load.

Something must have regressed in there and no one noticed since AVX has become
fairly common.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107655] X segfaults on startup in r300_dri.so, making system unusable

2018-08-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107655

Michel Dänzer  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  ---
(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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev