All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91308] Tonga UVD not working with GL_NV_vdpau_interop
Date: Sat, 25 Jul 2015 11:47:55 +0000	[thread overview]
Message-ID: <bug-91308-502-9lVP7qKQdO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91308-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Andy Furniss <adf.lists@gmail.com> ---
I tried reproducing these with agd5f drm/mesa amd-staging and I can reproduce
but I have to try a lot harder, were I not using scripts I would probably call
working.

The vdpau interop fail took about 30 tries with mpv.

After about 60 runs of mpv --vo=vdpau with cpufreq both on_demand and perf I
failed to get a ring 9 lock.

With mplayer I did about 60 with cpufreq perf without a lock, but did get one
after about 50 starts with cpufreq on_demand.

On amdgpu branches I can lock with both in < 10 starts sometimes as low as 3.

Historically I've had uvd issues that I can provoke with mplayer but not mpv -
looking at vdpau traces, I see that mplayer at start up, twice creates and
instantly destroys a decoder with w/h 48 before creating one with the correct
w/h (which depending on content it may then destroy if it needs more ref
frames).

mpv just does one create and uses it, perhaps this is why mplayer can trigger
some issues better.

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

[-- Attachment #1.2: Type: text/html, Size: 1896 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-07-25 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 15:39 [Bug 91308] Tonga UVD not working with GL_NV_vdpau_interop bugzilla-daemon
2015-07-11 15:41 ` bugzilla-daemon
2015-07-24  8:32 ` bugzilla-daemon
2015-07-24 11:34 ` bugzilla-daemon
2015-07-24 12:52 ` bugzilla-daemon
2015-07-24 16:36 ` bugzilla-daemon
2015-07-24 17:42 ` bugzilla-daemon
2015-07-24 18:26 ` bugzilla-daemon
2015-07-24 21:31 ` bugzilla-daemon
2015-07-24 21:36 ` bugzilla-daemon
2015-07-25 11:47 ` bugzilla-daemon [this message]
2015-08-28 11:11 ` bugzilla-daemon
2015-08-28 12:38 ` 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-91308-502-9lVP7qKQdO@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.