<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Screen flickering till it goes blank (console login, no X)" href="https://bugs.freedesktop.org/show_bug.cgi?id=108048#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Screen flickering till it goes blank (console login, no X)" href="https://bugs.freedesktop.org/show_bug.cgi?id=108048">bug 108048</a> from <a class="email" href="mailto:sten.heinze@gmx.de" title="Sten Heinze <sten.heinze@gmx.de>"> Sten Heinze</a> <pre>Over the last couple weeks I tried to bisect this problem (unfortunately a Core M is quite slow in compiling), but I could not reproduce the bug with any of the 14 kernels I compiled. In looking at every detail again, I noticed that I used Debian's 4.16 config for all kernels except the 4.17 to reproduce the bug. So I started the bisect again and compiled the first bisecting step twice, once with Debian's 4.16 and once with Debian's 4.17 config as starting point. (Then I removed Debian's signing key, and ran make olddefconfig.) And the different config causes the bug. I'll attach the diff. I'm not aware of an automated method to bisect configs. The most suspect config setting to me is CONFIG_SATA_MOBILE_LPM_POLICY, but I'm just guessing. I'd be happy to hear suggestions of how to make this more automated, and/or which config setting to prioritize in testing. (Also, even with a working kernel as far as this bug goes, I see "cpu pipe a fifo underrun" messages and flicker on shutdown - but maybe this should go in a different bug report?)</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> <li>You are the assignee for the bug.</li> </ul> </body> </html>