[Mesa-dev] [Bug 46458] New: Guest screen is corrupted after host screen locked

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 22 06:24:59 PST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=46458

             Bug #: 46458
           Summary: Guest screen is corrupted after host screen locked
    Classification: Unclassified
           Product: Mesa
           Version: 8.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Other
        AssignedTo: mesa-dev at lists.freedesktop.org
        ReportedBy: ostash at ostash.kiev.ua


I'm running Gentoo Linux under VMware Player 4.0.2 build-591240 on Windows XP.

Guest is running:

kernel 3.2.5 (provides vmwgfx 2.3.0.0)
mesa-8.0 (build with gallium and xatracker enabled)
xf86-video-vmware from today git (so I got xatracker-based driver)
xorg-server-1.11.4

Everything works perfectly and I'm able to get accelerated OpenGL.

However, if I lock host screen (Win+L) and unlock it, I got guest screen
corrupted and unusable.

I've checked following situations:

1) vmwgfx kenel module loaded, Xorg isn't started - works fine
2) vmwgfx kenel module loaded with enable_fbdev, Xorg isn't started - works
fine
3) vmwgfx kenel module loaded, Xorg is working and is on screen - FAIL
4) vmwgfx kenel module loaded, Xorg is working and VT on screen - FAIL
5) vmwgfx kenel module loaded with enable_fbdev, Xorg is working and is on
screen - FAIL
6) vmwgfx kenel module loaded with enable_fbdev, Xorg is working and VT on
screen - FAIL

So for me look like something isn't reinitialized correctly in xorg driver
after host screen is unlocked.

Only possible way to fix screen corruption is to shutdown/kill X server. VT is
redrawn correctly in few seconds.

I'll be glad to provide any other information/backtraces/debug outputs if
needed.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the mesa-dev mailing list