Created attachment 26424 [details] xorg.0.log System Environment: -------------------------- Host: x-aspire1 Arch: i386 Platform: 945GME Libdrm: (master)00fae87f96e1fc5198311feec81866bf9c53d0e1 Mesa: (mesa_7_5_branch)fc7f92478286041a018ac4e72d2ccedeea7c0eca Xserver: (server-1.6-branch)5cd5a01259ba349f1868ca4af04207cf120d69e4 Xf86_video_intel: (master)ea0b00e675281b2914450992501566122f9affe0 Kernel: (for-linus)07f4f3e8a24138ca2f3650723d670df25687cd05 Bug detailed description: -------------------------- startx ,X will crash when run googleearth,it happens on i915 and i965 under both KMS and UMS.below is the backtrace: #0 drmmode_get_pipe_from_crtc_id (bufmgr=0x969b9a0, crtc=0x0) at drmmode_display.c:931 #1 0xb7e74c24 in I830DRI2CopyRegion (pDraw=0x99e4010, pRegion=0x99a82d8, pDstBuffer=0x99e2a30, pSrcBuffer=0x99e2a48) at i830_dri.c:319 #2 0xb7f5ecf5 in DRI2CopyRegion (pDraw=0x99e4010, pRegion=0x99a82d8, dest=0, src=1) at dri2.c:186 #3 0xb7f5f5d7 in ProcDRI2CopyRegion () at dri2ext.c:251 #4 ProcDRI2Dispatch (client=0x98a4cd8) at dri2ext.c:296 #5 0x0808676f in Dispatch () at dispatch.c:437 #6 0x0806c69d in main (argc=2, argv=0xbfeb1cf4, envp=Cannot access memory at address 0xa ) at main.c:397 Reproduce Steps: ----------------------- 1.xinit& 2.googleearth
Created attachment 26425 [details] xorg conf file
this should be fixed by b8e360bf2b77d28559d15a7c0f9c766848eb6ced in xf86-video-intel. Cheers, Julien
commit b8e360bf2b77d28559d15a7c0f9c766848eb6ced Author: Eric Anholt <eric@anholt.net> Date: Wed Jun 3 10:12:25 2009 +0000 Fix segfault in DRI2 vblank syncing if the region isn't onscreen. Also, fix some weirdness in the checking for whether the target was the screen.
verified with below commits: Libdrm: (master)2cb4c64d7310904b354365c2cbc263211e9eb4a1 Mesa: (master)9f6ec50f8c79283583eeebdebd16bf7dcd134816 Xf86_video_intel: (master)66ceedc0cc123e5c9f85f708b2e56d943f00e4b9 Xserver: (master)b6c16fc7dad5a4ffcaaab647c0e3fabed372efd5 Kernel: (for-linus)07f4f3e8a24138ca2f3650723d670df25687cd05
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.