Bug 16582

Summary: [WINE] X crash when start Warcraft demo
Product: xorg Reporter: WuNian <nian.wu>
Component: Driver/intelAssignee: haihao <haihao.xiang>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: sokann
Version: 7.3 (2007.09)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 16084    
Attachments:
Description Flags
Xorg log none

Description WuNian 2008-07-02 02:06:21 UTC
Created attachment 17477 [details]
Xorg log

When start Warcraft demo, X crashed.
My platform: Cantiga

Source version:
Mesa: mesa_7_0_branch	9fa552eb0fb91d092f8a7df0e131696feda54130
Xserver: xserver_1.4_branch c3a7903f6a6a27e53ba0372408e0c5a68c608e86
Xf86_video_intel: 2.4 branch 45c1da56891723dd85153853885dd3b52a23c117
OSD: Fedora 9(kernel 2.6.25.6, including drm module)

The backtrace info:
#0  0x00110416 in __kernel_vsyscall ()
#1  0x00b2a660 in raise () from /lib/libc.so.6
#2  0x00b2c028 in abort () from /lib/libc.so.6
#3  0x081b7d5c in FatalError (f=0x3d53bc "lockup\n") at log.c:554
#4  0x0039a9fe in I830WaitLpRing (pScrn=0x9e52010, n=131064,
    timeout_millis=2000) at i830_accel.c:150
#5  0x0039ae45 in I830Sync (pScrn=0x9e52010) at i830.h:873
#6  0x003a8b65 in i830_stop_ring (pScrn=0x9e52010, flush=<value optimized out>)
    at i830_driver.c:1885
#7  0x003a8cb0 in I830LeaveVT (scrnIndex=0, flags=0) at i830_driver.c:3325
#8  0x080bbcc9 in xf86XVLeaveVT (index=0, flags=0) at xf86xv.c:1278
#9  0x003242ff in glxDRILeaveVT (index=0, flags=0) at glxdri.c:1001
#10 0x080a21f7 in AbortDDX () at xf86Init.c:1102
#11 0x081b7828 in AbortServer () at log.c:406
#12 0x081b7d47 in FatalError (f=0x3d53bc "lockup\n") at log.c:552
#13 0x0039a9fe in I830WaitLpRing (pScrn=0x9e52010, n=131064,
    timeout_millis=2000) at i830_accel.c:150
#14 0x0039ae45 in I830Sync (pScrn=0x9e52010) at i830.h:873
#15 0x003c304a in I830EXASync (pScreen=0x9e61870, marker=0) at i830_exa.c:154
#16 0x00366702 in exaWaitSync (pScreen=0x878) at exa.c:806
#17 0x003670b2 in exaPrepareAccess (pDrawable=0xa14a810, index=0) at exa.c:352
#18 0x0036aba9 in exaMoveInPixmap (pPixmap=0xa14a810) at exa_migration.c:223
#19 0x0036b277 in exaDoMigration (pixmaps=0xbfcc7a24, npixmaps=2, can_accel=1)
    at exa_migration.c:626
#20 0x0036c5e4 in exaTryDriverComposite (op=12 '\f', pSrc=0xa12cba8,
    pMask=0x0, pDst=0xa2895c0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=9,
    yDst=3, width=8, height=11) at exa_render.c:393
#21 0x0036cc34 in exaComposite (op=12 '\f', pSrc=0xa12cba8, pMask=0x0,
    pDst=0xa2895c0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=9, yDst=3, width=8,
    height=11) at exa_render.c:709
#22 0x0036e004 in exaGlyphs (op=3 '\003', pSrc=0xa08c818, pDst=0xa11a780,
    maskFormat=0x9e64e40, xSrc=35, ySrc=16, nlist=<value optimized out>,
    list=0xbfcc8238, glyphs=0xbfcc7e3c) at exa_render.c:1248
#23 0x0816be75 in damageGlyphs (op=3 '\003', pSrc=0xa08c818, pDst=0xa11a780,
    maskFormat=0x9e64e40, xSrc=35, ySrc=16, nlist=1, list=0xbfcc8238,
    glyphs=0xbfcc7e38) at damage.c:658
#24 0x08152afa in CompositeGlyphs (op=3 '\003', pSrc=0xa08c818,
    pDst=0xa11a780, maskFormat=0x9e64e40, xSrc=35, ySrc=16, nlist=1,
    lists=0xbfcc8238, glyphs=0xbfcc7e38) at picture.c:1785
#25 0x0815a4c7 in ProcRenderCompositeGlyphs (client=0xa0740a0) at render.c:1403
#26 0x081558c5 in ProcRenderDispatch (client=0x878) at render.c:2006
#27 0x08148f2e in XaceCatchExtProc (client=0xa0740a0) at xace.c:299
#28 0x0808726b in Dispatch () at dispatch.c:502
#29 0x0806e5e6 in main (argc=1, argv=0xbfcc8ad4, envp=Cannot access memory at address 0x880
) at main.c:452
Comment 1 Gordon Jin 2008-07-05 20:17:48 UTC
Does this happen on 965 too?
Comment 2 haihao 2008-07-08 18:17:09 UTC
Does Warcraft work well with mesa master?
Comment 3 WuNian 2008-07-09 01:01:29 UTC
Yes. Work fine with master.
Comment 4 haihao 2008-12-18 18:45:15 UTC
It works fine with current code. We don't fix mesa7.0 bug any more.

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.