https://bugs.freedesktop.org/show_bug.cgi?id=91305
Bug ID: 91305 Summary: When running JTR OpenCL tests: radeon 0000:01:00.0: ring 0 stalled for more than ...msec Product: Mesa Version: 10.6 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: devurandom@gmx.net QA Contact: dri-devel@lists.freedesktop.org
Created attachment 117050 --> https://bugs.freedesktop.org/attachment.cgi?id=117050&action=edit screenshot
I ran `john --test=0 --verbosity=5` from JohnTheRipper@d8cb9ce98acd26bd917dff4cbb54bdc14b7133f9, which made X crash.
I was dropped to VT1, where the messages "radeon 0000:01:00.0: ring 0 stalled for more than ...msec" and "radeon 0000:00:01.0: ring 3 stalled for more than ...msec" where flashing by. Afterwards messages of failed tests were logged (typewrote from attached screenshot): ``` AMD-Vi: Event logged [IO_PAGE_FAULT device=00:01.0 domain=0x0000 address=0x000000041145c040 flags=0x0050] [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 1 test failed (scratch(0x3010C)=0xCAFEDEAD) [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 2 test failed (scratch(0x3010C)=0xCAFEDEAD) [drm:cik_sdma_ring_test [radeon]] *ERROR* radeon: ring 4 test failed (0xCAFEDEAD) [drm:cik_resume [radeon]] *ERROR* cik startup failed on resume radeon 0000:00:01.0: ring 0 stalled for more than 10281msec [drm:cik_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35). ```
Since dmesg did not log these errors and journald is not accessible via journalctl ATM ("Error was encountered while opening journal files: Invalid argument"), I sadly cannot give you more accurate logs than the typewrote screenshot.