Bug 35260

Summary: Xorg crashing on prepare_wm_surfaces when invoking kwin switch window effects
Product: Mesa Reporter: Raúl <rasasi78>
Component: Drivers/DRI/i965Assignee: Eric Anholt <eric>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium    
Version: 7.10   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Backtrace and full backtrace.

Description Raúl 2011-03-12 17:03:33 UTC
Created attachment 44407 [details]
Backtrace and full backtrace.

Hello:

  I had this crash when I invoked the Kwin present windows effect with alt-tab. Here is my system information and attached the bt full.

  Please, let me know if you need further info.

Debian sid with experimental kernel.
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03)

Linux portaka 2.6.38-rc7-amd64 #1 SMP Tue Mar 8 17:17:06 UTC 2011 x86_64 GNU/Linux
libdrm 2.4.23
mesa 7.10
xserver-xorg-core 1.9.4.90
xserver-xorg-video-intel 2.14.0

#0  0x00007f3243223165 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007f3243225f70 in abort () at abort.c:92
#2  0x000000000045d95e in OsAbort () at ../../os/utils.c:1274
#3  0x000000000046b6ad in ddxGiveUp () at ../../../../hw/xfree86/common/xf86Init.c:940
#4  0x0000000000465ffd in AbortServer () at ../../os/log.c:424
#5  0x00000000004667d0 in FatalError (f=0x57e7c0 "Caught signal %d (%s). Server aborting\n") at ../../os/log.c:552
#6  0x0000000000464d9e in OsSigHandler (signo=11, sip=0x288, unused=<value optimized out>) at ../../os/osinit.c:156
#7  <signal handler called>
#8  0x00007f324063cc80 in prepare_wm_surfaces (brw=0x1f83c30) at brw_wm_surface_state.c:623
#9  0x00007f3240624a06 in brw_validate_state (brw=0x1f83c30) at brw_state_upload.c:397
#10 0x00007f32406138ec in brw_try_draw_prims (ctx=0x1f83c30, arrays=0x594c068, prim=0x594a784, nr_prims=1, ib=0x0, index_bounds_valid=<value optimized out>, 
    min_index=0, max_index=3) at brw_draw.c:362
#11 brw_draw_prims (ctx=0x1f83c30, arrays=0x594c068, prim=0x594a784, nr_prims=1, ib=0x0, index_bounds_valid=<value optimized out>, min_index=0, max_index=3)
    at brw_draw.c:447
#12 0x00007f32406ff832 in vbo_exec_vtx_flush (exec=<value optimized out>, unmap=<value optimized out>) at vbo/vbo_exec_draw.c:381
#13 0x00007f32406fd57c in vbo_exec_FlushVertices_internal (ctx=<value optimized out>, unmap=<value optimized out>) at vbo/vbo_exec_api.c:911
#14 0x00007f32406fd74a in vbo_exec_FlushVertices (ctx=<value optimized out>, flags=1) at vbo/vbo_exec_api.c:945
#15 0x00007f324069a10e in _mesa_MatrixMode (mode=5890) at main/matrix.c:153
#16 0x00007f3241c96563 in __glXDisp_Render (cl=<value optimized out>, pc=0x86b7494 "\b") at ../../glx/glxcmds.c:1847
#17 0x00007f3241c9a8a2 in __glXDispatch (client=0x597fa40) at ../../glx/glxext.c:600
#18 0x0000000000432e89 in Dispatch () at ../../dix/dispatch.c:432
#19 0x00000000004257ab in main (argc=8, argv=0x7fffa6e6d6c8, envp=<value optimized out>) at ../../dix/main.c:291
Comment 1 Chris Wilson 2011-03-14 09:59:02 UTC
Would it be impolite to point out that you are running indirect on the local host and that this bug already has an immediate fix, but the root cause is a likely to be a memory/object leak by the client?

commit 13bab58f04c1ec6d0d52760eab490a0997d9abe2
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Feb 18 17:51:10 2011 +0000

    i965: Fallback on encountering a NULL render buffer
    
    Following a GPU hang, or other error, the render target is not likely to
    have an allocated BO and so we must fallback to avoid using it.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=32534
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

*** This bug has been marked as a duplicate of bug 32534 ***
Comment 2 Raúl 2011-03-14 15:10:01 UTC
Hello and thanks for the quick answer. May I lack of english language precision, but this is what I got from your answer:

>you are running indirect on the local host
mmm, if you refer to indirect rendering, I'm not sure about this. From the X log I get:
[   186.604] (II) intel(0): direct rendering: DRI2 Enabled

>and that this bug already has an immediate fix
I'm sorry about this is a dupe, I came accross the original one, but I was unable to position it on the mesa tree/branches so I wasn't sure the version I run included the fix or not.

>the root cause is a likely to be a memory/object leak by the client
ok, so KWin to blame, right?

Anyway I understand this bug is a stupid load for the work you are doing and which I appreciate, so don't feel in the obligation to answer this. As I said I'm more than happy with your answer and with a fix. And no, you are not impolite, it's me not having been careful enough.

Regards,

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.