From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71923] New: Screen corruption when watching VDPAU-accelerated H264 video
Date: Fri, 22 Nov 2013 15:28:15 +0000 [thread overview]
Message-ID: <bug-71923-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2123 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71923
Priority: medium
Bug ID: 71923
Assignee: dri-devel@lists.freedesktop.org
Summary: Screen corruption when watching VDPAU-accelerated H264
video
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: kaszak696@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.2
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 89641
--> https://bugs.freedesktop.org/attachment.cgi?id=89641&action=edit
Dmesg log with the described errors
Hi, i have a trouble watching some H264 videos when using VDPAU acceleration.
What happens is the screen gets completly corrupted (gray bars cover the whole
screen) when player plays a certain frame in the video. It always happens at
the same point of the video, for some videos it doesn't happen at all. I
managed to blindly save smesg output to a file when this happened, and it's
filled with these kinds of messages:
[ 47.595028] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[ 48.303022] Forbidden register 0x0020 in cs at 9
[ 48.303029] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[ 56.146022] Forbidden register 0x0024 in cs at 9
[ 56.146029] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[ 57.148021] Forbidden register 0x0028 in cs at 9
[ 57.148028] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[ 57.523022] Forbidden register 0x0024 in cs at 9
[ 57.523030] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
I'm using Arch Linux with 3.12.1-ck at the moment, but it also happened on
3.11-ck and 3.11 vanilla.
lspci reports this card name, it's a Radeon 4570:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV710/M92 [Mobility Radeon HD 4530/4570/545v]
I'm using the newest stable mesa 9.2.3 and xf86-video-ati 7.2.0. The issue
happens with mpv and mplayer.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3580 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-22 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 15:28 bugzilla-daemon [this message]
2013-11-22 15:29 ` [Bug 71923] Screen corruption when watching VDPAU-accelerated H264 video bugzilla-daemon
2013-11-22 15:29 ` bugzilla-daemon
2013-11-22 15:30 ` bugzilla-daemon
2013-11-22 15:31 ` bugzilla-daemon
2013-11-22 15:33 ` bugzilla-daemon
2013-11-22 16:40 ` bugzilla-daemon
2013-11-22 17:05 ` bugzilla-daemon
2013-11-25 13:13 ` bugzilla-daemon
2013-11-26 8:14 ` bugzilla-daemon
2013-11-26 10:13 ` bugzilla-daemon
2013-11-26 11:28 ` 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-71923-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox