<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Constant "Resetting rcs0 for hang on rcs0" and machine lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111805#c34">Comment # 34</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Constant "Resetting rcs0 for hang on rcs0" and machine lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111805">bug 111805</a>
from <span class="vcard"><a class="email" href="mailto:kenny@panix.com" title="Kenneth C <kenny@panix.com>"> <span class="fn">Kenneth C</span></a>
</span></b>
<pre>(In reply to Lakshmi from <a href="show_bug.cgi?id=111805#c33">comment #33</a>)
<span class="quote">> Kenneth, Do you mean to say the issue is not seen on Linus' tip?</span >
No that's not what I'm saying, please re-read the comments carefully.
Linus' tip has the drm-next of mid-September pushed to it in commit
574cc4539762; it was this commit that has rendered i915 DRM completely
hang-ridden and unstable for me and others. My instructions above show how to
UNMERGE the drm-next changes so that if someone needs to run Linus' tip (or
several released kernels) for whatever upstream benefit yet go back to the
working DRM/i915.
Apparently you guys were warned of this issue regularly occurring by what
appears to be an Intel Mesa(?) developer, and he'd even bisected it to a range
of commits: <a class="bz_bug_link
bz_status_NEW "
title="NEW - (Only partly recoverable) GPU hangs in (multi-context) SynMark HDRBloom & Multithread tests with Iris driver"
href="show_bug.cgi?id=111385#c12">https://bugs.freedesktop.org/show_bug.cgi?id=111385#c12</a>
... and while no resolution to that bug was given, and apparently easily
reproducible, yet this was merged into the Linux tree. Those commits must be in
Intel-local repos, as I can't see those commits in any git repo I have.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>