All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89987] Slow VDPAU (rv770_restrict_performance_levels_before_switch failed)
Date: Sun, 09 Aug 2015 22:25:34 +0000	[thread overview]
Message-ID: <bug-89987-502-qlV4fSSlfU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89987-502@http.bugs.freedesktop.org/>


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

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

James Le Cuirot <chewi@gentoo.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #9 from James Le Cuirot <chewi@gentoo.org> ---
Sincere apologies for this but it looks like this is actually a bug in VLC.
Several factors threw me off, namely that mplayer isn't playing ball either
(don't know why yet), that I upgraded the kernel around the same time, that UVD
was introduced in 3.18, and the error in dmesg, all of which made it look like
a kernel problem.

Doesn't that mean it would have still been broken when going back to 3.17?
Actually it kinda was but not nearly as badly so I guess I didn't notice when
filing this bug. Under that kernel version, it looks as though it drops every
other frame in a smooth manner. Under recent kernels, it barely moves at all. I
started downgrading various userspace components like libvdpau, Mesa, and
xf86-video-ati to see whether any of those made a difference but it wasn't
until I downgraded VLC from 2.2 to 2.1 that the problem went away, both under
3.17 and 4.1. I also tried VLC git master under 4.1 and strangely it behaves
like 2.2 does under 3.17, dropping every other frame. Very confusing.

I am now bisecting to track down the precise cause.

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

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

      parent reply	other threads:[~2015-08-09 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 22:40 [Bug 89987] Slow VDPAU (rv770_restrict_performance_levels_before_switch failed) bugzilla-daemon
2015-04-11 22:40 ` bugzilla-daemon
2015-04-11 22:44 ` bugzilla-daemon
2015-04-11 22:46 ` bugzilla-daemon
2015-04-13  8:10 ` bugzilla-daemon
2015-05-26 21:19 ` bugzilla-daemon
2015-05-31  8:13 ` bugzilla-daemon
2015-07-09 22:21 ` bugzilla-daemon
2015-07-10 10:02 ` bugzilla-daemon
2015-08-09 22:25 ` bugzilla-daemon [this message]

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-89987-502-qlV4fSSlfU@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.