Comment # 27
on bug 53111
from Alexandre Demers
(In reply to comment #21) > (In reply to comment #20) > > (In reply to comment #19) > > > So about this locking piglit test (depthstencil-render-miplevels 146 > > > s=z24_s8_d=z32f_s8), I've been able to track it down to: > > > line 218: piglit_report_result(PIGLIT_SKIP); > > > > How did you determine that? It's weird, I wouldn't expect a skipped test to > > produce any actual GPU rendering. > > I used gdb and step into the code until it locked. It gets out at level 0, > after going through: > > /** > * Attach the proper miplevel of each texture to the framebuffer > */ > void > set_up_framebuffer_for_miplevel(int level)... > > Before this call, there is a framebuffer initialization: > GLuint fbo; > glGenFramebuffers(1, &fbo); > glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); > glBindFramebuffer(GL_READ_FRAMEBUFFER, fbo); > > for (int level = 0; level <= max_miplevel; ++level) { > set_up_framebuffer_for_miplevel(level); It seems that with latest mesa, drm, xf86 and kernel 3.7.0-rc7-71633-g3b6b59b from drm-next, it doesn't fail on this test anymore. It does lock however on a different one. I'll debug it and see where it locks.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
