| Summary: | svga prints out command errors | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | John Kåre Alsaker <john.kare.alsaker> |
| Component: | Drivers/Gallium/vmwgfx | Assignee: | mesa-dev |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | critical | ||
| Priority: | medium | CC: | brianp, thellstrom |
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
John Kåre Alsaker
2014-04-30 16:31:08 UTC
Hi John, Sorry I missed this earlier. My first guess is you need to update your vmwgfx kernel module. Have you tried that? I'm not sure what you mean by updating the module. I assume that's done with kernel updates. Shouldn't mesa work on old kernels anyway? Also Linux 3.14.2, libdrm 2.4.54 now. Actually, This should work also with older kernels. However, you should see error messages in the kernel log if this occurs, could you post the output of dmesg on the bug? [ 3419.698902] [drm:vmw_cmd_compat_res_check] *ERROR* Could not find or use resource 0x00000000. [ 3419.698942] CPU: 2 PID: 1421 Comm: glxgears Not tainted 3.14.2-1-ARCH #1 [ 3419.698944] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/31/2013 [ 3419.698946] 0000000000000000 000000009111f5ac ffff8800a6ac3bc0 ffffffff8150984e [ 3419.698948] ffff8800bad00a08 ffff8800a6ac3c28 ffffffffa05008f0 ffff8800a6ac3c48 [ 3419.698950] ffffc900ffffffea 0000000000000000 ffff8801a2555de0 ffff8800a6ac3f10 [ 3419.698952] Call Trace: [ 3419.698960] [<ffffffff8150984e>] dump_stack+0x4d/0x6f [ 3419.698978] [<ffffffffa05008f0>] vmw_cmd_compat_res_check+0x2c0/0x310 [vmwgfx] [ 3419.698980] [<ffffffffa05010d3>] vmw_cmd_set_render_target_check+0x73/0xf0 [vmwgfx] [ 3419.698983] [<ffffffff814b36f6>] ? unix_stream_sendmsg+0x406/0x440 [ 3419.698986] [<ffffffffa05023a6>] vmw_execbuf_process+0x266/0xe10 [vmwgfx] [ 3419.698989] [<ffffffffa0502ffc>] vmw_execbuf_ioctl+0x6c/0xe0 [vmwgfx] [ 3419.699009] [<ffffffffa039acf2>] drm_ioctl+0x4f2/0x600 [drm] [ 3419.699013] [<ffffffffa0502f90>] ? vmw_execbuf_release_pinned_bo+0x40/0x40 [vmwgfx] [ 3419.699016] [<ffffffff811bb87d>] ? do_readv_writev+0x1bd/0x250 [ 3419.699019] [<ffffffffa05069de>] vmw_unlocked_ioctl+0x4e/0x80 [vmwgfx] [ 3419.699022] [<ffffffff811cd7d0>] do_vfs_ioctl+0x2d0/0x4b0 [ 3419.699025] [<ffffffff813fe4e1>] ? __sys_recvmsg+0x51/0x90 [ 3419.699027] [<ffffffff811cda31>] SyS_ioctl+0x81/0xa0 [ 3419.699031] [<ffffffff81517629>] system_call_fastpath+0x16/0x1b [ 3419.699032] [drm:vmw_cmd_check] *ERROR* Invalid SVGA3D command: 1050 Is this stopping 3D from working at all, or is it a one-time thing? What mesa branch is this? Is it self compiled or the built-in Archlinux mesa? /Thomas It's stopping all 3D from working.
It's the master branch since fe6a854477c2ed30c37c200668a4dc86512120f7. It's self compiled. Options:
./autogen.sh --prefix=/usr --with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers= \
--with-gallium-drivers=svga,swrast \
--with-egl-platforms=drm,x11,wayland \
--disable-gallium-llvm \
--disable-gallium-egl \
--enable-gbm \
--disable-glx-tls \
--enable-dri \
--enable-glx \
--enable-osmesa \
--enable-egl \
--enable-gles1 \
--enable-gles2 \
--enable-glx-tls \
--enable-xcb \
--enable-texture-float \
--enable-xa \
--enable-debug \
John, is this still an issue? -- 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/887. |
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.