All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99579] [radeonsi,regression] Hardware-accelerated video playback with mpv spams console with "r600_texture_transfer_map - failed to create temporary texture to hold untiled copy"
Date: Sat, 28 Jan 2017 19:11:49 +0000	[thread overview]
Message-ID: <bug-99579-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2243 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99579

            Bug ID: 99579
           Summary: [radeonsi,regression] Hardware-accelerated video
                    playback with mpv spams console with
                    "r600_texture_transfer_map - failed to create
                    temporary texture to hold untiled copy"
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Keywords: bisect_pending, regression
          Severity: normal
          Priority: high
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: kai@dev.carbon-project.org
        QA Contact: dri-devel@lists.freedesktop.org

Since updating Mesa from 494b63f52541936e7b0357534ee0fd2444319501 to
7c5629a26912af9164bda17b7af5370f6b4302e4 I see the following error spammed to
the console when playing back any video with mpv and hardware acceleration
(VA-API and VDPAU are both affected):
> EE ../../../../../src/gallium/drivers/radeon/r600_texture.c:1571 r600_texture_transfer_map - failed to create temporary texture to hold untiled copy
Only when I set --hwdec=no and --vo to something other than "vaapi" or "vdpau"
I can avoid this error. dmesg is clear and shows no error.

I'm using the following mpv and FFmpeg versions (all from their respective
Debian packages):
mpv 0.23.0
ffmpeg library versions:
   libavutil       55.34.100
   libavcodec      57.64.101
   libavformat     57.56.100
   libswscale      4.2.100
   libavfilter     6.65.100
   libswresample   2.3.100
ffmpeg version: 3.2.2-1

The graphics stack used (Debian testing as a base) was:
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/7c5629a269 + the modified version of attachment 127812
libdrm: Git:master/d4b8344363 (tag libdrm-2.4.75)
LLVM: SVN:trunk/r293339 (5.0 devel) +
<https://reviews.llvm.org/D26348?download=true>
X.Org: 2:1.19.0-3
Linux: 4.9.6
Firmware: 20161130-2
libclc: Git:master/2ec7d80d5e
DDX (amdgpu): 1.2.0-1+b1

Let me know, if you need anything else (besides a bisect).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4166 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

             reply	other threads:[~2017-01-28 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 19:11 bugzilla-daemon [this message]
2017-01-28 19:37 ` [Bug 99579] [radeonsi,regression] Hardware-accelerated video playback with mpv spams console with "r600_texture_transfer_map - failed to create temporary texture to hold untiled copy" bugzilla-daemon
2017-01-28 19:51 ` 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-99579-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.