From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36934] screen corruption after running a game
Date: Tue, 9 Aug 2011 03:34:33 -0700 (PDT) [thread overview]
Message-ID: <20110809103433.44680130168@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36934-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36934
--- Comment #7 from Michel Dänzer <michel@daenzer.net> 2011-08-09 03:34:33 PDT ---
(In reply to comment #6)
> I observed that this corruption is often accompanied by these messages on the
> console from which I start a game:
What exactly does 'often' mean? If it's not always, it probably can't (fully)
explain the problem...
> radeon: mmap failed, errno: 1
> Mesa: User error: GL_OUT_OF_MEMORY in glTexImage
Looks like this app ran out of memory. (errno: 1 means EPERM, not sure how that
can happen...)
> A possibly unrelated question: what happens if the scene to be rendered needs
> more than VRAM+GART amount of data?
It's up to the userspace drivers to split it up into smaller chunks that can
fit.
A couple of random things to try would be radeon.agpmode=4 and =-1, disabling
tiling, ... Trying a newer kernel and possibly r300g driver probably wouldn't
hurt either.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for 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:[~2011-08-09 10:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:48 [Bug 36934] New: screen corruption after running a game through wine bugzilla-daemon
2011-05-09 11:41 ` [Bug 36934] " bugzilla-daemon
2011-05-13 10:36 ` bugzilla-daemon
2011-05-13 10:37 ` bugzilla-daemon
2011-05-13 10:38 ` bugzilla-daemon
2011-06-04 19:21 ` [Bug 36934] screen corruption after running a game bugzilla-daemon
2011-08-03 12:22 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:34 ` bugzilla-daemon [this message]
2011-08-09 19:39 ` bugzilla-daemon
2011-08-30 21:51 ` bugzilla-daemon
2011-08-31 10:44 ` bugzilla-daemon
2011-09-13 21:59 ` bugzilla-daemon
2011-10-18 16:00 ` bugzilla-daemon
2011-10-22 11:12 ` bugzilla-daemon
2011-10-22 13:11 ` bugzilla-daemon
2011-10-22 14:00 ` bugzilla-daemon
2011-10-23 8:49 ` bugzilla-daemon
2011-10-28 18:26 ` bugzilla-daemon
2013-03-08 20:11 ` bugzilla-daemon
2014-05-24 20:45 ` 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=20110809103433.44680130168@annarchy.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