From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN
Date: Mon, 04 Jul 2016 10:16:24 +0000 [thread overview]
Message-ID: <bug-96678-502-ZmKqXWW1zU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96678-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1915 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96678
--- Comment #6 from Joost van Dongen <joost@ronimo-games.com> ---
Joost here, lead programmer on Awesomenauts. Based on these logs it seems like
a driver problem since the crash is in an extremely early part of our OpenGL
code, before we do anything exciting. Also, nothing recently changed in that
part of our OpenGL code.
I'm not a Linux expert myself but it seems like you might not be running
proprietary AMD drivers or something like that? Maybe try other drivers?
Based on these logs the crash is somewhere in this bit of code:
GLint swapInterval = 0;
switch (interval)
{
case VSI_ONE: swapInterval = 1; break;
case VSI_TWO: swapInterval = 2; break;
case VSI_NONE:
default:
break;
}
if (GLXEW_EXT_swap_control)
{
glXSwapIntervalEXT(glXGetCurrentDisplay(),
glXGetCurrentDrawable(), swapInterval);
}
else if (GLXEW_SGI_swap_control)
{
glXSwapIntervalSGI(swapInterval);
}
glViewport(0, 0, windowWidth, windowHeight);
glScissor(0, 0, windowWidth, windowHeight);
glClearColor(0.f, 0.f, 0.f, 0.f);
glEnable(GL_DEPTH_TEST);
// perform an initial rendering to clear the screen on startup
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT |
GL_STENCIL_BUFFER_BIT);
SDL_GL_SwapBuffers();
glDisable(GL_CULL_FACE);
glDisable(GL_DEPTH_TEST);
I don't see any shader code here so if the problem is that a shader isn't
compiling then maybe glClear generates a basic shader to perform the clear, and
fails at that?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2683 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:[~2016-07-04 10:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 1:46 [Bug 96678] Awesomenauts cannot launch AMD PITCAIRN bugzilla-daemon
2016-07-01 13:13 ` bugzilla-daemon
2016-07-04 2:33 ` bugzilla-daemon
2016-07-04 2:34 ` bugzilla-daemon
2016-07-04 2:50 ` bugzilla-daemon
2016-07-04 2:51 ` bugzilla-daemon
2016-07-04 10:16 ` bugzilla-daemon [this message]
2016-07-04 16:00 ` bugzilla-daemon
2016-07-05 2:03 ` bugzilla-daemon
2016-07-06 9:21 ` bugzilla-daemon
2016-07-06 9:42 ` bugzilla-daemon
2016-07-06 10:43 ` bugzilla-daemon
2016-07-06 10:46 ` bugzilla-daemon
2016-07-06 12:16 ` bugzilla-daemon
2016-07-06 12:45 ` bugzilla-daemon
2016-07-06 12:50 ` bugzilla-daemon
2016-07-06 13:01 ` bugzilla-daemon
2016-07-07 3:06 ` bugzilla-daemon
2016-07-07 6:51 ` bugzilla-daemon
2016-07-07 6:54 ` bugzilla-daemon
2016-07-07 7:50 ` bugzilla-daemon
2016-07-07 9:44 ` bugzilla-daemon
2016-07-07 13:03 ` bugzilla-daemon
2016-07-07 13:29 ` bugzilla-daemon
2016-07-13 9:26 ` bugzilla-daemon
2016-07-23 11:16 ` bugzilla-daemon
2016-07-23 11:31 ` bugzilla-daemon
2016-10-26 10:51 ` bugzilla-daemon
2016-10-27 5:47 ` bugzilla-daemon
2016-11-04 10:15 ` 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-96678-502-ZmKqXWW1zU@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).