Re: Flipping the switch to Mesa 21?
Robert Swindells <[email protected]> Wed, 24 Apr 2024 12:57:26 +0100
| Newsgroups | gmane.os.netbsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: >On Tue, Apr 23, 2024 at 08:53:54AM +0100, Robert Swindells wrote: > > > > Also have the Makefile changes to build libGLESv2 if we wanted to add > > that. > > Neat, wiz just said that there's a package trying to use it - x11/zutty, > and wondered whether we can add it. Looks like that package needs the GLESv3 headers, I had only installed the GLESv2 ones. Not worked out how to handle more than one target include directory in the Makefiles yet. I wanted GLESv2 to be able to build kmscube, one of the Panfrost developers had suggested it as a simpler test app than just starting X and seeing what happened. It isn't in pkgsrc so I had not made the changes to pkgtools/x11-links. The x11/zutty package builds for me now but complains about the 'C' locale when I run it and doesn't display text correctly. > If you can share the diff, that would be nice (or commit it, if you > prefer) I will clean up the Makefile a bit first. > > > rjs had reported a prior issue i don't recall, but this seems like a > > > good time to at least test, and we can revert if there's something > > > immediately bad to deal with.. > > > > I still get a core dump from glxgears on my one nouveau system, this > > didn't happen with Mesa 19. > > Can you share a backtrace? Thread 1 "" received signal SIGSEGV, Segmentation fault. 0x00007f7ff09a9435 in ?? () (gdb) bt #0 0x00007f7ff09a9435 in ?? () #1 0x00007f7fffffddf0 in ?? () #2 0x00007f7ff74746c0 in ?? () #3 0x00007f7ff24a4cfb in emit_vertices_i32 (count=<optimized out>, start=<optimized out>, ctx=<synthetic pointer>) at /u1/xsrc/external/mit/MesaLib/dist/src/gallium/drivers/nouveau/nv30/nv30_push.c:166 #4 nv30_push_vbo (nv30=<optimized out>, info=<optimized out>, draw=<optimized out>) at /u1/xsrc/external/mit/MesaLib/dist/src/gallium/drivers/nouveau/nv30/nv30_push.c:272 Backtrace stopped: Cannot access memory at address 0x5a I had tried adding more debug to this a while ago but didn't find anything obviously wrong.