<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [IVB] triple display issue"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59810#c52">Comment # 52</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [IVB] triple display issue"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59810">bug 59810</a>
from <span class="vcard"><a class="email" href="mailto:yangweix.shui@intel.com" title="shui yangwei <yangweix.shui@intel.com>"> <span class="fn">shui yangwei</span></a>
</span></b>
<pre>By co-work with Terence and QNAP(one company of taiwan), we have been sure that
this issue already gone on latest -next-queued kernel. I reproduced this issue
by using QNAP's older kernel. Both loop running 100 times and only the kernel
is different, you can clearly see the results:
Physical environment:
------------------------
1. two of the same monitor
2. Both DP plugged
3. I haven't changed the X in the machine which Terence shipped to me.
Test Results:
------------------------
1. older kernel:
One DP monitor will come up a warning message “DisplayPort no signal”, and
the other one always be OK. In my tests, the reproduce rate almost 10%(Totally
loop running 100 times X start and stop).
2. latest -next-queued kernel:
------------------------
Worked perfect. loop running 100 times X start and stop, all passed.But the
latest kernel has another issue(It's not related to this bug):
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [IVB regression dp] *ERROR* mismatch in adjusted_mode.flags (expected 1, found 0)"
href="show_bug.cgi?id=65287">Bug #65287</a> - [IVB regression dp] *ERROR* mismatch in adjusted_mode.flags
(expected 1, found 0)
So we get a conclusion: this bug has been fixed on latest kernels. We can close
it now.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>