All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73191] New: [radeonsi] vdpau playback issues, skipping & looping
Date: Tue, 31 Dec 2013 18:32:41 +0000	[thread overview]
Message-ID: <bug-73191-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2880 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=73191

          Priority: medium
            Bug ID: 73191
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [radeonsi] vdpau playback issues, skipping & looping
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rachel@strangenoises.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 91375
  --> https://bugs.freedesktop.org/attachment.cgi?id=91375&action=edit
git bisect log

Simplest to illustrate the issue with a video taken on my phone:
www.youtube.com/watch?v=GvuNu1ZEgsw

In words, I would describe it as being stuck on looping a short sequence of
frames, then it skips forward in the stream to a later sequence of frames; I
think this is simply to keep it in range of the audio, which plays normally
throughout (but not through hdmi/displayport, audio is going out via usb
speakers)

This affects all h.264 playback; interlaced or progressive, SD or HD, though
the test clip shown above is a 23.976p movie. Unsure if it affects playback of
other codecs: I've been having system crashes attempting to play mpeg2 video
streams, but I believe that's an unrelated issue.

This behaviour seems to have been introduced in commit
91aca8c662faf0ec311968b2897a72a6d08b199d ("r600g,radeonsi: consolidate buffer
code, add handling of DISCARD_RANGE for SI") on Dec 12; discovered using git
bisect and a spare afternoon. :-) Before starting that process I had tested the
current ppa:wsnipex/mesa build (bad), the current master HEAD (bad), the
current 10.0 branch head (good)

On the previous commit, 12806449fa35aff47ad6f4615ede55776c9f66c8, playback is
fine.

Affected system is running Ubuntu 13.10 x86_64, running XBMC test builds from
https://launchpad.net/~wsnipex/+archive/xbmc-fernetmenta-master - afaik the
most developed vdpau-enabled *player*. Graphics card is an AMD Radeon HD 7750
(with four mini-displayports). lspci:

rachel@twilight:~/src/mesa$ lspci | grep Radeon
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde PRO [Radeon HD 7750]
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]

Test builds of mesa directly from the read-only git repo; while for convenience
I borrowed the debian directory from the ppa builds to make .debs for
installation/deinstallation, I removed the patches (emptied
debian/patches/series) so it should all be vanilla builds.

Tried with stock current Ubuntu Saucy generic kernel and with 3.13-rc6 mainline
kernel build and with several other of the rc builds too until decided to
bisect mesa instead.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4407 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

             reply	other threads:[~2013-12-31 18:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 18:32 bugzilla-daemon [this message]
2014-01-09  4:28 ` [Bug 73191] [radeonsi] vdpau playback issues, skipping & looping bugzilla-daemon
2014-01-10  1:58 ` bugzilla-daemon
2014-01-10  8:51 ` bugzilla-daemon
2014-01-10 11:05 ` bugzilla-daemon
2014-01-10 11:24 ` bugzilla-daemon
2014-01-10 11:42 ` bugzilla-daemon
2014-01-10 18:50 ` bugzilla-daemon
2014-01-10 19:18 ` bugzilla-daemon
2014-01-10 19:38 ` bugzilla-daemon
2014-01-11 10:21 ` bugzilla-daemon
2014-01-11 11:22 ` bugzilla-daemon
2014-01-11 11:45 ` bugzilla-daemon
2014-01-11 11:55 ` bugzilla-daemon
2014-01-11 16:21 ` bugzilla-daemon
2014-01-11 19:06 ` bugzilla-daemon
2014-01-11 19:16 ` bugzilla-daemon
2014-01-11 19:33 ` bugzilla-daemon
2014-01-11 19:35 ` bugzilla-daemon
2014-01-11 19:40 ` bugzilla-daemon
2014-01-11 19:41 ` bugzilla-daemon
2014-01-12  0:56 ` bugzilla-daemon
2014-01-12  7:11 ` bugzilla-daemon
2014-01-12 14:51 ` bugzilla-daemon
2014-01-28  3:44 ` bugzilla-daemon
2014-01-28 12:02 ` bugzilla-daemon
2014-01-28 12:06 ` bugzilla-daemon
2014-01-28 13:07 ` bugzilla-daemon
2014-01-28 13:47 ` bugzilla-daemon
2014-01-28 13:58 ` bugzilla-daemon
2014-01-28 22:37 ` bugzilla-daemon
2014-02-04  6:59 ` bugzilla-daemon
2014-02-04 12:02 ` bugzilla-daemon
2014-02-09 17:29 ` bugzilla-daemon
2014-02-10 20:27 ` bugzilla-daemon
2014-02-11  8:57 ` bugzilla-daemon
2014-02-11 12:05 ` bugzilla-daemon
2014-02-11 12:10 ` bugzilla-daemon
2014-02-11 12:16 ` bugzilla-daemon
2014-02-11 12:26 ` bugzilla-daemon
2014-02-11 12:48 ` bugzilla-daemon
2014-02-12 20:01 ` bugzilla-daemon
2014-02-24 19:28 ` bugzilla-daemon
2014-02-25  9:36 ` 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-73191-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.