Bug 26939

Summary: 3D applications hang in full screen mode
Product: DRI Reporter: maximlevitsky
Component: DRM/IntelAssignee: Jesse Barnes <jbarnes>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
compiz backtrace
none
etracer backtrace none

Description maximlevitsky 2010-03-07 08:40:08 UTC
Created attachment 33833 [details]
compiz backtrace

Environment:

drm:        581cafbc2493ad97ada41f03c8dd70f9ec4bf19d
mesa:       690ded32cdda4363c30aca32ef94383ba356a3c5
X server:   bbae92795c7eab062e6722c42fa7915e0cee5d69
xf86_intel: 1cd556420277f103c47ade422f3ec8f8efb2d282
kernel:     4da0b66c6e9ea7ba78a19f9f186779826d89f8b0

DG965RY Intel motherboard with VGA connector connected to an LCD

I do:
export SDL_VIDEO_X11_XRANDR=1
(The above turns on Xrandr support in the SDL, because xvidmode was removed)

And start an SDL application, it freezes.

I attack backtrace of etracer and compiz.
Note that compiz hangs in same way, and always.

The interesting part of the backtrace is:

#5  0xb7565a30 in DRI2GetBuffersWithFormat (dpy=0x86bda50, drawable=97, width=0x882e47c, height=0x882e480, attachments=0xbff6e69c, count=2, 
    outCount=0xbff6e6c8) at dri2.c:428

#6  0xb7563f62 in dri2GetBuffersWithFormat (driDrawable=0x882e458, width=0x882e47c, height=0x882e480, attachments=0xbff6e69c, count=2, out_count=0xbff6e6c8, 
    loaderPrivate=0x882e3b8) at dri2_glx.c:435

#7  0xb6f6cbf3 in intel_update_renderbuffers (context=0x883dcd8, drawable=0x882e458) at intel_context.c:253

Note that older mesa, 465fee75ee8991349da742e5a1a5be3cd179bb62 doesn't have that problem. Maybe I should do an bisect.
Comment 1 maximlevitsky 2010-03-07 08:40:34 UTC
Created attachment 33834 [details]
etracer backtrace
Comment 2 Jesse Barnes 2010-04-06 11:43:26 UTC
I think this is a dupe

*** This bug has been marked as a duplicate of bug 27040 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.