<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [i865G] stuck on render ring. Failed to reset chip: -19"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91126#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [i865G] stuck on render ring. Failed to reset chip: -19"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91126">bug 91126</a>
from <span class="vcard"><a class="email" href="mailto:goetzchrist@gmail.com" title="Götz <goetzchrist@gmail.com>"> <span class="fn">Götz</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=116932" name="attach_116932" title="graphics corruption">attachment 116932</a> <a href="attachment.cgi?id=116932&action=edit" title="graphics corruption">[details]</a></span>
graphics corruption
(In reply to Chris Wilson from <a href="show_bug.cgi?id=91126#c6">comment #6</a>)
<span class="quote">> It will just depend on which version of the libdrm headers it was built
> against. A fresh build of -intel will die, but at the time the package was
> built it was fine.</span >
Ah, interesting, thanks!
The bisecting finished showing 2.99.917-4-g986cb23 (Jan 6) "sna: Enable
mmap(wc) support by default", as the cause for the issue.
Additionally with the commit appeared graphics corruption, which persisted thru
2.99.917-17-ge53087e, but it was not present with 2.99.917-35-g6a6efd3 or
after.</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>