<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Intel GFX CI] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107762#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Intel GFX CI] *ERROR* ring sdma0 timeout, signaled seq=137, emitted seq=137"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107762">bug 107762</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>(In reply to Lucas Stach from <a href="show_bug.cgi?id=107762#c3">comment #3</a>)
<span class="quote">> We've just fixed a bug in the scheduler timeout handling, which might lead
> to the timeout worker being armed for the wrong job.
>
> Does this issue still occur on a recent kernel with
> 4823e5da2ea9061011242db81334d6ebbd2ed0a5 (drm/scheduler: fix timeout worker
> setup for out of order job completions) present?</span >
I see! We are using drmtip, which does not yet include
4823e5da2ea9061011242db81334d6ebbd2ed0a5. I assume we'll get it very soon, but
given the reproduction rate of the issue, we will not know for sure if the
issue is fixed for at least another month (it happened twice in a week, 2% of
our runs).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>