Bug 13005

Summary: X locks up when running compiz on cloned screen with XRandR
Product: xorg Reporter: Johan Bilien <jobi>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: VERIFIED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.3 (2007.09)   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Description Flags
configuration none

Description Johan Bilien 2007-10-30 05:24:58 UTC
Sorry for this very vague report, I'm happy to provide any more info you might need.

I run xserver 1.3 with the ATI driver 6.7.195, on a M22 (X300), on a thinkpad T43.
I use XAA and AIGLX.

When running compiz on a single display (LVDS), it works fine. However when I run it when 2 monitors are connected, it runs for a few seconds, then always ends up locking up the system after a few operations on windows.

$ xrandr 
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1200
VGA-0 disconnected (normal left inverted right)
DVI-0 connected 1600x1200+0+0 (normal left inverted right) 518mm x 324mm
   1600x1200      60.0*+
   1280x1024      69.8     59.9  
   1152x864       75.0  
   1024x768       84.9     75.1     60.0  
   832x624        74.6  
   800x600        84.9     75.0     60.3  
   640x480        84.6     75.0     60.0     59.4  
   720x400        70.1  
LVDS connected 1400x1050+0+0 (normal left inverted right) 0mm x 0mm
   1400x1050      50.0*+
   1280x1024      59.9  
   1280x960       59.9  
   1280x800       60.0  
   1280x768       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
S-video disconnected (normal left inverted right)
Comment 1 Johan Bilien 2007-10-30 05:30:20 UTC
Turning off the LVDS when the DVI monitor is connected seems to prevent the lockups, so it really seems related to having 2 outputs turned on.
Comment 2 Alex Deucher 2007-10-30 19:17:01 UTC
Can you get a backtrace from the server when the crash happens?  Also can you attach your xorg.conf and xorg log (including anything that may be output from the crash).
Comment 3 Johan Bilien 2007-10-31 00:26:53 UTC
Created attachment 12270 [details]

I attach the configuration file. There is no stack trace as the server hangs, it doesn't crash. I could try to attach gdb if you think that would help.
Comment 4 Michel Dänzer 2007-10-31 00:32:24 UTC
(In reply to comment #3)
> I attach the configuration file. There is no stack trace as the server hangs,
> it doesn't crash. I could try to attach gdb if you think that would help.

Yes, I think that's what Alex meant. :)
Comment 5 Johan Bilien 2007-11-05 00:57:51 UTC
Sorry I don't have debug symbols in the mouse driver, I can recompile it if it helps.

(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e10919 in ioctl () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7f3ad04 in drmGetLock () from /usr/lib/libdrm.so.2
#3  0xb7f45992 in DRILock (pScreen=0x822f940, flags=0)
    at ../../../../hw/xfree86/dri/dri.c:1900
#4  0xb7b809c8 in radeon_crtc_show_cursor ()
   from /usr/lib/xorg/modules/drivers//radeon_drv.so
#5  0x080fb85f in xf86_crtc_show_cursor (crtc=0xb7bb8cf4)
    at ../../../../hw/xfree86/modes/xf86Cursors.c:236
#6  0x080fba9d in xf86_set_cursor_position (scrn=0x8217b98, x=360, y=1031)
    at ../../../../hw/xfree86/modes/xf86Cursors.c:325
#7  0x0812f4aa in miPointerMove (pScreen=0x822f940, x=366, y=1034,
    time=252064599) at ../../mi/mipointer.c:485
#8  0x0812f570 in miPointerAbsoluteCursor (x=366, y=1034, time=252064599)
    at ../../mi/mipointer.c:454
#9  0x080e8cbf in xf86PostMotionEvent (device=0x82904f8, is_absolute=0,
    first_valuator=0, num_valuators=2)
    at ../../../../hw/xfree86/common/xf86Xinput.c:1055
#10 0xb7b57874 in ?? () from /usr/lib/xorg/modules/input//mouse_drv.so
#11 0x082904f8 in ?? ()
#12 0x00000000 in ?? ()
Comment 6 Michel Dänzer 2007-11-05 02:05:28 UTC
Should be fixed in Git, please reopen if not. However, some cards will be affected by bug 12245 for now.
Comment 7 Johan Bilien 2007-11-05 03:08:11 UTC
Thanks, no lockups so far.

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.