<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NVC1] Display corruption when DP connector is reattached" href="https://bugs.freedesktop.org/show_bug.cgi?id=78439#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NVC1] Display corruption when DP connector is reattached" href="https://bugs.freedesktop.org/show_bug.cgi?id=78439">bug 78439</a> from <a class="email" href="mailto:skeggsb@gmail.com" title="Ben Skeggs <skeggsb@gmail.com>"> Ben Skeggs</a> <pre>(In reply to <a href="show_bug.cgi?id=78439#c18">comment #18</a>) > Yes it helps. DP screen is no longer black. > > The original issue has diminished too. The corrupted portion of the display > is three times narrower. But I haven't tested whether this patch helps or > one of the patches after that "bad revision" > 8894f4919bc43f821775db2cfff4b917871b2102. Well, the interesting thing is that the "bad" patch is doing nothing wrong. There is a change in behaviour in that we train the link at the highest rate supported between the display and the GPU instead of the bare minimum required to support the mode (something which is sensible for supporting MST, and which the NVIDIA binary driver also does). I've seen some odd behaviour on my GF108 with one particular DP->VGA adapter at the high bit rate too, which the NVIDIA binary driver is also effected by, however, I'm not sure it's the same as you're seeing. Mine is random, and works a lot of the time. The bad log *does* look like the same symptoms (the link trains successfully, but continually drops out afterwards). Would it be at all possible for you to try NVIDIA's driver, and see how it does? And, if it works, get a trace[1] of it initialising the screen? Hopefully in your case it works perfectly fine, and I can find something we're doing wrong for the high link rate. [1] <a href="http://nouveau.freedesktop.org/wiki/MmioTrace/">http://nouveau.freedesktop.org/wiki/MmioTrace/</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>