[ANNOUNCE] xf86-video-intel-2.1.99

Robert Gerlach khnz at gmx.de
Mon Nov 12 07:37:39 PST 2007

Am Freitag 09 November 2007 18:48:30 schrieben Sie:
> On Friday, November 09, 2007 8:23 am Robert Gerlach wrote:
> > Hello,
> >
> > Am Freitag 09 November 2007 03:39:19 schrieb Jesse Barnes:
> > > Ok, the first Intel 2.2 pre-release is out, available at the usual
> > > locations (e.g.
> > > http://xorg.freedesktop.org/archive/individual/driver/).
> >
> > Works fine with my 855GME, except the issue I've reported (for i810
> > driver) some days ago.
> > (http://lists.freedesktop.org/archives/xorg/2007-November/030001.html)
> Is there a bug filed for this problem?  It's interesting that a sleep
> before doing the randr call makes things work...

The sleep delayed the randr calls only, so the functions are called after the 
resume phase - not in.

I've got nearly the same crash, if I call randr while on another console.

$ sudo chvt 1 ; sleep 1 ; xrandr -o normal

Program received signal SIGSEGV, Segmentation fault.
0x49473cbc in memcpy () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0x49473cbc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1  0xb7dcb642 in fbBlt (srcLine=0xaf330008, srcStride=4096, srcX=0, 
dstLine=0x300000, dstStride=4096, dstX=<value optimized out>, width=3072, 
height=256, alu=3, pm=4294967295,
    bpp=32, reverse=0, upsidedown=0) at ../../fb/fbblt.c:93
#2  0xb7dd70c8 in fbOddTile (dst=0x300000, dstStride=1024, dstX=0, 
width=24576, height=0, tile=0xaf330008, tileStride=1024, tileWidth=32768, 
tileHeight=768, alu=3,
    pm=4294967295, bpp=32, xRot=0, yRot=<value optimized out>) 
at ../../fb/fbtile.c:152
#3  0xb7dd718c in fbTile (dst=0x300000, dstStride=1024, dstX=0, width=24576, 
height=256, tile=0xaf330008, tileStride=1024, tileWidth=-1355612152, 
tileHeight=768, alu=3,
    pm=4294967295, bpp=32, xRot=0, yRot=768) at ../../fb/fbtile.c:200
#4  0xb7dd781e in fbFillRegionTiled (pDrawable=0x826eb38, pRegion=0x84749d0, 
pTile=0x83d3d90) at ../../fb/fbwindow.c:298
#5  0xb7dd7ad4 in fbPaintWindow (pWin=0x826eb38, pRegion=0x84749d0, what=0) 
at ../../fb/fbwindow.c:337
#6  0xb7d87634 in XAAPaintWindow (pWin=0x826eb38, prgn=0x84749d0, what=0) 
at ../../../../hw/xfree86/xaa/xaaPaintWin.c:192
#7  0xb7db5f3e in cwPaintWindowBackground (pWin=0x826eb38, pRegion=0x84749d0, 
what=0) at ../../../miext/cw/cw.c:459
#8  0x0816fe4f in damagePaintWindow (pWindow=0x826eb38, prgn=0x84749d0, 
what=0) at ../../../miext/damage/damage.c:1654
#9  0x08104b9d in compPaintWindowBackground (pWin=0x826eb38, 
pRegion=0x84749d0, what=0) at ../../composite/compwindow.c:253
#10 0x081209a2 in miWindowExposures (pWin=0x826eb38, prgn=0x84749d0, 
other_exposed=0x0) at ../../mi/miexpose.c:565
#11 0x080db3f5 in xf86XVWindowExposures (pWin=0x826eb38, reg1=0x84749d0, 
reg2=0x0) at ../../../../hw/xfree86/common/xf86xv.c:1063
#12 0x08136ac8 in miHandleValidateExposures (pWin=0x826eb38) 
at ../../mi/miwindow.c:470
#13 0x080d3036 in xf86SetRootClip (pScreen=0x8229890, enable=1) 
at ../../../../hw/xfree86/common/xf86Helper.c:1229
#14 0xb7d71133 in XAAEnableDisableFBAccess (index=0, enable=1) 
at ../../../../hw/xfree86/xaa/xaaInit.c:781
#15 0x080fc383 in xf86CursorEnableDisableFBAccess (index=0, enable=1) 
at ../../../../hw/xfree86/ramdac/xf86Cursor.c:210
#16 0x080f9c7b in xf86RandR12ScreenSetSize (pScreen=0x8229890, width=768, 
height=1024, mmWidth=270, mmHeight=203) 
at ../../../../hw/xfree86/modes/xf86RandR12.c:367
#17 0x0816b49e in RRScreenSizeSet (pScreen=0x8229890, width=0, height=<value 
optimized out>, mmWidth=270, mmHeight=203) at ../../randr/rrscreen.c:187
#18 0x0816bc0b in ProcRRSetScreenConfig (client=0x8458508) 
at ../../randr/rrscreen.c:914
#19 0x08165ad5 in ProcRRDispatch (client=0x300) at ../../randr/randr.c:486
#20 0x0814fcae in XaceCatchExtProc (client=0x8458508) at ../../Xext/xace.c:299
#21 0x0808d7ff in Dispatch () at ../../dix/dispatch.c:502
#22 0x0807467b in main (argc=6, argv=0xbfd25b14, envp=Cannot access memory at 
address 0x308
) at ../../dix/main.c:452

I don't know if this issue is related to the intel driver. Currently I think 
it's not.


More information about the xorg mailing list