From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91281] Tonga VCE 2160p encode fails with BO to small for addr
Date: Fri, 29 Jul 2016 23:08:37 +0000 [thread overview]
Message-ID: <bug-91281-502-kxDylN22HF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91281-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91281
--- Comment #1 from Andy Furniss <adf.lists@gmail.com> ---
Now that vaapi is enabled the situation with this is more mixed.
omx still just always fails.
ffmpeg vaapi always works.
gatreamer vaapi fails or works depending on framerate, which is a bit
confusing.
For 2160p as long as I say framerate <=30 it works. For 4096x2160 it has to be
<=26.
Adding size to the kernel error message shows that the failing size = 2x raw
framesize -
[drm:amdgpu_vce_cs_reloc [amdgpu]] *ERROR* BO to small for addr 0x0108fde000 14
13 24883200
Adding debugging to vlVaCreateBuffer doesn't show any difference between
working and failing cases - the size requested being one raw frame.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1625 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-29 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:38 [Bug 91281] Tonga VCE 2160p encode fails with BO to small for addr bugzilla-daemon
2016-07-29 23:08 ` bugzilla-daemon [this message]
2016-08-01 10:19 ` bugzilla-daemon
2016-08-01 23:49 ` bugzilla-daemon
2016-08-03 12:24 ` bugzilla-daemon
2016-08-03 23:13 ` bugzilla-daemon
2016-08-07 23:32 ` bugzilla-daemon
2016-12-06 9:57 ` 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-91281-502-kxDylN22HF@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