<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station" href="https://bugs.freedesktop.org/show_bug.cgi?id=71267#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station" href="https://bugs.freedesktop.org/show_bug.cgi?id=71267">bug 71267</a> from <a class="email" href="mailto:tprevite@gmail.com" title="Todd Previte <tprevite@gmail.com>"> Todd Previte</a> <pre>So a 500us delay in retries alleviates the problem? Interesting. That would seem to indicate that the sink device rather slow to get back to a ready state after responding to a transaction. As I indicated above, the only issue with a high retry time is ensuring that operations like link training can occur within the specified time period. An isolated defer would be a single AUX_DEFER received from a sink device for a request from the source. For example, if you ask to read the status bits for link training out of the DPCD and the sink replies with an AUX_DEFER because it's busy servicing another request. You could then wait (in your case, 500us), resend the same request, and receive a valid response. That would be a single, isolated defer. As for your docking station question, you'd have to refer to the manufacturer's information or contact their support team. I'm sure there's multiple ways they could have constructed the hardware and I don't want to speculate on it without having exactly knowledge. -T</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> </ul> </body> </html>