Comment # 9
on bug 76501
from Christian König
(In reply to comment #6) > interestingly also the last good commit produces the following log: > [ 7.573975] [drm] UVD initialized successfully. > [ 7.574210] [drm] Enabling audio 0 support > [ 7.574240] [drm] ib test on ring 0 succeeded in 0 usecs > [ 7.574263] [drm] ib test on ring 3 succeeded in 0 usecs > [ 17.730386] radeon 0000:01:00.0: GPU lockup CP stall for more than > 10000msec > [ 17.730390] radeon 0000:01:00.0: GPU lockup (waiting for > 0x0000000000000002 last fence id 0x0000000000000000) > [ 17.730393] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed > (-35). > [ 17.730397] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB > on ring 5 (-35). > > > So that seems unrelated to the issue at hand. Actually it is related, and now the behaviours makes perfect sense. Somewhere between 3.12 and your "last good" commit we have a patch that breaks UVD IB testing. But that isn't critical (3D still works fine) until the reset detection rework, cause after that one we try to get the UVD ring working again with each new IOCTL made to the card. Please give the attached patch a try, it clears the "needs_reset" flag if the IB test failed for some reason. So that if the initial bringup fails we won't try to get it working over and over again. Additional to that please bisect what commit breaks UVD IB testing between 3.12 and the "last good" commit and open up a new bug report for this issue. Thanks for the help, Christian.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
