Bug 90916 - [965gm] glitches
Summary: [965gm] glitches
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-09 17:03 UTC by Mads Villadsen
Modified: 2017-02-24 07:16 UTC (History)
1 user (show)

See Also:
i915 platform: I965GM
i915 features:


Attachments

Description Mads Villadsen 2015-06-09 17:03:29 UTC
I am seeing graphics corruption on a Dell Lattitude 1525 laptop. It shows as lots of horizontal lines across windows. Not so often when the windows are maximized it seems.

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)

xorg-x11-drv-intel-2.99.917-10.20150526.fc22.x86_64

cat /sys/kernel/debug/dri/0/i915_swizzle_info

bit6 swizzle for X-tiling = bit9/bit10/bit11
bit6 swizzle for Y-tiling = bit9/bit11
DDC = 0x000f0002
DDC2 = 0x00000000
C0DRB3 = 0x0000
C1DRB3 = 0x0000
L-shaped memory detected
Comment 1 Mads Villadsen 2015-06-12 16:49:52 UTC
Did an update to xorg-x11-drv-intel-2.99.917-11.20150603.fc22.x86_64 and the problem is still there.

In the beginning it appears mostly in the top of windows but never in the Gnome header. If a window starts out maximized and is then resized smaller the graphics get more corrupt.
Comment 2 Mads Villadsen 2015-06-15 16:35:27 UTC
With updates to driver and kernel the problem seems to be practically gone. I have still seen image corruption in for instance Firefox under certain circumstances when resizing, maximing, restoring, dragging, scrolling window and opening multiple tabs. Not easy to reproduce.

xorg-x11-drv-intel-2.99.917-11.20150603.fc22.x86_64
kernel-4.0.5-300.fc22.x86_64
Comment 3 Chris Wilson 2015-06-16 16:34:36 UTC
Hmm, so I got out my t61 today and being playing about with different kernels + xf86-video-intel.git to see if I can replicate this. Sadly nothing with LinuxMint.
Comment 4 Chris Wilson 2015-06-16 17:01:26 UTC
My presumption here is that it is mmap(wc) playing up.

diff --git a/src/sna/kgem.c b/src/sna/kgem.c
index 0178df7..11e80f9 100644
--- a/src/sna/kgem.c
+++ b/src/sna/kgem.c
@@ -83,7 +83,7 @@ search_snoop_cache(struct kgem *kgem, unsigned int num_pages, unsigned flags);
 #define DBG_NO_FAST_RELOC 0
 #define DBG_NO_HANDLE_LUT 0
 #define DBG_NO_WT 0
-#define DBG_NO_WC_MMAP 0
+#define DBG_NO_WC_MMAP 1
 #define DBG_NO_BLT_Y 0
 #define DBG_NO_SCANOUT_Y 0
 #define DBG_NO_DETILING 0

is perhaps the simplest way of testing.
Comment 5 Mads Villadsen 2015-06-16 18:13:21 UTC
So I should apply that patch and recompile the intel driver?
Comment 6 Chris Wilson 2015-06-16 19:27:03 UTC
Yes, change that line in xf86-video-intel.git and see if that confirms mmap(wc) is the sore point.
Comment 7 Mads Villadsen 2015-06-23 20:27:12 UTC
That seems to have made a big difference so far but it is difficult to test since it only appears sporadically.
Comment 8 yann 2017-02-24 07:16:39 UTC
(In reply to Mads Villadsen from comment #7)
> That seems to have made a big difference so far but it is difficult to test
> since it only appears sporadically.

timeout, closing this old bug w/o further activity assuming it should be fixed by now.

If this still occurring, please ensure that you use latest kernel, xf86-video-intel version - alternatively you may consider to use Glamor/modesetting with latest Mesa version - and the fill a new bug with gpu error dump and kernel log.


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.