From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100242] radeon buffer allocation failure during startup of Factorio
Date: Sun, 25 Jun 2017 10:46:50 +0000 [thread overview]
Message-ID: <bug-100242-502-dA9qmf2xul@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100242-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100242
--- Comment #8 from tnmailinglists@gmail.com ---
I managed to bisect mesa and got this result:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=fb827c055cb1bdd2b18d0687c06c56b537d805f3
is the first bad commit
commit fb827c055cb1bdd2b18d0687c06c56b537d805f3
Author: Nicolai Hähnle <nicolai.haehnle@amd.com>
Date: Mon Sep 12 12:19:47 2016 +0200
winsys/radeon: enable buffer allocation from slabs
Only enable for chips with GPUVM, because older driver paths do not take
the
required offset into account.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
:040000 040000 4e1327d4b72890178a2057d2341971001f2de54d
d162404a219307e5f6cda1009b864e66f23f4e63 M src
I have also noticed that after a recent update the game now gives some more
information, so when it does run like described in comment #3, it now also
tells me that it detected an error by adding the following line right after the
four driver error blocks:
2.321 glTexImage2D for format ARGB_8888, size 8192x8185 failed
(GL_OUT_OF_MEMORY)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2261 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-25 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 22:55 [Bug 100242] radeon buffer allocation failure during startup of Factorio bugzilla-daemon
2017-03-16 22:56 ` bugzilla-daemon
2017-03-16 22:56 ` bugzilla-daemon
2017-03-17 12:07 ` bugzilla-daemon
2017-03-17 12:21 ` bugzilla-daemon
2017-03-21 2:22 ` bugzilla-daemon
2017-03-21 14:41 ` bugzilla-daemon
2017-03-22 1:56 ` bugzilla-daemon
2017-03-22 1:57 ` bugzilla-daemon
2017-06-25 10:46 ` bugzilla-daemon [this message]
2017-06-26 3:06 ` bugzilla-daemon
2017-06-27 7:53 ` bugzilla-daemon
2017-06-27 15:28 ` bugzilla-daemon
2017-07-03 10:41 ` 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-100242-502-dA9qmf2xul@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