From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98280] RX480 GPU lockup with vaapi encoding
Date: Sun, 16 Oct 2016 17:01:54 +0000 [thread overview]
Message-ID: <bug-98280-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1228 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98280
Bug ID: 98280
Summary: RX480 GPU lockup with vaapi encoding
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
Created attachment 127333
--> https://bugs.freedesktop.org/attachment.cgi?id=127333&action=edit
dmesg 4.9-rc1
Happens with 4.8 and 4.9-rc1. I haven't tried 4.7.
This pipeline hangs the GPU very quickly:
gst-launch-1.0 ximagesrc display-name=:0 use-damage=0 startx=0 starty=0
endx=1919 endy=1079 ! videoconvert ! video/x-raw,framerate=60/1,format=NV12 !
vaapih264enc ! h264parse ! matroskamux ! filesink location=output.avi
attached dmesg is from 4.9-rc1.
As far as I can see, it also produces one frame corrupted output with the image
being duplicated vertically and then squashed to fit into 1920x1080, see bug
98278.
Probably not related to bug 97240, but maybe?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2781 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:[~2016-10-16 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 17:01 bugzilla-daemon [this message]
2016-10-16 23:56 ` [Bug 98280] RX480 GPU lockup with vaapi encoding bugzilla-daemon
2016-10-17 12:04 ` 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-98280-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.