<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Native screen resolution not working correctly over HDMI LSPCON (i915)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107503#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Native screen resolution not working correctly over HDMI LSPCON (i915)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107503">bug 107503</a> from <a class="email" href="mailto:nicholas.stommel@gmail.com" title="Nicholas Stommel <nicholas.stommel@gmail.com>"> Nicholas Stommel</a> <pre>Fredrik made a good point about why we might be having difficulties reproducing the bug with the drm.debug=0x1e parameter: (In reply to Hector Martin from <a href="show_bug.cgi?id=107503#c21">comment #21</a>) > If the issue is timing-related (which is quite likely given the randomness > and the error message associated with it) then it's quite possible that > enabling additional debugging might slow things down enough to stop it from > happening. This very well might be a timing related bug, as the drm.debug=0x1e parameter writes hundreds of lines of feedback to the kernel log very quickly. I can confirm this bug is very much indeed still a problem. I have posted my dmesg sans the debugging parameter as well as the output of xrandr --verbose from a good and bad boot. The bug is *very* reproducible without adding any extra kernel parameters on Fedora 28 and Ubuntu 18.04. I will do my best in attempting to find at which point the bug started happening,</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>