<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - System "forgets" about its DVI output" href="https://bugs.freedesktop.org/show_bug.cgi?id=90804#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - System "forgets" about its DVI output" href="https://bugs.freedesktop.org/show_bug.cgi?id=90804">bug 90804</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>The source will be the invalid EDID - we use it to confirm that you have a DVI connection. You can do a bisect to find which commit aggravated the issue for you. It might be something wrong in the comms protocol, e.g. switching to using GMBUS rather than GPIO, caused more frequent failure, but if the monitor always has returned invalid EDID at some point, then I'm not optimistic that it will be that. My guess is that the bisect would report that the offending commit is one that causes to try less hard to recover a broken EDID. But maybe the bisect would be a surprise and we find a genuine bug. Whilst I would appreciate a bisect, it may take a few days to perform, longer based on how long it takes for the invalid EDID to generate a disconnect. Overriding the EDID would take a couple of minutes to setup, so I can understand if you just did the workaround.</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>