dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82162] Syslog flooded by [drm:radeon_gem_object_create] errors
Date: Thu, 14 Aug 2014 17:43:39 +0000	[thread overview]
Message-ID: <bug-82162-502-lXxeiVf2BD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82162-502@http.bugs.freedesktop.org/>


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

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

--- Comment #27 from sarnex <commendsarnex@gmail.com> ---
(In reply to comment #26)
> After compiling the latest version of mesa from git, I'm still getting this
> bug with my Radeon HD 7950 spamming the system log.
> 
> [  372.835016] [TTM] Illegal buffer object size
> [  372.835019] [TTM] Illegal buffer object size
> [  372.835021] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM
> object (0, 6, 4096, -22)
> 
> So it doesn't seem to be fixed for me at least.

You need to compile the 32 bit mesa packages you are using as well. It's must
easier to just install the oibaf PPA. I have no issues after the fix.

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

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

  parent reply	other threads:[~2014-08-14 17:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  1:25 [Bug 82162] New: Syslog flooded by [drm:radeon_gem_object_create] errors bugzilla-daemon
2014-08-05  1:25 ` [Bug 82162] " bugzilla-daemon
2014-08-05  1:29 ` bugzilla-daemon
2014-08-05  1:31 ` bugzilla-daemon
2014-08-05  1:41 ` bugzilla-daemon
2014-08-05  6:56 ` bugzilla-daemon
2014-08-05 14:00 ` bugzilla-daemon
2014-08-05 14:34 ` bugzilla-daemon
2014-08-05 17:51 ` bugzilla-daemon
2014-08-05 17:56 ` bugzilla-daemon
2014-08-05 18:14 ` bugzilla-daemon
2014-08-06  2:33 ` bugzilla-daemon
2014-08-06  4:08 ` bugzilla-daemon
2014-08-06  7:35 ` bugzilla-daemon
2014-08-06 14:13 ` bugzilla-daemon
2014-08-06 14:39 ` bugzilla-daemon
2014-08-06 15:09 ` bugzilla-daemon
2014-08-06 15:13 ` bugzilla-daemon
2014-08-06 15:16 ` bugzilla-daemon
2014-08-06 15:24 ` bugzilla-daemon
2014-08-06 15:31 ` bugzilla-daemon
2014-08-07 10:10 ` bugzilla-daemon
2014-08-07 13:34 ` bugzilla-daemon
2014-08-07 14:27 ` bugzilla-daemon
2014-08-07 14:29 ` bugzilla-daemon
2014-08-07 16:57 ` bugzilla-daemon
2014-08-09 21:53 ` bugzilla-daemon
2014-08-09 21:54 ` bugzilla-daemon
2014-08-14 17:34 ` bugzilla-daemon
2014-08-14 17:43 ` bugzilla-daemon [this message]
2014-08-14 18:00 ` bugzilla-daemon
2014-08-14 18:01 ` bugzilla-daemon
2014-08-18 21:01 ` 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-82162-502-lXxeiVf2BD@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