<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL] [regression] Random display flickering on Kernel 4.8 with dual-screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=97450#c31">Comment # 31</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [SKL] [regression] Random display flickering on Kernel 4.8 with dual-screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=97450">bug 97450</a> from <a class="email" href="mailto:direx@betriebsdirektor.de" title="Direx <direx@betriebsdirektor.de>"> Direx</a> <pre>(In reply to yann from <a href="show_bug.cgi?id=97450#c17">comment #17</a>) > Please re-test with Paulo's patch to apply memory workarounds for skylake: > <a href="https://patchwork.freedesktop.org/series/13548/">https://patchwork.freedesktop.org/series/13548/</a> I've been testing the rebased patch on 4.8.1 now for a while. I cannot confirm significant positive effects, however I haven't experienced any negative effects at all. The flickering might have become a little better, it's hard to tell. There are only very few screen flickers (once every ~30 minutes), so the machine is definitely usable. There still are the usual underruns: [15792.820143] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun [16070.293825] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [18877.276327] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=224491 end=224492) time 471 us, min 1192, max 1199, scanline start 1189, end 1227 [22438.333764] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [22692.923450] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun Also, suspend/resume cycles work fine. I can also confirm that drm-intel-nightly feels quite good. Maybe there finally is hope for Skylake users (more than one year after the platform's release).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>