From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67187] Radeon HD6950: UVD not responding, trying to reset the VCPU
Date: Mon, 05 Aug 2013 07:31:22 +0000 [thread overview]
Message-ID: <bug-67187-502-sKy8ykQ84v@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67187-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67187
--- Comment #8 from Harald Judt <h.judt@gmx.at> ---
Finally! I've pulled
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11 for rc3 and
reliability of suspending and hibernating has improved *a lot*. The machine
will even hibernate and resume with successfully with pm_async=1 now. There was
only one time that a similar error message occurred in 1 out of 18 attempts,
this time only slightly different from the other errors:
[ 4379.361691] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 4379.361692] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000026
last fence id 0x0000000000000024)
[ 4379.361693] [drm:r600_uvd_ib_test] *ERROR* radeon: fence wait failed (-35).
[ 4379.361695] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).
Let's see how more often this will occur. Apart from this one failure (I hope
it was only bad luck) it works very well now. Thanks for the improvements.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1969 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-08-05 7:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 19:18 [Bug 67187] New: Radeon HD6950: UVD not responding, trying to reset the VCPU bugzilla-daemon
2013-07-23 8:46 ` [Bug 67187] " bugzilla-daemon
2013-07-23 9:00 ` bugzilla-daemon
2013-07-23 18:01 ` bugzilla-daemon
2013-07-25 7:06 ` bugzilla-daemon
2013-07-30 8:20 ` bugzilla-daemon
2013-07-30 8:29 ` bugzilla-daemon
2013-07-30 17:43 ` bugzilla-daemon
2013-08-05 7:31 ` bugzilla-daemon [this message]
2013-08-05 10:02 ` bugzilla-daemon
2013-08-05 11:37 ` bugzilla-daemon
2013-08-05 13:20 ` bugzilla-daemon
2013-08-07 10:12 ` bugzilla-daemon
2013-08-08 22:30 ` bugzilla-daemon
2013-08-08 22:37 ` bugzilla-daemon
2013-08-08 22:41 ` bugzilla-daemon
2013-08-09 18:26 ` bugzilla-daemon
2013-08-19 21:14 ` bugzilla-daemon
2013-10-13 20:50 ` bugzilla-daemon
2013-10-14 8:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-67187-502-sKy8ykQ84v@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox