Summary: | [vmwgfx] Invalid SVGA3D command: 1202 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Grief <iamgrief> |
Component: | Drivers/Gallium/vmwgfx | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
Severity: | critical | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Grief
2017-03-02 17:02:39 UTC
Hi, Do you used Ubuntu Zesty GNOME and then installed Plasma top of it or used the kubuntu (http://cdimage.ubuntu.com/kubuntu/releases/17.04/alpha-2/) which I guess comes with Plasma desktop. Thanks. I am using kubuntu, but not sure if that matters since these distros are only different by the set of preinstalled packages. You can always remove all of them and turn ubuntu to kubuntu or to lubuntu or whatever. Anyway, I think this is highly relevant: https://communities.vmware.com/thread/537924?start=0&tstart=0 Here is the same bug reported against kwin. But I suspect vmware itself being the only root cause of the issue. As I've said in the latest comment in the thread above, `export SVGA_VGPU10=0` helped me to workaround the issue. I can reproduce the bug but not able seeing the below dmesg: [ 103.849508] [drm:vmw_cmd_dx_destroy_shader [vmwgfx]] *ERROR* Could not find shader to remove. [ 103.849513] [drm:vmw_execbuf_process [vmwgfx]] *ERROR* Invalid SVGA3D command: 1202 Could you please provide complete dmesg and output of glxinfo Thanks, Hello Deepak, The issue still reproduces but the message is gone. I definetely saw it every time after that crash happened but it seems that after one of frequent KDE neon updates the message just gone. Anyway, here is a dropbox folder with output you asked: https://www.dropbox.com/sh/ig6v9tntqertwy7/AADSnRpdkHaYrx4yunOrTdEFa?dl=0 Just out of curiosity, you've said "I can reproduce the bug" does that mean that you reproduced it already or you meant that it is possible to reproduce it? Hello, I meant that I can reproduce it already. Thanks for providing the details. -- 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/889. |
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.