From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 67187] Radeon HD6950: UVD not responding, trying to reset the VCPU Date: Tue, 30 Jul 2013 17:43:12 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0570395955==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 356E7E611F for ; Tue, 30 Jul 2013 10:43:12 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0570395955== Content-Type: multipart/alternative; boundary="1375206192.Df7D0.24578"; charset="us-ascii" --1375206192.Df7D0.24578 Date: Tue, 30 Jul 2013 17:43:12 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67187 --- Comment #7 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. --1375206192.Df7D0.24578 Date: Tue, 30 Jul 2013 17:43:12 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 7 on bug 67187 from 
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.
--1375206192.Df7D0.24578-- --===============0570395955== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0570395955==--