Bug 68777 - [SNA TearFree] SDL fullscreen switch causes persistent display corruption
Summary: [SNA TearFree] SDL fullscreen switch causes persistent display corruption
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-31 01:27 UTC by xlinuxro
Modified: 2013-10-23 16:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (21.30 KB, text/plain)
2013-08-31 01:27 UTC, xlinuxro
no flags Details
A small program which reproduces the bug (893 bytes, text/plain)
2013-08-31 01:30 UTC, xlinuxro
no flags Details

Description xlinuxro 2013-08-31 01:27:02 UTC
Created attachment 84944 [details]
Xorg log

When SDL has a window open which is the same size as the screen and it switches to fullscreen mode it sometimes breaks the driver and an Xorg restart is required.  After the SDL application exits the whole screen continues to have corrupted display.  It seems like old data from the window is sometimes displayed.  Or sometimes just random image corruption appears.  It only happens if the non-fullscreen SDL window is exactly 1920x1080 (the size of my screen).  I noticed this problem when watching 1080p video with ffplay (from ffmpeg), but I have created a small program to reproduce the bug have attached it to this report.

Program versions (all from git):
Xorg: 1.14.2.902
xf86-video-intel: 2.21.15
libdrm: 2.4.46
pixman: 0.30.2
libXdamage: 1.1.4

$ uname -a
Linux namdle 3.10.10-namdle+ #5 SMP Fri Aug 30 21:12:29 EDT 2013 x86_64 GNU/Linux
Comment 1 xlinuxro 2013-08-31 01:30:28 UTC
Created attachment 84945 [details]
A small program which reproduces the bug
Comment 2 xlinuxro 2013-09-15 15:18:01 UTC
I have bisected this and found
  b7a96df9b0872867c823dc945add5be04d51c30a sna: Honour LinearFramebuffer
is the first bad commit.
Comment 3 xlinuxro 2013-10-23 16:20:37 UTC
As of the 2.99.905 snapshot I can no longer reproduce this problem.  Some commit between 2.99.904-b1ecadd and now must have fixed it.
Comment 4 Chris Wilson 2013-10-23 16:28:01 UTC
Sorry, I forgot to ask you to test. I had hoped that this was fixed accidentally as I had not worked out the root cause here.

Please reopen if this problem is merely hidden temporarily.


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.