From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69120] With dpm=1 vdpau is not usable
Date: Thu, 30 Jan 2014 18:39:32 +0000 [thread overview]
Message-ID: <bug-69120-502-mOlGkLGdoa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69120-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1551 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69120
--- Comment #24 from Chris Humbert <freedesktop@mahadri.com> ---
Created attachment 93075
--> https://bugs.freedesktop.org/attachment.cgi?id=93075&action=edit
cedar-3.13.1-dmesg
radeon.dpm=1 vdpau causes Cedar [HD 5450] to GPU lockup CP stall immediately.
The player hangs with a black window.
radeon.dpm=0 vdpau works very well.
01:00.0 VGA compatible controller: [AMD/ATI] Cedar [Radeon HD 5450]
Linux 3.13.1, xf86-video-ati 7.3.0, mesa 9.5
[ 107.875202] switching to power state:
[ 107.875203] ui class: none
[ 107.875204] internal class: uvd
[ 107.875206] caps: video
[ 107.875208] uvd vclk: 54000 dclk: 40000
[ 107.875210] power level 0 sclk: 65000 mclk: 40000 vddc: 1070
vddci: 0
[ 107.875212] power level 1 sclk: 65000 mclk: 40000 vddc: 1070
vddci: 0
[ 107.875213] power level 2 sclk: 65000 mclk: 40000 vddc: 1070
vddci: 0
[ 107.875214] status: r
[ 108.178542] [drm:cypress_dpm_set_power_state] *ERROR*
rv770_restrict_performance_levels_before_switch failed
[ 118.396040] radeon 0000:01:00.0: GPU lockup CP stall for more than 10068msec
[ 118.396046] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x0000000000000002 on ring 5)
[ 118.545687] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low.
[ 118.545698] [drm] Disabling audio 0 support
[ 118.698386] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2419 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:[~2014-01-30 18:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 22:38 [Bug 69120] New: With dpm=1 vdpau is not usable bugzilla-daemon
2013-09-09 0:11 ` [Bug 69120] " bugzilla-daemon
2013-09-09 0:13 ` bugzilla-daemon
2013-09-09 0:14 ` bugzilla-daemon
2013-09-09 0:16 ` bugzilla-daemon
2013-09-09 0:24 ` bugzilla-daemon
2013-09-09 4:42 ` bugzilla-daemon
2013-09-09 4:43 ` bugzilla-daemon
2013-09-09 12:40 ` bugzilla-daemon
2013-09-09 13:55 ` bugzilla-daemon
2013-09-09 14:09 ` bugzilla-daemon
2013-09-10 13:44 ` bugzilla-daemon
2013-09-10 15:23 ` bugzilla-daemon
2013-09-10 15:31 ` bugzilla-daemon
2013-09-11 0:38 ` bugzilla-daemon
2013-09-11 0:39 ` bugzilla-daemon
2013-09-11 0:40 ` bugzilla-daemon
2013-09-11 0:42 ` bugzilla-daemon
2013-09-11 0:43 ` bugzilla-daemon
2013-09-11 1:57 ` bugzilla-daemon
2013-09-11 6:36 ` bugzilla-daemon
2013-09-11 13:20 ` bugzilla-daemon
2013-09-11 13:20 ` bugzilla-daemon
2013-10-08 20:50 ` bugzilla-daemon
2013-10-08 20:50 ` bugzilla-daemon
2013-10-08 20:54 ` bugzilla-daemon
2014-01-30 18:39 ` bugzilla-daemon [this message]
2014-01-30 18:41 ` bugzilla-daemon
2015-10-11 4:02 ` bugzilla-daemon
2018-07-20 8:59 ` 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-69120-502-mOlGkLGdoa@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