[Bug 93048] [CTS regression] mesa af2723 breaks GL Conformance for debug extension

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Dec 5 03:28:42 PST 2015


--- Comment #10 from Emil Velikov <emil.l.velikov at gmail.com> ---
(In reply to Mark Janes from comment #9)
> Emil: can you explain why the cts test still fails on g33?  
> This doesn't seem like the kind of test that would be hardware specific.
Indeed it's not.

> g33 wouldn't be in the CI results that you got, because the machine is to
> old/slow to complete in a reasonable time.  The test failed on a nightly run.
Can you point me out to a PCI ID, so that I can check which path gets executed
on the said platform. I doubt that I'll find such a platform in the wild to do
some actual debugging.

> /tmp/build_root/m64/bin/cts/glcts
> --deqp-case=ES2-CTS.gtf.GL2ExtensionTests.debug.debug
> dEQP Core GL-CTS-2.0 (0x0052484b) starting..
>   target implementation = 'intel-gbm'
> Test case 'ES2-CTS.gtf.GL2ExtensionTests.debug.debug'..
> #+ Initial value for GL_DEBUG_GROUP_STACK_DEPTH is 0 but it should be 1
And here comes the strange part... the default (1) stack is allocated via
_mesa_lock_debug_state/debug_create, which gets executed by all khr_debug entry
points (iirc). Thus I'm wondering how it's possible for this to fail.

> #+ Initial state for GL_DEBUG_OUTPUT is not enabled
>   Fail (Fail)
While this one is even stranger - as we attempt to set DEBUG_OUTPUT (via the
dri layer), _mesa_set_debug_state_int gets called, which fails to set the flag
only if the _mesa_lock_debug_state/debug_create combo above also fails.

Can you set MESA_DEBUG=1 and LIBGL_DEBUG=verbose and attach (or email) the

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20151205/e5831c93/attachment.html>

More information about the intel-3d-bugs mailing list