[Mesa-dev] Assertion failure on SandyBridge
Kenneth Graunke
kenneth at whitecape.org
Wed Jan 25 15:41:30 PST 2012
On 01/25/2012 02:10 PM, Anuj Phogat wrote:
> On Wed, Jan 25, 2012 at 12:22 PM, Paul Berry <stereotype441 at gmail.com
> <mailto:stereotype441 at gmail.com>> wrote:
>
> On 25 January 2012 11:42, Anuj Phogat <anuj.phogat at gmail.com
> <mailto:anuj.phogat at gmail.com>> wrote:
>
> Hi,
>
> I'm getting following assertion failure on executing any OpenGL
> application including glxinfo with mesa master (dc435ae):
>
> glxinfo: brw_program.c:261: brwInitFragProgFuncs: Assertion
> `functions->ProgramStringNotify == _tnl_program_string' failed.
>
> Program received signal SIGABRT, Aborted.
> 0x00110416 in __kernel_vsyscall ()
> (gdb) bt
> #0 0x00110416 in __kernel_vsyscall ()
> #1 0x4dc3698f in raise () from /lib/libc.so.6
> #2 0x4dc382d5 in abort () from /lib/libc.so.6
> #3 0x4dc2f6a5 in __assert_fail_base () from /lib/libc.so.6
> #4 0x4dc2f757 in __assert_fail () from /lib/libc.so.6
> #5 0x00221850 in brwInitFragProgFuncs (functions=0xbfffeb30) at
> brw_program.c:261
> #6 0x0020d3e8 in brwInitDriverFunctions (functions=0xbfffeb30,
> screen=0x805fd38) at brw_context.c:117
> #7 brwCreateContext (api=0, mesaVis=0x8063040,
> driContextPriv=0x8066180, sharedContextPrivate=0x0) at
> brw_context.c:148
> #8 0x001fcde8 in intelCreateContext (api=API_OPENGL,
> mesaVis=0x8063040, driContextPriv=0x8066180, major_version=1,
> minor_version=0, flags=0, error=0xbfffee9c,
> sharedContextPrivate=0x0) at intel_screen.c:557
> #9 0x002915fb in dri2CreateContextAttribs (screen=0x805fc70,
> api=0, config=0x8063040, shared=0x0, num_attribs=0, attribs=0x0,
> error=0xbfffee9c, data=0x805a850)
> at ../common/dri_util.c:236
> #10 0x002917b7 in dri2CreateNewContextForAPI (screen=0x805fc70,
> api=0, config=0x8063040, shared=0x0, data=0x805a850) at
> ../common/dri_util.c:254
> #11 0x002917ef in dri2CreateNewContext (screen=0x805fc70,
> config=0x8063040, shared=0x0, data=0x805a850) at
> ../common/dri_util.c:262
> #12 0x00163244 in dri2_create_context (base=0x805a390,
> config_base=0x8066cc0, shareList=0x0, renderType=32788) at
> dri2_glx.c:213
> #13 0x0012bb91 in CreateContext (dpy=0x804e008, generic_id=146,
> config=0x8066cc0, shareList_user=0x0, allowDirect=1, code=3,
> renderType=32788, screen=0)
> at glxcmds.c:276
> #14 0x0012c023 in glXCreateContext (dpy=0x804e008,
> vis=0x805a6b8, shareList=0x0, allowDirect=1) at glxcmds.c:381
> #15 0x08048fc3 in print_screen_info (limits=0 '\000',
> allowDirect=1, scrnum=0, dpy=0x804e008) at glxinfo.c:430
> #16 main (argc=1, argv=0xbffff254) at glxinfo.c:1255
>
>
> I also verified that i'm using latest drm (66518ab). Is anyone
> else seeing similar errors? or am i missing something?
>
> Thanks
> Anuj
>
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> <mailto:mesa-dev at lists.freedesktop.org>
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
>
> That's a surprising failure, since that assertion would only be
> expected to be hit if brwInitFragProgFuncs() got called more than
> once on the same context. That in turn should only happen if the
> driver's CreateContext() function got called more than once on the
> same context, and it's hard to see how dri2CreateContextAttribs()
> would ever do that.
>
> Note: I've heard that there have been some build problems recently;
> have you tried building from scratch just to be sure? I happen to
> be reinstalling my OS today, so I've just done a clean build,
> install, and piglit run on mesa commit dc435ae, and everything looks
> fine.
>
>
> If a clean build doesn't help for you, I'd recommend either
> bisecting to try to see if a recent commit introduced the problem,
> or else using gdb to see if brwInitFragProgFuncs() is getting called
> multiple times, and if so, why.
>
> clean build didn't help. It shows assertion failure while executing
> brwInitFragProgFuncs() for the first time.
> A fresh clone of mesa git repository works fine.
>
> Thanks
> Anuj
I think you might have to throw out your lib/ directory. There's a bug
where it can pick up an old libdricore.so, or the one from your system,
which is pretty nasty. I think Eric was looking into a fix...
More information about the mesa-dev
mailing list