[Bug 109953] New: Intel Skylake HD520 Screen flickering

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=109953

            Bug ID: 109953
           Summary: Intel Skylake HD520 Screen flickering
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: dominik232 at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 143620
  --> https://bugs.freedesktop.org/attachment.cgi?id=143620&action=edit
dmesg output on booted Arch with 5.0.0-rc7-drm-intel-next-git-b4bf44d2dcbd and
enabled debug flag

== Machine details ==

Host: Aspire E5-574 V1.14
CPU: Intel i5-6200U (4) @ 2.700GHz
GPU: Intel Skylake GT2 [HD Graphics 520]
Memory: 15904MiB (2 * 8GB)
Resolution: 1920x1080

== Issue description ==

This problem was already solved for me once. When I bought this laptop I
immediately changed its hardware configuration. As far as I remember, that
problem was introduced when I extended RAM memory from 1x4GB to 2x8GB. Any
Linux OS with any kernel version (that supported Skylake graphics at all) had
that issue. System starts normally and image rendering is totally fine, but
sometimes I can see that some part of the screen is black for a small fraction
of a second. Sometimes I can see some little scratches and distortions too.
Back then I commented on existing, related bug
https://bugs.freedesktop.org/show_bug.cgi?id=94605#c87 I posted some dmesg
outputs and then Paulo Zanoni posted kernel patches I tested and first patch
was enough for me to not experiencing this issue anymore.

For now I modified my hardware configuration again by replacing harddrive (from
256G SSD to 512GB SSD). Unfortunately now the problem is back. I already
checked Windows and it works just fine without any flickering nor any
distortions at all. I don't know why it happens, maybe new harddrive consumes
more power or something.

Anyway there was also something that Paulo Zanoni suggested - sometimes first
row of pixels is broken while playing video. Back when we exchanged comments I
wasn't able to reproduce this issue, but on regular basis I started to notice
green line on top of the screen showin ocasionally when playing fullscreen
video.

== Steps to reproduce ==

Simply run any graphical environment with i915 and sooner or later I can
experience some broken frames. It feels like it happens the more often, the
more GPU resources are used - e.g. playing YouTube video and running Virtual
Machine with other OS makes it happening pretty often.
I doesn't seem like X.org related problem, because I can easily reproduce it on
the Wayland session.

== Logs ==

When this happens, this appears in dmesg output:

[ 2609.752028] [drm:intel_hpd_irq_handler [i915]] HPD interrupt storm detected
on PIN 6
[ 2609.752539] [drm] HPD interrupt storm detected on connector DP-1: switching
from hotplug detection to polling

The `dmesg.txt` attachment has full dmesg output. I added kernel parameters
drm.debug=0xe and log_buf_len=4M so maybe those logs would be any useful.

== Environments ==

I tried with few different kernel versions and distros and it's the same
everywhere:

Arch Linux: Linux 5.0
Arch Linux: Linux 5.0-rc7 (linux-drm-intel-next)
KDE Neon (Ubuntu?): Linux ~4.16
Debian Stable: Linux 4.8

== Summary ==

Since this is not any blocking sort of bug, it is really annoying and breaks
the overall experience.
I would be very grateful for help / fixes. From my side, if I only have some
time, I can make any tests, compile kernels, provide logs and so on.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190311/763266a0/attachment.html>