I'm forwarding a Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/220345 Original Report: "Ever since I updated from gutsy to hardy, my Laptop freezes whenever I boot the system with kernel 2.6.24-16-generic and start an X session (kdm + kde) using the radeon open source driver. Most of the time I can still move the mouse pointer, but the rest of the system is not responding and I can't even switch to a tty. Other times the whole screen gets messed up and scrambled and even the mouse isn't responding any more. What's weird is, that I don't get that freeze if I boot the system with a mouse plugged into one of the Laptops USB ports. As long as I keep the mouse plugged, the system runs smooth, but as soon as I unplug the mouse, the system freezes. I worked around that bug by using the vesa driver for now. "My system: Acer TravelMate 4002LMi with Mobility Radeon 9700 (64 MB RAM)" Xorg.0.log: http://launchpadlibrarian.net/14080995/Xorg.0.log dmesg: http://launchpadlibrarian.net/14081011/dmesg.txt Here's a backtrace where it's stuck in RADEONWaitForIdleCP doing PolyPoint operations. (gdb) backtrace full #0 0xb7efe410 in __kernel_vsyscall () No symbol table info available. #1 0xb7d4ce99 in ioctl () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb7b62b42 in drmCommandNone () from /usr/lib/libdrm.so.2 No symbol table info available. #3 0xb7a74ca6 in RADEONWaitForIdleCP () from /usr/lib/xorg/modules/drivers//radeon_drv.so No symbol table info available. #4 0xb786babb in XAAPolyPointFallback (pDraw=0x8913758, pGC=0x85d64e8, mode=0, npt=1, pptInit=0x8ae87c8) at ../../../../hw/xfree86/xaa/xaaFallback.c:123 infoRec = (XAAInfoRecPtr) 0x8260520 oldFuncs = (GCFuncs *) 0xb78ae800 #5 0xb78abda9 in cwPolyPoint (pDst=0x8913758, pGC=0x85d64e8, mode=0, npt=1, ppt=0x8ae87c8) at ../../../miext/cw/cw_ops.c:253 pGCPrivate = (cwGCPtr) 0x85d6594 dst_off_x = 0 dst_off_y = 0 pBackingDst = (DrawablePtr) 0x8913758 pBackingGC = (GCPtr) 0x85d64e8 #6 0x08171fb6 in damagePolyPoint (pDrawable=0x8913758, pGC=0x85d64e8, mode=0, npt=1, ppt=0x8ae87c8) at ../../../miext/damage/damage.c:923 pGCPriv = (DamageGCPrivPtr) 0x85d65a8 oldFuncs = (GCFuncs *) 0x81e4660 #7 0x0808aa9a in ProcPolyPoint (client=0x84694b0) at ../../dix/dispatch.c:1883 pGC = (GC *) 0x85d64e8 pDraw = (DrawablePtr) 0x8913758 #8 0x0815075e in XaceCatchDispatchProc (client=0x84694b0) at ../../Xext/xace.c:281 major = 64 #9 0x0808d8df in Dispatch () at ../../dix/dispatch.c:502 result = <value optimized out> client = (ClientPtr) 0x84694b0 nready = 0 start_tick = 16780 #10 0x0807471b in main (argc=8, argv=0xbfa1f684, envp=Cannot access memory at address 0x644c ) at ../../dix/main.c:452 i = 1 error = 136163204 xauthfile = <value optimized out> alwaysCheckForInput = {0, 1} (gdb)
Alex, btw, I had him test a package with the dozen or so patches you mentioned to me at XDC, but reported they didn't solve it.
Hi, I'm the guy who filed that bug on launchpad. If you need further information, just let me know.
Have you gotten the latest hardy updates? I had a similar problem with some of the earlier hardy betas. It was not driver related as I was using a known working xserver and driver (self compiled). One of the hardy updates fixed it, but I don't know which. From you log it looks like the something is repeatedly calling the output->detect() routines, I had the same pattern in my log at the time. The mouse thing makes me think kernel. I'm guessing there some strange interaction in the kernel related to the mouse driver and the radeon drm. I vaguely recall a similar bug from a while back, but I can't find it at the moment. Can you try the following options (individually) and let me know if any of them help: Option "BusType" "PCI" Option "AGPMode" "1" Option "DRI" "FALSE"
Yes, my system is up to date. I kept installing all updates in the hope that one of them would fix the freezes, but the issue isn't solved by any update in the official repositories. If I add any of the options you suggested to my device section, the system works like a charm.
(In reply to comment #4) > If I add any of the options you suggested to my device section, the system > works like a charm. > Sounds like there's a bad interaction with AGP 4x and the mouse on your system. I think this comes back to the fact that AGP is broken by design.
*** This bug has been marked as a duplicate of bug 12934 ***
I just wanted to note that the issues described above and in bug 12934 started after an upgrade to a kernel with version > 2.6.22. I never had any problems with stability till I installed hardy (kernel 2.6.24). Alex experienced the problems when he switched to kernel 2.6.23. I don't know if that helps in any way, but if the bug is kernel related, it wasn't there in 2.6.22.
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.