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: Thu, 09 Jul 2015 10:38:48 +0000 [thread overview]
Message-ID: <bug-91281-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 893 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91281
Bug ID: 91281
Summary: Tonga VCE 2160p encode fails with BO to small for
addr
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
I don't know what the VCE is supposed to do on this R9 285 card but testing
with 2160p gives.
amdgpu: The CS has been rejected, see dmesg for more information.
[drm:amdgpu_vce_cs_reloc [amdgpu]] *ERROR* BO to small for addr 0x0002450000 14
13
Same test works with 1080p (bit slow but I haven't tested/understood the PM
situation yet).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2107 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:[~2015-07-09 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:38 bugzilla-daemon [this message]
2016-07-29 23:08 ` [Bug 91281] Tonga VCE 2160p encode fails with BO to small for addr bugzilla-daemon
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@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.