Enabling 3D acceleration in VMware Workstation 9.0.1 causes the system to freeze after starting Xorg. With 3D acceleration disabled things work fine using llvmpipe. This started happening after Mesa 8.0 (9.0 and git master). It does work for Arch Linux's mesa-9.0-1 packages, but not for mesa-9.0.1-1 or any of the manual builds I made. Relevant software versions: libdrm : 2.4.40-1 xorg-server : 1.13.0.902-2 linux : 3.6.9-1 xf86-video-vmware : 12.0.2-2
Removing assert(svga_texture(texture)->key.cachable == 0); at svga_resource_texture.c:207 seems to fix this...
(In reply to comment #1) > Removing assert(svga_texture(texture)->key.cachable == 0); at > svga_resource_texture.c:207 seems to fix this... The assertion should only affect debug builds. Does Xorg only crash on debug builds? The fact the assertion fails means we're trying to share a resource which wasn't created shareable by the state tracker... We set svga_texture(texture)->key.cachable = 0 on the next line, so things should still sort of work, bu I think this is the symptom of some other issue with resource creation.
It works with non-debug builds too. It could be that this is fixed in 9.1. I tried building the 9.0 branch, but I think I hit some 2D fallback mode in GDM and couldn't trigger the bug. Building Mesa 9.1 for Fedora 18 would be a way to test that at least.
Is this Fedora or are you using gnome-shell or anything clutter based? If so then, we know about this and it's already been fixed in master and backported to stable branches: https://bugzilla.redhat.com/show_bug.cgi?id=903413
I've been triggering it with GDM and Cinnamon. Closing this then.
I haven't tested Cinnamon, but iirc it was using Clutter and since Clutter uses GLX_INTEL_swap_event it had to be broken (all GLX_INTEL_swap_event using apps were freezing waiting for the sync event that would never come). So it should be fixed like everything else Clutter based but if you'll notice any problems, reopen and we'll take a closer look.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.