All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100024] [radeonsi] Failed to find memory space for buffer eviction when calling glTexSubImage2D with 16384 / 2
Date: Wed, 01 Mar 2017 17:45:25 +0000	[thread overview]
Message-ID: <bug-100024-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 100024
           Summary: [radeonsi] Failed to find memory space for buffer
                    eviction when calling glTexSubImage2D with 16384 / 2
           Product: DRI
           Version: XOrg git
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: julien.isorce@gmail.com

Created attachment 130005
  --> https://bugs.freedesktop.org/attachment.cgi?id=130005&action=edit
new piglit test max-texture-size2 to reproduce the problem

/ [AMD/ATI] Cape Verde PRO [FirePro W600] /

The piglit test max-texture-size2 prints:

GL_TEXTURE_RECTANGLE, Internal Format = GL_RGBA8, Largest Texture Size = 16384
radeon: Not enough memory for command submission.
[drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -12! (ENOMEM)
PIGLIT: {"subtest": {"GL_TEXTURE_RECTANGLE-GL_RGBA8" : "pass"}}

It says it passes but internally it fails. It looks like a bug from the TTM GPU
memory manager subsystem in the linux kernel.

To reproduce just run:
RADEON_THREAD=false DISPLAY=:0 PIGLIT_SOURCE_DIR=/home/julien/dev/piglit/
PIGLIT_PLATFORM=mixed_glx_egl ./bin/max-texture-size -fbo -auto

I set RADEON_THREAD=false to make it easier since the problem also appears with
true.

I attached a new and more minimal piglit test "max-texture-size2" that
reproduces the problem.
A workaround of the problem is to use GL fence as the new test also
demonstrates setting the env var USE_FENCE.

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

[-- Attachment #1.2: Type: text/html, Size: 3425 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-03-01 17:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 17:45 bugzilla-daemon [this message]
2017-03-01 17:46 ` [Bug 100024] [radeonsi] Failed to find memory space for buffer eviction when calling glTexSubImage2D with 16384 / 2 bugzilla-daemon
2017-03-01 17:46 ` bugzilla-daemon
2017-03-01 17:47 ` bugzilla-daemon
2017-03-01 17:47 ` bugzilla-daemon
2017-03-01 17:48 ` bugzilla-daemon
2017-03-01 17:49 ` bugzilla-daemon
2017-03-01 17:49 ` bugzilla-daemon
2017-03-01 17:50 ` bugzilla-daemon
2017-03-01 17:52 ` bugzilla-daemon
2017-03-01 17:52 ` bugzilla-daemon
2017-03-02  1:23 ` bugzilla-daemon
2017-03-02  1:25 ` bugzilla-daemon
2017-03-02  1:25 ` bugzilla-daemon
2017-03-02  1:28 ` bugzilla-daemon
2017-03-02  9:50 ` bugzilla-daemon
2017-03-02  9:52 ` bugzilla-daemon
2017-03-02  9:56 ` bugzilla-daemon
2019-09-25 17: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-100024-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.