dri-devel.lists.freedesktop.org archive mirror
 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: Thu, 02 Mar 2017 09:50:38 +0000	[thread overview]
Message-ID: <bug-100024-502-wZLHZ17uJn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100024-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from Julien Isorce <julien.isorce@gmail.com> ---
Hi Michel. Thx you for your comment. In a way it is a good and only my attached
mesa will be needed to fix the test. I will send it to the mailing list.

But I still do not properly understand why there is not enough graphic memory
because lspci reports 2048M. And there are some contradictions depending on the
subSize for the test sequence which is:

for i in 0 1:
  glGenTextures
  glTexImage2D    maxSize
  glTexSubImage2D subSize = maxSize / 2.
  glDeleteTextures

A: The kernel trace ENOMEM appears with:
  subSize = maxSize - 1 -> "radeon: Failed to allocate a buffer"
  subSize = 3 * maxSize / 4 -> "radeon: Failed to allocate a buffer"
  subSize = maxSize / 2 -> "radeon: Not enough memory for command submission"

B: It works with:
  subSize = maxSize
  subSize = maxSize / 4

Isn't A and B a contradiction ? For me A should succeeds because
glDeteteTextures should . Also note that on other 

Also by calling glFush() within an additional loop iteration i = 2, it can
recover so it will fail for iteration i = 1 but succeeds for i = 2. 
So what could the explanation here ? Should the driver just flush the cs
automatically in that case like it does for subSize = maxSize ? Sorry I am just
trying to understand :). Thx!

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

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

  parent reply	other threads:[~2017-03-02  9:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 17:45 [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: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 [this message]
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-wZLHZ17uJn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).