OpenGL fails after server reset in RC2; can't test in RC3
Jin, Gordon
gordon.jin at intel.com
Tue Mar 27 19:10:07 PDT 2007
Marty Jack wrote:
> This is on a G965, builds from release tarballs of Mesa 6.5.2, server,
> xf86-video-intel.
>
> In pre-RC1, OpenGL applications did not work due to the DRM memory
> manager being disabled at X startup. Running glxinfo gave the
> assertion below. As I understand it, this was a problem with
> aperture memory allocation needing additional work.
>
> In RC1, OpenGL applications did work due to the improvements to memory
> allocation. This was an example of excellent progress. However,
> server reset ("logging out and in") left the display at the incorrect
> resolution.
>
> In RC2, the display resolution problem on server reset was fixed,
> which was another example of excellent progress, and OpenGL
> applications continued to work. However, after server reset I am
> experiencing a reproducible:
>
> $ glxinfo
> name of display: :0.0
> glxinfo: bufmgr_fake.c:746: bmGenBufferStatic: Assertion `0' failed.
> Aborted
>
> I am curious if anyone else is able to reproduce this.
I'm not seeing this in RC1, RC2 and RC3.
I suspect this may be fixed in Mesa after 6.5.2 release. I'm using Mesa
upstream code. Maybe you can also try that.
> In RC3, I am experiencing the problem that was reported with display
> blanking after server reset, so cannot determine if this is still
> happening. I have reverted to RC2 for now.
With display blanking, you still can test that will remote login.
-Gordon
More information about the xorg
mailing list