Summary: | Host application crash on vmware fusion 7 in vmw_swc_flush | ||
---|---|---|---|
Product: | Mesa | Reporter: | Nicholas Yue <yue.nicholas> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | 8.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Nicholas Yue
2014-11-09 17:31:01 UTC
From the description I assume the submitter is using mplayer. I've done the following steps and could not reproduce this issue: 1. download and build mplayer from http://www.mplayerhq.hu 2. download an mpeg2 clip from http://support.apple.com/en-us/HT1425 3. ran: mplayer sample_mpeg2.m2v The clip seems to run fine. My system configuration: Fedora 20 64-bit MESA 10.4 Please provide more details in terms of steps to reproduce and the system configuration. Hi Sinclair, The application mplay (not mplayer) is from the Houdini suite of software by Side Effects http://www.sidefx.com/index.php?option=com_download&task=apprentice&Itemid=208 You can use the Apprentice (free) version to verify the crash when launching mplay, gplay or houdini itself Mesa version was already included in the original report OpenGL version string: 2.1 Mesa 8.0.4 My OS in question is Ubuntu 12.04.5 x64 Kernel is : Linux ubuntu 3.13.0-32-generic #57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Cheers I am using the most recent version of VMWare Fusion 7 on OS X Yosemite to host Ubuntu 12.04.5 x64 and it only provides Mesa3D at version 8.0.4 not the 10.4 you are testing with. Is there an update in VMWare Fusion 7 I should get and retest before debugging further ? Thanks. I can now reproduce this issue with MESA 8.0.4 and MESA 9.0. This seems to work fine with MESA 10.1.3. I'll track down the root cause of this. Do you see this "vmw_ioctl_command error Invalid argument." in the terminal when you run mplay-bin? (In reply to Sinclair Yeh from comment #4) > Thanks. I can now reproduce this issue with MESA 8.0.4 and MESA 9.0. This > seems to work fine with MESA 10.1.3. > > I'll track down the root cause of this. > > Do you see this "vmw_ioctl_command error Invalid argument." in the terminal > when you run mplay-bin? No. I don't recall seeing "vmw_ioctl_command error Invalid argument." Cheers (In reply to Sinclair Yeh from comment #4) > Do you see this "vmw_ioctl_command error Invalid argument." in the terminal > when you run mplay-bin? Those messages happen when a mix of downstream & upstream modules happen. Namely: - Both downstream vs upstream modules have the same name. Thus userspace loads either one. - Upstream modules require another module which is available as upstream & downstream. In some cases via alias. One could fix this, by stripping/avoiding the build of the downstream module when the kernel is new enough/has the equivalent module. Please kindly forward this to the relevant team/person :) This issue has been fixed by ce9a3a8997d86f3bf387f23578972acb5b16ac4ac, which is in MESA 10.1.0 onwards. The fix is not trivial to back port to MESA 8.0.4 and so the easiest way is to wait until the next update of Ubuntu 12.04. There is a temporary workaround if waiting for the next update is not an option. 1. Download MESA 10.1.2 from freedesktop 2. ./configure --prefix=<PATH OF YOUR CHOOSING> --with-gallium-drivers=svga --enable-xa --disable-dri3 3. make install After the above is done, before running mplay-bin, do an "export LD_LIBRARY_PATH=<PATH OF YOUR CHOOSING FROM EARLIER>/lib" (In reply to Sinclair Yeh from comment #7) > This issue has been fixed by ce9a3a8997d86f3bf387f23578972acb5b16ac4ac, > which is in MESA 10.1.0 onwards. The fix is not trivial to back port to > MESA 8.0.4 and so the easiest way is to wait until the next update of Ubuntu > 12.04. > > There is a temporary workaround if waiting for the next update is not an > option. > 1. Download MESA 10.1.2 from freedesktop > 2. ./configure --prefix=<PATH OF YOUR CHOOSING> --with-gallium-drivers=svga > --enable-xa --disable-dri3 > 3. make install > > After the above is done, before running mplay-bin, do an "export > LD_LIBRARY_PATH=<PATH OF YOUR CHOOSING FROM EARLIER>/lib" Thanks Sinclair, I have built Mesa 10.1.2 as a temporary solution and the Houdini tools are now running fine on VMWare Fusion 7. Cheers |
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.