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 36934] screen corruption after running a game
Date: Wed,  3 Aug 2011 05:22:44 -0700 (PDT)	[thread overview]
Message-ID: <20110803122244.B10C4130178@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36934-502@http.bugs.freedesktop.org/>

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

--- Comment #6 from almos <aaalmosss@gmail.com> 2011-08-03 05:22:44 PDT ---
I observed that this corruption is often accompanied by these messages on the
console from which I start a game:
radeon: mmap failed, errno: 1
Mesa: User error: GL_OUT_OF_MEMORY in glTexImage
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1
radeon: mmap failed, errno: 1

Some of the corruption disappears after a suspend-resume cycle. Can this be a
memory-accounting bug?

A possibly unrelated question: what happens if the scene to be rendered needs
more than VRAM+GART amount of data?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-08-03 12:22 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 [this message]
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
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=20110803122244.B10C4130178@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