On Sat, Jul 04, 2020 at 11:19:49AM -0400, Joe Gidi wrote: > >> Is there anything else I can try to resolve this instability? Any other > >> info I can provide? > > > > if you look in dmesg when it occurs you may see a message along the > > lines of > > > > [drm] *ERROR* ring gfx timeout, signaled seq=1417, emitted seq=1418 > > > > running top and looking at the wait channels may show 'dmafence' > > or one of the other drm wait channels. > > Hi Jonathan, > > Thank you for your work on this driver! From reading the commit messages, > it looks like it has been a monumental effort. > > After playing around for quite a while, I was finally able to capture some > output. The dmesg buffer overflowed with thousands of lines of the same > error, finally ending with: > > [drm] *ERROR* Failed to initialize parser -88! > [drm] *ERROR* Failed to initialize parser -88! > [drm] *ERROR* Failed to initialize parser -88! > [drm] *ERROR* ring gfx timeout, signaled seq=22, emitted seq=22 > [drm] *ERROR* Process information: process pid 0 thread Xorg pid 17620 > [drm] *ERROR* ring comp_1.0.1 test failed (-60) > > Please let me know if I can provide any other information. Would a > donation of a video card be helpful to you?
Thanks for the offer but this kind of problem can be reproduced on other amdgpu parts. With both the linux 4.19 based drm and the recent port of linux 5.7 drm 'piglit run quick <dir>' will cause a ring timeout/hang. piglit being a series of OpenGL/Mesa regression tests. piglit finishes with inteldrm.
