<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BAT] [SKL Gt4e] gem_exec_suspend@basic-s3 *ERROR* failed to enable link training"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97829#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BAT] [SKL Gt4e] gem_exec_suspend@basic-s3 *ERROR* failed to enable link training"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97829">bug 97829</a>
from <span class="vcard"><a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> <span class="fn">Jani Nikula</span></a>
</span></b>
<pre>(In reply to Jim Bride from <a href="show_bug.cgi?id=97829#c4">comment #4</a>)
<span class="quote">> How about we do a bisect before we start reverting changes? Blind
> dart-throwing may or may not work out, but I'd rather see a data-based
> decision being made.</span >
I wasn't suggesting the commits should be reverted from the tree, but rather
try without them to see if that makes a difference. A debug thing to try before
resorting to bisecting. Based on what's changed recently that could cause link
training errors rather than blind guessing.</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>