Summary: | gentoo on i7-4700MQ: after loading i915, console blurry with distorted colors or flickering | ||
---|---|---|---|
Product: | DRI | Reporter: | Adam Jirasek <libm3l> |
Component: | DRM/Intel | Assignee: | Paulo Zanoni <przanoni> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | chris, daniel, intel-gfx-bugs |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=81647 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
Adam Jirasek
2014-02-22 18:50:12 UTC
Created attachment 94598 [details]
dmesg, Xorg.0.log, xrandr and intel_reg_dumper.txt output
dmesg, Xorg.0.log, xrandr and intel_reg_dumper.txt output
This sounds like it's probably a modesetting problem. Perhaps Daniel or Chris can take a look or comment. Another hsw edp with funky colors. We have a few others of those ... Presuming this is indeed an i915 bug and reassigning this bug to Paulo. Can you please attach a jpeg/video which clearly shows the effect your seeing? Also retesting on latest drm-intel-nightly from http://cgit.freedesktop.org/~danvet/drm-intel/ can't hurt. (In reply to comment #3) > Another hsw edp with funky colors. We have a few others of those ... > > Presuming this is indeed an i915 bug and reassigning this bug to Paulo. > > Can you please attach a jpeg/video which clearly shows the effect your > seeing? Thanks for answer, I tried to make snapshot from another laptop which did not work well. Will need to use my camera, need to buy a new battery, will take a few days before I get it by mail, once I have a photo I'll upload it. (In reply to comment #4) > Also retesting on latest drm-intel-nightly from > http://cgit.freedesktop.org/~danvet/drm-intel/ can't hurt. I will check it out and let you know. (In reply to comment #4) > Also retesting on latest drm-intel-nightly from > http://cgit.freedesktop.org/~danvet/drm-intel/ can't hurt. Did not help, still the same. Created attachment 95307 [details]
Photo of screen with color distortion and correct screen
This picture shows a "normal" screen and photo of my screen with distorted colores. Algtough not really visible, the text on distrorted screen is blurry
Created attachment 95308 [details]
video with flicker
This video shows flicker of the screen. The flicker starts during boot when i915 is loaded. After kde starts, the kde background does not flicker.
In the case the screen flickers, there is no any color distortion and
text is sharp.
So after the boot the screen either goes to blurry, distorted mode and
flickering mode. Seems the screen after boot goes to one of the two modes.
(In reply to comment #9) > So after the boot the screen either goes to blurry, distorted mode and > flickering mode. Seems the screen after boot goes to one of the two modes. Is there a difference in the intel reg dumper output for these two? Created attachment 95739 [details]
intel reg dumper for "blurry" mode
Created attachment 95740 [details]
inltel reg dumper for "flickering" mode
Created attachment 95741 [details]
intel reg dumper for "blurry" mode done after some time after some time
(In reply to comment #10) > (In reply to comment #9) > > So after the boot the screen either goes to blurry, distorted mode and > > flickering mode. Seems the screen after boot goes to one of the two modes. > > Is there a difference in the intel reg dumper output for these two? I posted attachment of the intel reg dumper for "blurry" mode and "flickering" mode. There are two attachment for "flickering" mode, I took one right after the login to my KDE session (file intel_reg_dumper_flickering.txt), the second is taken about five mintues after that (intel_reg_flickering.txt1). I hope it helps Thanks Ok, few more things: - Can you please attach a picture of the grainy console, too? - Please boot latest drm-intel-nightly kernel with drm.debug=0xe added to your kernel cmdline and then attach the complete dmesg. - When you boot and the screen is in flicker mode, are there any messsage in dmesg about underruns? Same for the funny color mode. This only works with latest -nightly, released kernels dont have this debug feature implemented yet. Nothing extraordinary in the reg dumps afaics. Created attachment 96486 [details]
dmesg
Hello Daniel
Success!!
I compiled the lates drm-intel-nightly kernel, booted it with with drm.debug=0xe
and everythign works just fine, no more flicker, no more blurry screen with color distortion. Dmesg does not show any more "i915 : registered panic notifier"
Thanks for help! Not sure if you need anything more from me to find out what has changed, if you need just let me know
Adam Jirasek
You can attempt a reverse bisect (google has neat howtos, e.g. the kernel bisect from ubuntu) between the last broken kernel and drm-intel-nightly and so try to figure out which patch fixed your machines. Then we can backport it (if it's not an entire pile of patches ofc) so that all kernel will work properly. But the bug itself seems resolved in the latest code, so closing this. If you have the reverse bisect results simply open a new bug report linked to this. (In reply to comment #17) > You can attempt a reverse bisect (google has neat howtos, e.g. the kernel > bisect from ubuntu) between the last broken kernel and drm-intel-nightly and > so try to figure out which patch fixed your machines. Then we can backport > it (if it's not an entire pile of patches ofc) so that all kernel will work > properly. > > But the bug itself seems resolved in the latest code, so closing this. If > you have the reverse bisect results simply open a new bug report linked to > this. Hello I tried to upgrade my kernel to 3.16.0-rc5 (drm-intel-nighlty from 18th July 2014 ) and it seems the problem of blurry screen is back. The kernels 3.15.0-rc7 and 3.14.0-rc8 are working well. I will try to bisect it and see if I can find anything |
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.