All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82783] New: [radeonsi] [r9 280] Constantly receiving "Failed to allocate a buffer" (of size 0) messages
Date: Mon, 18 Aug 2014 20:12:53 +0000	[thread overview]
Message-ID: <bug-82783-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 82783
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [radeonsi] [r9 280] Constantly receiving "Failed to
                    allocate a buffer" (of size 0) messages
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: dpcismael@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 10.2
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Every time I use an application requiring the use of the radeonsi driver from
Mesa, I get a continuous stream of the following  message :

radeon: Failed to allocate a buffer:
radeon:    size      : 0 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4

I never get this kind of message when running apps using the 'normal'
xf86-video-ati driver, so I'm pretty sure radeonsi is the one sending it. 
I've made some basic tests with a self-made program and it seems like the
message is sent at least once on every frame. 

If it were just for that, I wouldn't mind that much about it; most apps that
spawn it don't show any performance problems. However, it might be linked to
another error message I sometimes get : 
LLVM ERROR: ran out of registers during register allocation 

This LLVM error always turns up as a report of a recent crash. So far, I've
seen two situations where it happened : trying to start a game on Xonotic with
video effects settings on ultra, and reaching some triggers/areas in the
Warcraft III campaign on Wine with Warcraft III being in Direct3D mode. I could
probably search and/or file reports about that LLVM error, so I won't digress
any further; this post is mostly meant to be about the 'Failed to allocate a
buffer' error messages.

To end this report, I'll provide the relevant hardware and software components
from my setup:
- CPU : Intel Core i5 4460
- Motherboard : Asus H87 Plus
- RAM : GSkill Ripjaws 2 x 4gb
- GPU : Gigabyte Radeon R9 280
- OS : Arch Linux with kernel version 3.16.1-1
- Xorg 1.16.0-6 
- GPU drivers : all open-source; xf86-video-ati 1:7.4.0-3, 
radeonsi from xf86-video-ati package 10.2.5-1

That's pretty much it, I guess.

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

[-- Attachment #1.2: Type: text/html, Size: 3694 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-08-18 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 20:12 bugzilla-daemon [this message]
2014-08-18 21:01 ` [Bug 82783] [radeonsi] [r9 280] Constantly receiving "Failed to allocate a buffer" (of size 0) messages 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-82783-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.