Bug 22374 - [GM965] compiz crashes in intel_renderbuffer_set_region at intel_fbo.c:348
Summary: [GM965] compiz crashes in intel_renderbuffer_set_region at intel_fbo.c:348
Status: RESOLVED DUPLICATE of bug 22408
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium critical
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20570
  Show dependency treegraph
 
Reported: 2009-06-19 13:14 UTC by Peter
Modified: 2009-06-22 13:59 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
intel-gpu-dump.dump.gz (125.17 KB, application/gzip)
2009-06-19 13:14 UTC, Peter
no flags Details

Description Peter 2009-06-19 13:14:26 UTC
Created attachment 26964 [details]
intel-gpu-dump.dump.gz

Today I've upgraded up to:

linux kernel: today's intel-drm-next state (52dc7d3)
libdrm: today's git (2fa2db1)
xserver: today's git, server-1.6-branch branch (dbac41b)
mesa: today's git, mesa_7_4_branch branch (afe0ca1)
xf86-video-intel: today's git (534e73a)

Now xserver starts, but after I ran compiz it crashs with the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffe573d66f0 (LWP 27913)]
intel_renderbuffer_set_region (rb=0x5590550, region=0x0) at intel_fbo.c:348
348     intel_fbo.c: No such file or directory.
        in intel_fbo.c
(gdb) bt
#0  intel_renderbuffer_set_region (rb=0x5590550, region=0x0) at intel_fbo.c:348
#1  0x00007ffe5307bb55 in intelDestroyBuffer (driDrawPriv=0x558ffd0) at intel_screen.c:394
#2  0x00007ffe5306ac03 in driDestroyDrawable (pdp=0x558ffd0) at ../common/dri_util.c:503
#3  0x00007ffe53e4d706 in __glXDRIdrawableDestroy (drawable=0x558fed0) at glxdri2.c:105
#4  0x00007ffe53e42dfd in DrawableGone (glxPriv=0x558fed0, xid=0) at glxext.c:136
#5  0x0000000000435c93 in FreeResource (id=39845891, skipDeleteFuncType=0) at resource.c:561
#6  0x000000000044a0db in ProcDestroyWindow (client=0x51e0650) at dispatch.c:581
#7  0x000000000044d454 in Dispatch () at dispatch.c:437
#8  0x000000000043344d in main (argc=9, argv=0x7fff7eae97e8, envp=<value optimized out>) at main.c:397

I'm unsure if it's interesting but I'm attaching intel_gpu_dump output.
Comment 1 Peter 2009-06-19 13:15:01 UTC
And this is output of bt full:

(gdb) bt full
#0  intel_renderbuffer_set_region (rb=0x5590550, region=0x0) at intel_fbo.c:348
        old = (struct intel_region *) 0x0
#1  0x00007ffe5307bb55 in intelDestroyBuffer (driDrawPriv=0x558ffd0) at intel_screen.c:394
        intel_fb = (struct intel_framebuffer *) 0x5590070
        depth_rb = <value optimized out>
        stencil_rb = <value optimized out>
#2  0x00007ffe5306ac03 in driDestroyDrawable (pdp=0x558ffd0) at ../common/dri_util.c:503
No locals.
#3  0x00007ffe53e4d706 in __glXDRIdrawableDestroy (drawable=0x558fed0) at glxdri2.c:105
No locals.
#4  0x00007ffe53e42dfd in DrawableGone (glxPriv=0x558fed0, xid=0) at glxext.c:136
        c = (__GLXcontext *) 0x1
#5  0x0000000000435c93 in FreeResource (id=39845891, skipDeleteFuncType=0) at resource.c:561
        rtype = 53
        cid = <value optimized out>
        res = (ResourcePtr) 0x5590670
        prev = (ResourcePtr *) 0x5107198
        head = (ResourcePtr *) 0x5107198
#6  0x000000000044a0db in ProcDestroyWindow (client=0x51e0650) at dispatch.c:581
        pWin = (WindowPtr) 0x4f4f0b0
        rc = 1
#7  0x000000000044d454 in Dispatch () at dispatch.c:437
        result = 0
        client = (ClientPtr) 0x51e0650
        nready = 0
        start_tick = 3700
#8  0x000000000043344d in main (argc=9, argv=0x7fff7eae97e8, envp=<value optimized out>) at main.c:397
        i = 1
        alwaysCheckForInput = {0, 1}
Comment 2 Peter 2009-06-19 13:16:04 UTC
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Comment 3 Alex Bennee 2009-06-22 01:02:37 UTC
Ahh #22408 which I just raised looks like a dupe of this although I'm not running git versions of everything and my crash occurs as xdm logs in (I assume when compiz fires up).
Comment 4 Alex Bennee 2009-06-22 13:59:04 UTC

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


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.