| Summary: | [ivb gt1] display getting garbled | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | sudip <sudipm.mukherjee> | ||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Status: | CLOSED INVALID | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | intel-gfx-bugs, sudipm.mukherjee | ||||||||||
| Version: | unspecified | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
sudip
2015-04-01 03:52:31 UTC
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.