<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [sna] Output at last pipe stays black" href="https://bugs.freedesktop.org/show_bug.cgi?id=66494#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [sna] Output at last pipe stays black" href="https://bugs.freedesktop.org/show_bug.cgi?id=66494">bug 66494</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=66494#c16">comment #16</a>) > (In reply to <a href="show_bug.cgi?id=66494#c15">comment #15</a>) > > Do you mind repeating your testing and attaching Xorg & dmesg? Thanks. > > Sure, with or without --enable-debug=full? If you have the extra debug information, it will not hurt, so please do. At the moment, I just want to confirm that we stop doing the incorrect middle step of switching off a pipe. But after that I'll need a new idea, which will probably require more information again! > Meanwhile I've got a log with --enable-debug=full. Should I attach it? Yes, it will be useful to check the full details. > And I started to annotate (for better understanding) the log of my randr > client, which has things like crtc and output ids within. Would that help? > (I've verified that the problem exists with xrandr too.) Right now, I think the root cause of this issue is that the kernel decides there is no DVI/HDMI connection until the probe initiated by the randr client. The new DDX probe mechanism is designed to avoid doing a detection and modeset cycle and so requires the information determined by the kernel during boot to be accurate (and matches your expectations).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>