All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93301] ns2_linux32: radeon VM fault on Hawaii (+mmap errors)
Date: Wed, 09 Dec 2015 20:28:49 +0000	[thread overview]
Message-ID: <bug-93301-502-mfCWK2GCNB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93301-502@http.bugs.freedesktop.org/>


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

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

Nicolai Hähnle <nhaehnle@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nhaehnle@gmail.com

--- Comment #15 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Created attachment 120440
  --> https://bugs.freedesktop.org/attachment.cgi?id=120440&action=edit
0001-XXX-winsys-radeon-limit-buffer-cache-size.patch

Following the hypothesis that your game is running out of address space, here
is a quick patch for Mesa that limits the buffer cache size to 4MB as a simple
test.

Try this (feel free to play around with the number in the patch), plus reducing
any graphics quality options the game may have to the minimum. Don't be
surprised if performance becomes worse.

Please also set the environment variable R600_DEBUG=info and provide the
output, as this allows us to see the default buffer cache size.

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

[-- Attachment #1.2: Type: text/html, Size: 2742 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:[~2015-12-09 20:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  4:10 [Bug 93301] ns2_linux32: radeon VM fault / VM_CONTEXT1_PROTECTION_FAULT_ADDR bugzilla-daemon
2015-12-09  5:48 ` bugzilla-daemon
2015-12-09  5:52 ` bugzilla-daemon
2015-12-09  6:22 ` bugzilla-daemon
2015-12-09  9:21 ` bugzilla-daemon
2015-12-09  9:23 ` bugzilla-daemon
2015-12-09  9:39 ` bugzilla-daemon
2015-12-09  9:44 ` bugzilla-daemon
2015-12-09  9:52 ` bugzilla-daemon
2015-12-09 10:18 ` bugzilla-daemon
2015-12-09 10:37 ` bugzilla-daemon
2015-12-09 10:39 ` bugzilla-daemon
2015-12-09 12:37 ` [Bug 93301] ns2_linux32: radeon VM fault on Hawaii w/ DCC enabled (+mmap errors) bugzilla-daemon
2015-12-09 12:39 ` [Bug 93301] ns2_linux32: radeon VM fault on Hawaii " bugzilla-daemon
2015-12-09 12:51 ` bugzilla-daemon
2015-12-09 14:18 ` bugzilla-daemon
2015-12-09 14:35 ` bugzilla-daemon
2015-12-09 20:28 ` bugzilla-daemon [this message]
2015-12-09 21:05 ` bugzilla-daemon
2015-12-09 21:56 ` bugzilla-daemon
2015-12-10  1:46 ` bugzilla-daemon
2015-12-10  1:47 ` bugzilla-daemon
2015-12-10  1:48 ` bugzilla-daemon
2015-12-10 11:35 ` bugzilla-daemon
2015-12-10 13:01 ` bugzilla-daemon
2015-12-10 14:41 ` bugzilla-daemon
2017-01-14 19:54 ` bugzilla-daemon
2017-01-14 20:25 ` bugzilla-daemon
2017-01-14 22:31 ` bugzilla-daemon
2017-01-14 23:00 ` bugzilla-daemon
2017-01-15  1:59 ` bugzilla-daemon
2017-08-24 21:02 ` bugzilla-daemon
2017-08-25  8:36 ` bugzilla-daemon
2017-10-09 15:34 ` 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-93301-502-mfCWK2GCNB@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.