<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Video cutout on Kaby Lake U processors." href="https://bugs.freedesktop.org/show_bug.cgi?id=107543#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Video cutout on Kaby Lake U processors." href="https://bugs.freedesktop.org/show_bug.cgi?id=107543">bug 107543</a> from <a class="email" href="mailto:dan.booker@adder.com" title="Dan Booker <dan.booker@adder.com>"> Dan Booker</a> <pre>(In reply to Rodrigo Vivi from <a href="show_bug.cgi?id=107543#c18">comment #18</a>) > Hi Dan, > > The i915.enable_psr=0 is not doing anything actually. First because PSR is > an eDP only feature and you have no eDP, according to your display_info. But > also becuase i915.enable_psr=0 is no op because i915.enable_psr defaults to > 0 anyways by default in all current platforms. > > Maybe it was the fbc the one you thought it is helping. But anyways, if you > still see the issue with that =0 it is only masking the real issue. So could > you please retest latest drm-tip without any modified parameter? > > Also, question, how many memory do you have on your system? > I wonder if this series would help you: > <a href="https://patchwork.freedesktop.org/series/46481/">https://patchwork.freedesktop.org/series/46481/</a> > > Also, what is the CPU/GPU load that you are using? Media? 3D? See above for output with drm-tip and no parameters set. On the Celeron system I'm currently using I have a single stick of 4GB DDR4-2133 but we also see the error on the i3 system with 2 sticks of 4GB DDR4-2133. The easiest way to trigger the error is to create high CPU load by rebuilding a linux kernel using make. However the error has also occurred when the system is idling. Our intended load is using the CPU to decode a video stream and GPU to display it a 2160p which can also trigger the issue. I will take a look at the suggested patch. Dan</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>