From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67994] Lockup with UVD and DPM on RV730
Date: Tue, 20 Aug 2013 23:22:57 +0000 [thread overview]
Message-ID: <bug-67994-502-I2qGEbt3k9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67994-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1691 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67994
--- Comment #11 from Timothée Ravier <timothee.romain.ravier@gmail.com> ---
Created attachment 84362
--> https://bugs.freedesktop.org/attachment.cgi?id=84362&action=edit
X server logs
Note: if I quickly kill the second mplayer right after the start of the video I
can avoid the crash, but UVD won't work anymore and mplayer will permanently
end with some errors (if VDPAU is forced):
Selected video codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (VDPAU
acceleration) [libavcodec]
Selected audio codec: ATSC A/52A (AC-3) [libavcodec]
AUDIO: 48000 Hz, 2 ch, floatle, 384.0 kbit/12.50% (ratio: 48000->384000)
AO: [pulse] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
VIDEO: 1280x720 23.976 fps 0.0 kbps ( 0.0 kB/s)
VO: [vdpau] 1280x720 => 1280x720 H.264 VDPAU acceleration
[ vdpau] Failed creating VDPAU decoder: An invalid/unsupported
VdpDecoderProfile value was supplied.
FATAL: Cannot initialize video driver.
VIDEO: 1280x720 23.976 fps 0.0 kbps ( 0.0 kB/s)
VO: [vdpau] 1280x720 => 1280x720 H.264 VDPAU acceleration
[ vdpau] Failed creating VDPAU decoder: An invalid/unsupported
VdpDecoderProfile value was supplied.
FATAL: Cannot initialize video driver.
[h264_vdpau @ 0x7f736c111cc0]decode_slice_header error
[h264_vdpau @ 0x7f736c111cc0]no frame!
Error while decoding frame!
FATAL: Could not initialize video filters (-vf) or video output (-vo).
But right after that my X session was killed and the X server kept exiting with
bus errors when starting new ones (see attached log).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2601 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-20 23:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 12:19 [Bug 67994] New: System freezes when playing video on open source AMD drivers with VDPAU bugzilla-daemon
2013-08-11 12:22 ` [Bug 67994] " bugzilla-daemon
2013-08-11 15:26 ` bugzilla-daemon
2013-08-11 15:29 ` [Bug 67994] System freezes (GPU lockup) " bugzilla-daemon
2013-08-11 16:06 ` bugzilla-daemon
2013-08-11 18:25 ` bugzilla-daemon
2013-08-11 18:28 ` bugzilla-daemon
2013-08-11 19:04 ` [Bug 67994] Lockup with UVD and DPM on RV730 bugzilla-daemon
2013-08-15 20:43 ` bugzilla-daemon
2013-08-20 16:22 ` bugzilla-daemon
2013-08-20 16:25 ` bugzilla-daemon
2013-08-20 16:59 ` bugzilla-daemon
2013-08-20 18:15 ` bugzilla-daemon
2013-08-20 23:22 ` bugzilla-daemon [this message]
2014-03-05 21:42 ` bugzilla-daemon
2014-05-19 21:20 ` bugzilla-daemon
2015-05-08 16:32 ` bugzilla-daemon
2015-05-08 16:35 ` bugzilla-daemon
2015-05-08 16:36 ` bugzilla-daemon
2015-05-08 16:38 ` bugzilla-daemon
2015-05-08 17:19 ` bugzilla-daemon
2019-11-19 8:37 ` 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-67994-502-I2qGEbt3k9@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