dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 23 Jul 2013 18:01:33 +0000	[thread overview]
Message-ID: <bug-67187-502-AmAA7Gd8qu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67187-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=67187

--- Comment #3 from Harald Judt <h.judt@gmx.at> ---
Ok, good news first: It doesn't seem to have to do anything with playing videos
using UVD. In fact, playing videos works fine and doesn't have any bad effect
on suspending or hibernating.

But there are worse troubles now. The reason the error messages started to
appear was because I set /sys/power/pm_async to 1 - to make it faster -, albeit
for suspend/resume only. This explains why they appeared only for some cycles.
I've always set pm_async to 0 because of my hibernate/resume problems described
in bug #44772. Before the introduction of UVD support, suspend/resume worked
reliably with pm_async=1. Now that's not the case anymore and pm_async=0 has
become mandatory. But what's worse, even with pm_async set to 0, suspend/resume
doesn't work reliable anymore. Sometimes the monitor simply turns off when
suspending, and the system hangs. Previously, that was only the case with
hibernate/resume at resume time.

Now I wonder... Maybe the card simply takes more time to initialize? At least
the error message states UVD failed to initialize... Is there some way to add a
delay at resuming/initializing, maybe this would help?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2313 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

  parent reply	other threads:[~2013-07-23 18:01 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 [this message]
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
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-AmAA7Gd8qu@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