From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
Date: Wed, 30 Jan 2013 17:22:36 +0000 (UTC) [thread overview]
Message-ID: <20130130172236.AF30811FF21@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-49981-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=49981
Jérôme Glisse <glisse@freedesktop.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |glisse@freedesktop.org
--- Comment #6 from Jérôme Glisse <glisse@freedesktop.org> 2013-01-30 17:22:36 ---
It's not completely a kernel bug. It's userspace asking insane things to
kernel.
This mesa patch should avoid the issue most of the time :
http://people.freedesktop.org/~glisse/0001-r600g-add-cs-memory-usage-accounting-and-limit-it.patch
If you are using a recent mesa with gnome you will probably want this cogl
patch too :
http://people.freedesktop.org/~glisse/0001-glx-do-not-use-multisample-visual-config-for-front-o.patch
And for kernel i am working on better handling of memory fragmentation.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-01-30 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-49981-2300@https.bugzilla.kernel.org/>
2012-11-05 14:11 ` [Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! bugzilla-daemon
2012-11-12 19:42 ` bugzilla-daemon
2012-11-12 19:43 ` bugzilla-daemon
2012-12-27 18:16 ` bugzilla-daemon
2013-01-30 3:15 ` bugzilla-daemon
2013-01-30 17:22 ` bugzilla-daemon [this message]
2013-02-12 18:58 ` 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=20130130172236.AF30811FF21@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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.