Summary: | vmwgfx: atom (electron-based app) causes corruption, hangs | ||
---|---|---|---|
Product: | Mesa | Reporter: | David Cuthbert <dacut> |
Component: | Drivers/Gallium/vmwgfx | Assignee: | mesa-dev |
Status: | RESOLVED WORKSFORME | QA Contact: | mesa-dev |
Severity: | major | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
David Cuthbert
2018-05-28 07:18:41 UTC
NB: I'm not sure if this belongs in the Mesa or DRI queue; neither has an exact match for the vmwgfx component. In any case, I'm referring to this tree: https://cgit.freedesktop.org/mesa/vmwgfx/ (In reply to David Cuthbert from comment #0) > I'm filing this currently so I have a place to keep notes on this bug. > > Running the atom text editor under various OSes (tried Linux Mint 18.3, > Ubuntu 18.04, and currently using Fedora 28) results in minor screen > glitches, eventually followed by drawing going completely haywire. I > recompiled vmwgfx.ko from the current HEAD which resulted in fewer glitches, > but it never completely goes away. > > The hangs are always immediately preceded by: > [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command "(null)" causing device > error. > [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer offset is 28 > [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command size is 24 > Hi David, thanks for the bug report. Do you see the command buffer error with the new top of the tree vmwgfx only ? I tried to reproduce this bug with clean Ubuntu 18.04 and Atom installed from software center. I see that Atom text editor will be unresponsive but couldn't see the kernel command buffer errors. Will try with Fedora 28 later. FWIW, no apparent problems on Fedora Rawhide with 4.18.0-rc0. /Thomas Note that it takes some fiddling to reproduce this currently (the exact trigger isn't known). I can go hours without seeing this issue. I've been banging my head against the wall trying to get my extra logging to work -- finally realized yesterday that vmwgfx.ko is being loaded in initramfs and not from my filesystem. I'm attempting to reproduce it now with a rebuilt initramfs. Unable to duplicate, at least with new top of tree mesa and vmware drivers. |
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.