<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> <span class="fn">Ville Syrjala</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [bisected HSW ULT]igt/testdisplay -d 16 cause balckscreen with HDMI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69404">bug 69404</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [bisected HSW ULT]igt/testdisplay -d 16 cause balckscreen with HDMI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69404#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [bisected HSW ULT]igt/testdisplay -d 16 cause balckscreen with HDMI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69404">bug 69404</a>
from <span class="vcard"><a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> <span class="fn">Ville Syrjala</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=69404#c4">comment #4</a>)
<span class="quote">> > Yes, I think a bisect would be really useful here. Ville discovered hard
> > hangs when doing modest on HSW, but this seems to be a different issue. And
> > I have no idea what's really going on here ...
>
> I have finished bisect, the result shows:
>
> e6e792092e816bea0797995c886fb057c91d4546 is the first bad commit
> commit e6e792092e816bea0797995c886fb057c91d4546
> Author: Ville Syrj盲l盲 <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
> Date: Fri May 31 15:23:41 2013 +0300
>
> drm/edid: Add both 60Hz and 59.94Hz CEA modes to connector's mode list
>
> Sorry for take some time, the amount of the steps is a little large. What's
> more, I think the problem may be caused by this mode:
> CRTS(3):[12] 1280x720 60 1280 1390 1430 1650 720 725 730 750 0x5 0x40 74250</span >
Most likely that mode was already present before your bisect commit. It could
be the 1280x720 mode with 72.176 MHz clock.
But if the monitor claims to be CEA compatible, then according to the spec it
must support both frequencies. Do you have another monitor you can try with the
same failing mode?
Please attach the EDID for the monitor, and a full log w/ drm.debug=0xe which
includes the failing modeset could be helpful.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>