<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#c7">Comment # 7</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:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=107762#c4">comment #4</a>)
<span class="quote">> However, if it is scheduler bug, I would assume this issue to be
> reproducible on any AMD GPU. Can you try running
> igt@amdgpu/amd_cs_nop@sync-fork-gfx0 in a loop for an hour or so?</span >
Hmm, 'fork' sounded suspicious, and indeed AFAICT this test uses the same
amdgpu_context_handle (and by extension the same DRM file descriptor) in
multiple processes spawned by fork(). I'm afraid Christian is going to explain
why that's not supported. :)
I suppose we should at least handle this more gracefully though, if possible.</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>