Those errors does not occur without VirtualGL. I've tried both locally
with GPU and
with llvmpipe software renderer in X proxy.
Sorry, I couldn't say if errors started after any system upgrade. I
didn't search /var/log/messages
for them before.
I've tried with same version of Gnome (3.28) on and AMD equipped host
and found no error there.
But OS is Fedora 28, not RHEL7. So I'm not completely sure.
I've tried to catch the first error (Out of memory) with gdb. I think
the report is wrong:
glGetError() returns GL_OUT_OF_MEMORY even before glTexImage2D() is
called, so I guess
glGetError() is just sampled at a wrong time.
The call causing the error looks this one, rather:
self->gl_x11_sync = meta_gl_import_sync (GL_SYNC_X11_FENCE_EXT,
self->xfence, 0);
at compositor/meta-sync-ring.c:354
The the specific configuration causing this issue for me:
OS: RHEL 7.6
Video card: Quadro K600
Driver version: NVIDIA 430.26
Gnome version: 3.28 (gnome-shell 3.28.3)
-
Marcello.
On 09/08/2019 16:45, DRC wrote:
Do these errors occur without VirtualGL? Please test both locally, with
GPU acceleration, and using the software OpenGL implementation in your X
proxy.
Did these errors start occurring recently (for instance, due to a system
update)?
Do these errors occur with multiple underlying OpenGL stacks (for
instance, nVidia and AMD)?
As near as I can figure, the errors are being triggered by the following
OpenGL functions:
journal: driver/gl/gl/cogl-texture-driver-gl.c:494: GL error (1285):
glTexImage2D() or glGetTexLevelParameteriv()
journal: driver/gl/cogl-buffer-gl.c:87: GL error (1281): Invalid value
glGenBuffers()
journal: driver/gl/cogl-clip-stack-gl.c:463: GL error (1281):
Invalid value
glDisable (GL_STENCIL_TEST)
journal: driver/gl/cogl-framebuffer-gl.c:157: GL error (1281):
Invalid value
glViewport()
I can't conceive of any reason why VirtualGL would be causing those
errors. Once VirtualGL redirects the rendering context to a Pbuffer on
the 3D X server, it steps out of the way. The errors are much more
likely to be due to an application bug (in this case, a COGL bug) or a
bug in the underlying OpenGL stack. However, do perform the diagnosis I
suggested above, and if it indicates that the bugs are indeed isolated
to VirtualGL, then send me more information about the specific
configuration that triggers them, and I can try to reproduce.
On 8/9/19 5:54 AM, Marcello Blancasio wrote:
Accelerating Gnome 3.28 in RHEL 7.6 with VirtualGL works fine, excepted
some GL errors found in /var/log/messages.
This message is issued once, at the beginning:
journal: driver/gl/gl/cogl-texture-driver-gl.c:494: GL error (1285):
Out of memory
then this one:
journal: driver/gl/cogl-buffer-gl.c:87: GL error (1281): Invalid value
and a lot ot these two kinds:
journal: driver/gl/cogl-clip-stack-gl.c:463: GL error (1281): Invalid
value
journal: driver/gl/cogl-framebuffer-gl.c:157: GL error (1281): Invalid
value
As I monitored message log with tail -f , I noticed that those last two
kinds of messages are issued when some screen update occur (e.g. when
caret blinks inside a gnome-terminal window).
Regards.
--
You received this message because you are subscribed to the Google Groups "VirtualGL
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/virtualgl-users/ecae53f8-977f-c66c-86b3-8226c84d70a7%40gmail.com.
