Bug 100207 - atw_opengl crashes
Summary: atw_opengl crashes
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 17.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2017-03-15 01:44 UTC by Cass Everitt
Modified: 2019-09-25 19:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Cass Everitt 2017-03-15 01:44:51 UTC
You need this commit of the Vulkan-Samples repo to get something that will run on these drivers, but it crashes almost immediately sometimes, and then will run for 10s of seconds others.


OS      : Ubuntu 16.04.2 LTS
CPU     : Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
GPU     : Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) 
OpenGL  : 4.5 (Core Profile) Mesa 17.1.0-devel - padoka PPA
Display :  960 x  544 - 60 Hz (windowed)
Eye Img : 1024 x 1024 - 1x MSAA
Comment 1 Kenneth Graunke 2017-03-18 00:32:49 UTC
The application needs to call XInitThreads().
Comment 2 Kenneth Graunke 2017-03-18 00:53:14 UTC
Regarding GLSL 4.30 not working...it looks like the app initially creates a GL 4.3 core profile context...but then on atw_opengl.c:2447, it creates a second shared context by doing:

context->glxContext = glXCreateNewContext( other->xDisplay, other->glxFBConfig, GLX_RGBA_TYPE, other->glxContext, True );

That doesn't create a core profile context, so we give you the highest compatibilty context we support, which is OpenGL 3.0...hence GLSL 4.30 doesn't work.
Comment 3 GitLab Migration User 2019-09-25 19:00:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1576.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.