Comment # 7
on bug 107762
from Michel Dänzer
(In reply to Martin Peres from comment #4) > 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? 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.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
