xf86-video-intel 1.9.94: occasional X server crash

Wang Zhenyu zhenyu.z.wang at intel.com
Thu Apr 5 19:34:21 PDT 2007


On 2007.04.05 11:59:42 +0000, Andrew Barr wrote:
> This happens about every 4 or 5 resumes from suspend-to-RAM:
> 
> (II) AIGLX: Resuming AIGLX clients after VT switch
> (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007df000 (pgoffset
> 2015)
> (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x007e0000 (pgoffset
> 2016)
> (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x007e4000 (pgoffset
> 2020)
> (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x007e5000 (pgoffset
> 2021)
> (II) intel(0): xf86BindGARTMemory: bind key 4 at 0x007e9000 (pgoffset
> 2025)
> (II) intel(0): xf86BindGARTMemory: bind key 5 at 0x007f0000 (pgoffset
> 2032)
> (II) intel(0): xf86BindGARTMemory: bind key 6 at 0x03800000 (pgoffset
> 14336)
> (II) intel(0): xf86BindGARTMemory: bind key 7 at 0x04000000 (pgoffset
> 16384)
> (II) intel(0): xf86BindGARTMemory: bind key 8 at 0x04800000 (pgoffset
> 18432)
> (WW) intel(0): PRB0_HEAD (0x00000000) and PRB0_TAIL (0x0001a8a0)
> indicate ring buffer not flushed
> (WW) intel(0): Existing errors found in hardware state.
> (II) intel(0): Output configuration:
> (II) intel(0):   Pipe A is on
> (II) intel(0):   Display plane A is now enabled and connected to pipe A.
> (II) intel(0):   Pipe B is on
> (II) intel(0):   Display plane B is now enabled and connected to pipe B.
> (II) intel(0):   Output VGA is connected to pipe A
> (II) intel(0):   Output LVDS is connected to pipe B
> (II) intel(0): [drm] dma control initialized, using IRQ 11
> 
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c2074]
> 1: [0xffffe420]
> 2: /usr/bin/X [0x80d7805]
> 3: /usr/bin/X(TraverseTree+0x2d) [0x807257d]
> 4: /usr/bin/X(WalkTree+0x38) [0x80725f8]
> 5: /usr/bin/X [0x80d7896]
> 6: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c3717f]
> 7: /usr/bin/X(xf86Wakeup+0x3d9) [0x80c37e9]
> 8: /usr/bin/X(WakeupHandler+0x65) [0x808c1b5]
> 9: /usr/bin/X(WaitForSomething+0x1b4) [0x81b07c4]
> 10: /usr/bin/X(Dispatch+0x81) [0x80882a1]
> 11: /usr/bin/X(main+0x489) [0x80701f9]
> 12: /lib/i686/cmov/libc.so.6(__libc_start_main+0xd8) [0xb7d5aea8]
> 13: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806f531]
> 
> Fatal server error:
> Caught signal 11.  Server aborting
> 
> (II) AIGLX: Suspending AIGLX clients for VT switch
> (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
> (II) intel(0): xf86UnbindGARTMemory: unbind key 5
> 
> Server restarts successfully, however, no reboot is required. 
> 

If this is true, that means agp doesn't screwd up, and was restored ok
when resuming. So that's probably not a driver issue... dmesg will help.
Could you file a bug for this?



More information about the xorg mailing list