All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201163] New: amdgpu: carrizo: Stalls using vaapi encoder
Date: Mon, 17 Sep 2018 12:39:36 +0000	[thread overview]
Message-ID: <bug-201163-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=201163

            Bug ID: 201163
           Summary: amdgpu: carrizo: Stalls using vaapi encoder
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.18.0
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: ricardo.ribalda@gmail.com
        Regression: No

Created attachment 278595
  --> https://bugzilla.kernel.org/attachment.cgi?id=278595&action=edit
glxinfo

This command:

gst-launch-1.0 v4l2src io-mode=4 ! vaapih264enc ! fakesink dump=1

results in a stall non recoverable using ctrl+c and the following kernel
message

[ 1617.944590] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vce0 timeout,
last signaled seq=4, last emitted seq=6
[ 1617.944628] [drm] IP block:vce_v3_0 is hung!
[ 1617.944632] [drm] GPU recovery disabled.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-09-17 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 12:39 bugzilla-daemon [this message]
2018-09-17 12:40 ` [Bug 201163] amdgpu: carrizo: Stalls using vaapi encoder bugzilla-daemon
2018-09-17 12:40 ` bugzilla-daemon
2018-09-17 12:40 ` bugzilla-daemon
2018-09-17 12:42 ` bugzilla-daemon
2018-09-17 12:46 ` bugzilla-daemon
2018-10-03 15: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-201163-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.