Bug 61631

Summary:	VMWare driver hard crashes with recent mesa libgl upgrade
Product:	xorg	Reporter:	Jeremy M <jskier>
Component:	Driver/VMWare	Assignee:	linux-graphics-maintainer <linux-graphics-maintainer>
Status:	RESOLVED MOVED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	major
Priority:	high	CC:	aganders3, brandon, jskier, loic.yhuel, paul, unbeliver23
Version:	unspecified
Hardware:	All
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Jeremy M 2013-02-28 19:45:23 UTC

I upgraded to mesa-libgl 9.1 and found that ArchLinux hard crashes when starting X at loading GLX Module every time (it worked fine before the upgrade). Several ArchLinux users (https://bbs.archlinux.org/viewtopic.php?id=158721) are also reporting the same issue. No log information is provided, the crash completely locks up the VM. 

Not sure if this helps, but VirtualBox and other video drivers works fine. I can also run the vesa driver in VMWare Workstation just fine.

Running virtualized up-to-date ArchLinux 64-bit on a Windows 7 64bit workstation with VMWare Workstation 8. 

Other versions of software include:
xf86-video-vmware 13.0.0-1
svga-dri 9.1-2
xf86-input-vmmouse 13.0.0-1
open-vm-tools-modules 1:9.2.2-6
linux 3.8-2 (vanilla, was on 3.7, tried 3.8 from testing- no diff)

I'm not much of a developer but can help with providing more information if needed.

Comment 1 Jeremy M 2013-03-20 13:51:04 UTC

Updated importance. 

More reports here, along with xorg log: https://bbs.archlinux.org/viewtopic.php?id=158882

Comment 2 Paul Barker 2013-04-06 14:11:40 UTC

I've worked around this for now by recompiling xorg-server without the --enable-glx-tls argument to configure. On the arch linux forums a modified PKGBUILD script was provided: http://pastebin.com/q0hLj7M1

Knowing that it's something to do with glx-tls may help anyone looking to fix this.

Comment 3 Bill 2013-04-06 15:32:49 UTC

I don't know if it's importnant.
I report this for completness: https://bugs.archlinux.org/task/34638

Comment 4 Paul Barker 2013-04-11 13:06:21 UTC

(In reply to comment #2)
> I've worked around this for now by recompiling xorg-server without the
> --enable-glx-tls argument to configure. On the arch linux forums a modified
> PKGBUILD script was provided: http://pastebin.com/q0hLj7M1
> 
> Knowing that it's something to do with glx-tls may help anyone looking to
> fix this.

I'm an idiot. The fix was in mesa not xorg-server.

Comment 5 Jakob Bornecrantz 2013-04-11 19:01:57 UTC

*** Bug 61630 has been marked as a duplicate of this bug. ***

Comment 6 Jakob Bornecrantz 2013-04-15 13:00:58 UTC

Changing to the default assignee.

Comment 7 Loïc Yhuel 2013-04-23 09:32:11 UTC

(In reply to comment #3)
> I don't know if it's importnant.
> I report this for completness: https://bugs.archlinux.org/task/34638

It's the issue.
Building mesa with --with-llvm-shared-libs fixes the crash, but ArchLinux doesn't do it now since mesa needs to be built with an llvm2.3 snapshot (llvm-amdgpu-snapshot) for r600g, while shared llvm is still 2.2.

Comment 8 Michel Dänzer 2013-04-23 09:45:56 UTC

(In reply to comment #7)
> Building mesa with --with-llvm-shared-libs fixes the crash, but ArchLinux
> doesn't do it now since mesa needs to be built with an llvm2.3 snapshot
> (llvm-amdgpu-snapshot) for r600g, while shared llvm is still 2.2.

An LLVM 3.3 snapshot is only required for Mesa Git master. The Mesa 9.1 branch just requires some patches on top of LLVM 3.2 which should have negligible impact outside of the R600 LLVM backend, so they could be applied in the main LLVM packages. That's what Debian and I assume other distros do.

Comment 9 Martin Peres 2019-11-29 18:51:17 UTC

-- 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/xorg/driver/xf86-video-vmware/issues/5.

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.