my display was getting garbled for a moment very frequently. it looked like when the screen was getting refreshed then something was going wrong. git bisect gave <0f71979ab7fbd0c71c41c2798de3d33937915434> as the first bad commit, and after reverting it now display is not having that problem. lspci -k gives: "VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Subsystem: Foxconn International, Inc. Device 0d74 Kernel driver in use: i915" This is my bisect log: # bad: [e42391cd048809d903291d07f86ed3934ce138e9] Linux 4.0-rc6 # good: [b7392d2247cfe6771f95d256374f1a8e6a6f48d6] Linux 3.19-rc2 git bisect start 'v4.0-rc6' 'v3.19-rc2' '--' 'drivers/gpu/drm/i915/' # good: [d2182a660808d9053a605e3ebc8c46a323ec6e5d] drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV git bisect good d2182a660808d9053a605e3ebc8c46a323ec6e5d # bad: [36d21f4c557a2b18ed7c9d254060d4ca07a6c5c7] drm/i915/dsi: remove unnecessary dsi device callbacks git bisect bad 36d21f4c557a2b18ed7c9d254060d4ca07a6c5c7 # good: [72f95afa5faaf899f7344879b6ccd5f0cb271b28] drm/i915: Removed duplicate members from submit_request git bisect good 72f95afa5faaf899f7344879b6ccd5f0cb271b28 # good: [2844a9214759901f382086644842e39ad6f7d894] drm/i915: Use pipe_name() in the get_plane_config() functions git bisect good 2844a9214759901f382086644842e39ad6f7d894 # bad: [1b842c89bd8eb0e9619e1aba071c9a5529b7a179] drm/i915: Fix kzalloc() smatch warnings in get_initial_plane_config() git bisect bad 1b842c89bd8eb0e9619e1aba071c9a5529b7a179 # good: [8d360dffd6d8634868e433128d5178bea14cc42c] drm/i915: Specify bsd rings through exec flag git bisect good 8d360dffd6d8634868e433128d5178bea14cc42c # good: [1197b4f230fb7c8fe3a9b549596fe130b09a0db2] drm/i915: Balance context pinning on reset cleanup git bisect good 1197b4f230fb7c8fe3a9b549596fe130b09a0db2 # bad: [0f71979ab7fbd0c71c41c2798de3d33937915434] drm/i915: Performed deferred clflush inside set-cache-level git bisect bad 0f71979ab7fbd0c71c41c2798de3d33937915434 # good: [a7cbedec8317a5cacecb567674fdbc1c3fb22de8] drm/i915: Rename unpin_count to pin_count git bisect good a7cbedec8317a5cacecb567674fdbc1c3fb22de8 please let me know if you need any more information. Regards Sudip
Created attachment 114795 [details] [review] patch to revert after applying the attached patch (reverting the first bad commit) the display is not giving any more problems.
(In reply to sudip from comment #0) > git bisect gave <0f71979ab7fbd0c71c41c2798de3d33937915434> as the first bad > commit, and after reverting it now display is not having that problem. commit 0f71979ab7fbd0c71c41c2798de3d33937915434 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Jan 13 13:32:52 2015 +0000 drm/i915: Performed deferred clflush inside set-cache-level
Can you please attach both an Xorg.0.log and dmesg from after the corruption is exhibited?
Created attachment 114801 [details] dmesg
Created attachment 114802 [details] Xorg.0.log
(In reply to Chris Wilson from comment #3) > Can you please attach both an Xorg.0.log and dmesg from after the corruption > is exhibited? the corruption is only momentary, maybe just for a second or two. Xorg.0.log and dmesg are uploaded as attachments.
I suspect it is broken domain management in xf86-video-intel-2.21.6 (i.e. userspace is making a mistake that we just happened to fixup in the kernel). Could you please do a quick test with the latest driver? $ sudo apt-get build-dep xserver-xorg-video-intel $ git clone git://anongit.freedesktop.org/xorg/driver/xf86-video-intel $ cd xf86-video-intel $ ./autogen.sh --prefix=/usr $ make && sudo make install
(Less likely but also possible, is that the missed set-domain is in mesa. Less likely due to the longer path between mesa and the scanout.)
(In reply to Chris Wilson from comment #7) > I suspect it is broken domain management in xf86-video-intel-2.21.6 (i.e. > userspace is making a mistake that we just happened to fixup in the kernel). if it is fixed up in the kernel then I should not get the problem anymore if i boot with next-20150401. I will prefer to try with linux-next. And besides - "sudo apt-get build-dep xserver-xorg-video-intel" returns "Unable to find a source package for xserver-xorg-video-intel", i think that is because I am running ubuntu 13.04. > Could you please do a quick test with the latest driver? > > $ sudo apt-get build-dep xserver-xorg-video-intel > $ git clone git://anongit.freedesktop.org/xorg/driver/xf86-video-intel > $ cd xf86-video-intel > $ ./autogen.sh --prefix=/usr > $ make && sudo make install
The kernel is just one part of the driver stack, you ideally want to fix the bug at the source rather than penalize non-buggy components. It did find the source package because you don't have any source repositories (deb-src)
(In reply to Chris Wilson from comment #10) > It did find the source package because you don't have any source > repositories (deb-src) deb-src is mentioned in /etc/apt/sources.list
(In reply to sudip from comment #11) > (In reply to Chris Wilson from comment #10) > > > It did find the source package because you don't have any source > > repositories (deb-src) > deb-src is mentioned in /etc/apt/sources.list Maybe, but it wasn't used. Try enabling it, running apt-get update, then apt-get build-dep.
(In reply to Chris Wilson from comment #12) > (In reply to sudip from comment #11) > > (In reply to Chris Wilson from comment #10) > > > > > It did find the source package because you don't have any source > > > repositories (deb-src) > > deb-src is mentioned in /etc/apt/sources.list > > Maybe, but it wasn't used. Try enabling it, running apt-get update, then > apt-get build-dep. This is Ubuntu 13.04 and it is not supported any more. So I guess apt-get update will not work. In any case i have not tested with 4.1-rc series till now. I will check with this sunday's release and let you know. If the problem is still there I will see if i can install 14.04 in it.
Created attachment 116649 [details] video Just now checked with 4.1 and the problem still persists. Please check the attached mp4. It will show you what is happening. I will be very happy to assist you in debugging this problem. But since I am on ubuntu 13.04 and the support for it has been discontinued so I can not do any apt-get. But any patch to test on linux-next or v4.1 is ok.
(In reply to sudip from comment #14) > Created attachment 116649 [details] > video > > Just now checked with 4.1 and the problem still persists. Please check the > attached mp4. It will show you what is happening. > I will be very happy to assist you in debugging this problem. But since I am > on ubuntu 13.04 and the support for it has been discontinued so I can not do > any apt-get. But any patch to test on linux-next or v4.1 is ok. Chris said the problem is likely in your userspace, not kernel.
(In reply to Jani Nikula from comment #15) > Chris said the problem is likely in your userspace, not kernel. Yes, I think so. I installed ubuntu 14.04 in another harddisk with 4.1 and the problem doesnot show, but if i go back to 13.04 with same kernel the problem shows. Since 13.04 is not supported anymore I am marking it as invalid.
Thanks for the follow-up!
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.