From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100242] radeon buffer allocation failure during startup of Factorio
Date: Fri, 17 Mar 2017 12:21:19 +0000 [thread overview]
Message-ID: <bug-100242-502-qEsG3Uuyn9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100242-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 540 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100242
--- Comment #4 from Christian König <deathsimple@vodafone.de> ---
The maximum size for allocations in VRAM on radeon are usually 256MB minus
pinned system resources like GART.
The game tries to allocate something which is 256MB in size, so that won't fit.
Either the driver tries to allocate a temporary buffer which is way to large or
the game tries to allocate a texture which is way to large.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1351 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-03-17 12:21 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 [this message]
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
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-qEsG3Uuyn9@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;
as well as URLs for NNTP newsgroup(s).