<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected BYT] complete freeze after: drm/i915/vlv: WA for Turbo and RC6 to work together"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88012#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected BYT] complete freeze after: drm/i915/vlv: WA for Turbo and RC6 to work together"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88012">bug 88012</a>
from <span class="vcard"><a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> <span class="fn">Andy Furniss</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=88012#c24">comment #24</a>)
<span class="quote">> That bisect appears to be a red herring though.</span >
As someone who is also affected by this I can well believe that.
Though I wasn't bisecting Kernel at the time (and still haven't) I've had runs
of 12 hours without a lock - the same setup locked < 2H next day.
Having test quite hard since this bug was filed with released kernels I am
99.9% sure the issue is between 3.16.7 and 3.17.0.
I also think that gpu load is needed - I use LFS and have compiled plenty on
bad kernels + mprime torture test and never locked.
Do you have any guesses of what the bad commit could be between those - if you
have then people could test that and someone will hopefully call bad quickly
then extended test on the one before.</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>