From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71796] New: Hardware assisted (VDPAU) decoding of MPEG-2 causes GPU lockup - Radeon HD6950
Date: Tue, 19 Nov 2013 16:27:14 +0000 [thread overview]
Message-ID: <bug-71796-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1277 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71796
Priority: medium
Bug ID: 71796
Assignee: dri-devel@lists.freedesktop.org
Summary: Hardware assisted (VDPAU) decoding of MPEG-2 causes
GPU lockup - Radeon HD6950
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: libgradev@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Created attachment 89477
--> https://bugs.freedesktop.org/attachment.cgi?id=89477&action=edit
DMESG output showing hardware info and lockup.
Playing back MPEG-2 compressed video causes a GPU lockup and reset. This
happens about 9 times out of 10 upon start of playback - the other time
playback starts fine.
About 4 out of 5 times the reset is successful and playback begins a catchup
phase before continuing normally - otherwise it results in a complete system
freeze.
If playback actually starts it continues fine.
Using VDPAU assisted playback via XBMC. Using software only playback works fine
every time. h264 playback seems unaffected.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2774 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 reply other threads:[~2013-11-19 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 16:27 bugzilla-daemon [this message]
2013-11-22 19:13 ` [Bug 71796] Hardware assisted (VDPAU) decoding of MPEG-2 causes GPU lockup - Radeon HD6950 bugzilla-daemon
2013-11-22 19:17 ` bugzilla-daemon
2013-11-23 13:35 ` bugzilla-daemon
2013-11-23 13:36 ` bugzilla-daemon
2013-11-24 1:13 ` bugzilla-daemon
2013-11-24 1:18 ` bugzilla-daemon
2013-11-24 1:20 ` bugzilla-daemon
2013-11-28 15:39 ` bugzilla-daemon
2013-12-02 2:57 ` bugzilla-daemon
2013-12-06 13:15 ` bugzilla-daemon
2013-12-08 15:52 ` bugzilla-daemon
2013-12-08 19:15 ` bugzilla-daemon
2013-12-08 21:15 ` bugzilla-daemon
2013-12-08 21:24 ` bugzilla-daemon
2013-12-08 21:41 ` bugzilla-daemon
2013-12-08 21:56 ` bugzilla-daemon
2013-12-15 17:54 ` bugzilla-daemon
2019-09-18 19:11 ` 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-71796-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.