From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84140] New: mplayer crashes playing some files using vdpau output
Date: Sun, 21 Sep 2014 17:06:47 +0000 [thread overview]
Message-ID: <bug-84140-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84140
Priority: medium
Bug ID: 84140
Assignee: dri-devel@lists.freedesktop.org
Summary: mplayer crashes playing some files using vdpau output
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: pejakm@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 106609
--> https://bugs.freedesktop.org/attachment.cgi?id=106609&action=edit
gdb debugging log
Driver: r600, using vdpau kernel patch.
Mesa version: commit 4eb2bbefd2bf0359aff7ebbb8e931a1c7833606f.
mplayer crashes playing »some« x264 files using vdpau. `ffmpeg -i` for those
files reports:
> Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x800
[SAR 1:1 DAR 12:5], 1769 kb/s, 23.98 fps, 23.98 tbr, 96k tbn, 47.95 tbc
(default)
The same command for files which don't cause crash looks like this:
> Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv,
bt709), 1920x800, 1979 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
(the difference is this "SAR DAR" thing).
Mplayer config ($HOME/.mplayer/config) is
> vo = vdpau
> [vo.vdpau]
> vc=ffh264vdpau,ffmpeg12vdpau,
Debug log attached. vdpauinfo log attached.
Note: I think I could play all x264 encoded files few days ago (same setup,
older mesa drivers), so this might be a some kind of regression.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3208 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:[~2014-09-21 17:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 17:06 bugzilla-daemon [this message]
2014-09-21 17:08 ` [Bug 84140] mplayer crashes playing some files using vdpau output bugzilla-daemon
2014-09-21 17:12 ` bugzilla-daemon
2014-09-22 6:15 ` bugzilla-daemon
2014-09-22 8:15 ` bugzilla-daemon
2014-09-22 8:34 ` bugzilla-daemon
2014-09-22 11:16 ` bugzilla-daemon
2014-09-22 11:38 ` bugzilla-daemon
2014-09-22 12:07 ` bugzilla-daemon
2014-09-22 12:21 ` bugzilla-daemon
2014-09-22 12:45 ` bugzilla-daemon
2014-09-22 12:51 ` bugzilla-daemon
2014-09-22 12:51 ` bugzilla-daemon
2014-09-22 13:52 ` bugzilla-daemon
2014-09-22 14:23 ` bugzilla-daemon
2014-09-22 15:53 ` bugzilla-daemon
2014-09-22 19:26 ` bugzilla-daemon
2014-09-22 21:24 ` bugzilla-daemon
2014-09-22 21:34 ` bugzilla-daemon
2014-09-22 21:38 ` bugzilla-daemon
2014-09-22 21:54 ` bugzilla-daemon
2014-09-22 23:16 ` bugzilla-daemon
2014-10-05 23:31 ` bugzilla-daemon
2014-10-06 1:47 ` bugzilla-daemon
2014-10-07 14:14 ` bugzilla-daemon
2014-10-07 22:56 ` bugzilla-daemon
2014-10-09 1:58 ` bugzilla-daemon
2014-10-21 17:15 ` bugzilla-daemon
2014-10-22 9:04 ` 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-84140-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;
as well as URLs for NNTP newsgroup(s).