Comment # 7
on bug 67187
from Harald Judt
Further tests show: * the 0xCAFEDEAD seems to have been a one-time error that usually does not occur * in case of problems, "UVD not responding" does not always appear and is successfully initialized, but the ring 5 error usually does radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000008 last fence id 0x0000000000000006) [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35). * it does not always hang when suspending, yet resume might still fail * enabling pm_async makes suspend/resume fail sometimes with "uvd not responding", while the process appears to be quite stable with pm_async deactivated (may only be harder to reproduce, still needs more testing) * hibernate/resume will fail with pm_async deactivated sometimes, and pretty reliably with pm_async enabled Pretty weird...
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
