<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@kms_chv_cursor_fail@pipe-[abc]-* - dmesg-warn - *ERROR* Overflow of CRC buffer, userspace reads too slow."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107885#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@kms_chv_cursor_fail@pipe-[abc]-* - dmesg-warn - *ERROR* Overflow of CRC buffer, userspace reads too slow."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107885">bug 107885</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>I think in the guc case, it's a bit more nuanced than our usual wedging. The
gpu claims to reset just fine, so our reset between tests, as a part of say
igt_require_gem(), appears to succeed. But it immediately hangs. I suppose if
we were wait for reset + idle, then we would know for certain.
However, handling the wedge gpu is a separate issue to cleaning up the debugfs
CRC iface. Emitting ERROR into dmesg instead of talking to the user trying to
use the fd that doesn't help the client detect errors.</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>