<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - [bdw edp] Screen Flickering" href="https://bugs.freedesktop.org/show_bug.cgi?id=91393#c134">Comment # 134</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - [bdw edp] Screen Flickering" href="https://bugs.freedesktop.org/show_bug.cgi?id=91393">bug 91393</a> from <a class="email" href="mailto:gdm85frd@iragan.com" title="gdm85 <gdm85frd@iragan.com>"> gdm85</a> <pre>@Mika Kahola I can reproduce the original problem here with a HD 5500 and the panel of a Dell Chromebook 13 7310. I was reading <a href="https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522922">https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522922</a> and noticed this patch <a href="https://patchwork.freedesktop.org/patch/66697/">https://patchwork.freedesktop.org/patch/66697/</a> which unfortunately I did not manage to apply on top of the stable Ubuntu-4.15.0-66.75 kernel as I could not understand how invalidation of the train set works in the more recent tree. The training logic has changed quite a bit. See also my comment here: <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/comments/18">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/comments/18</a> All the hints make me think that if I could somehow use the logic which was there in kernel v4.4.0, and which perhaps the mentioned patch would cover, then I could use again this GPU with latest kernels. I am available for trying patches and submitting the necessary relevant logs as requested; I did not provide any so far because I saw that this bug is closed.</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>