Getting crash with new X, Intel driver - Warcraft

Joshua Rodman <[email protected]> Thu, 3 May 2007 15:00:56 -0700
Newsgroups gmane.comp.video.dri.user
Message-ID <[email protected]>
Hi DRI folks,

I upgraded (in debian) to XOrg 7.2 yesterday, updating the mesa dri
drivers, mesa itself, xorg, and the intel x driver.  I'm an amd64 user.

First dri wasn't working, but it turns out this was because of my
unhelpful VideoRam entry in the xorg.conf. I removed this, and dri
worked again.

This version of the driver has all kinds of things working nicely that
were not working nicely in the old version from months ago that I was
using.  Great show.

Some problems though; 

1 - performance is quite bad. for example, foobillard is getting
framerates that resemble software, 640x480 resolution and the framerates
are under 10 a second.  This is a fairly simple 3d app.  A pooltable,
some balls, a cue.  Not sure what to try.

2 - Stability isn't so great.  gltron crashes frequently, although this
may be gltron's fault since the last time I mucked around with it, i was
on i386.  Launching World of Warcraft under WINE causes an X server
crash:
 
 Backtrace:
 0: /usr/bin/X11/X(xf86SigHandler+0x6d) [0x47ea8d]
 1: /lib/libc.so.6 [0x2b2461498ca0]
 2: /usr/lib/xorg/modules/extensions//libGLcore.so(xmesa_check_and_update_buffer_size+0xc) [0x2b2472ec7c4c]
 3: /usr/lib/xorg/modules/extensions//libGLcore.so [0x2b2472ec714d]
 4: /usr/lib/xorg/modules/extensions//libglx.so [0x2b2461eada3b]
 5: /usr/bin/X11/X(ResizeChildrenWinSize+0x1bb) [0x438f1b]
 6: /usr/bin/X11/X [0x48a24a]
 7: /usr/bin/X11/X(xf86EnableDisableFBAccess+0xa1) [0x48a681]
 8: /usr/bin/X11/X [0x4b2db0]
 9: /usr/bin/X11/X [0x4b1103]
 10: /usr/bin/X11/X(ProcRRSetScreenConfig+0x49f) [0x51d8df]
 11: /usr/bin/X11/X(Dispatch+0x1cb) [0x44a06b]
 12: /usr/bin/X11/X(main+0x45d) [0x43314d]
 13: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b24614858e4]
 14: /usr/bin/X11/X(FontFileCompleteXLFD+0xa1) [0x432449]

 Fatal server error:
 Caught signal 11.  Server aborting

 (II) intel(0): xf86UnbindGARTMemory: unbind key 0
 (II) intel(0): xf86UnbindGARTMemory: unbind key 1
 (II) intel(0): xf86UnbindGARTMemory: unbind key 2
 (II) intel(0): xf86UnbindGARTMemory: unbind key 3
 (II) intel(0): xf86UnbindGARTMemory: unbind key 4

It's quite possible this is a Debian error, or a user error.  Do you
have any suggestions on how I can narrow this down or report the problem
more completely or in a better way etc?

-josh

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
--