From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102296] R9 285 VCE corruption since drm/amdgpu/gmc8: use the vram location programmed by the vbios
Date: Fri, 18 Aug 2017 14:43:10 +0000 [thread overview]
Message-ID: <bug-102296-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1464 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102296
Bug ID: 102296
Summary: R9 285 VCE corruption since drm/amdgpu/gmc8: use the
vram location programmed by the vbios
Product: DRI
Version: DRI 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
Bit late with this, bisected on drm-next-4.13-wip
R9 285 Tonga I am getting corrupted output from VCE encode, omx or vaapi since
below commit.
To re-produce this you need to use gstreamer and encode "fast and large" eg.
2160p from raw nv12.
Slow things like ffmpeg or gst-vaapi without ! queue ! seem to hide the issue
somewhat.
26d4ac55d2260f8685475b3f6e76e276a238cca7 is the first bad commit
commit 26d4ac55d2260f8685475b3f6e76e276a238cca7
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Tue Nov 1 13:08:33 2016 -0400
drm/amdgpu/gmc8: use the vram location programmed by the vbios
This makes mc programming much simpler in future patches.
Since evergreen, the vbios has been programming the fb location
to the proper vram size. The only reason to reprogram it would
be to change the location.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2852 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 reply other threads:[~2017-08-18 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 14:43 bugzilla-daemon [this message]
2017-08-18 15:06 ` [Bug 102296] R9 285 VCE corruption since drm/amdgpu/gmc8: use the vram location programmed by the vbios bugzilla-daemon
2017-08-18 15:31 ` bugzilla-daemon
2017-08-18 15:31 ` bugzilla-daemon
2017-08-18 15:33 ` bugzilla-daemon
2017-08-18 15:45 ` bugzilla-daemon
2017-08-18 16:27 ` bugzilla-daemon
2017-08-18 16:54 ` bugzilla-daemon
2017-08-18 17:25 ` bugzilla-daemon
2017-08-18 17:59 ` bugzilla-daemon
2017-08-18 18:24 ` bugzilla-daemon
2017-09-19 14:59 ` bugzilla-daemon
2017-09-19 15:16 ` bugzilla-daemon
2017-09-19 15:24 ` bugzilla-daemon
2018-01-17 19:21 ` bugzilla-daemon
2018-01-18 17:59 ` 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-102296-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.