I just wanted to play neverball/neverput, moved the mouse over the menu and the whole system froze. I am running on Debian unstable and tried the CVS Version of Mesa from the debian archive (6.5.0.cvs.20060524-1). I also and I am running currently the self compiled cvs Version of mesa, libdrm and drm kernel module.
ok, I just reproduced the freeze by spinning the starting cube in blender - just spinning it a few times sends the system into an unresponsive state I checked over the network, the system was unresponsive I forgot to mention the relevant driver and hardware. The hardware is a Mobile Radeon 9600 M10 - running with the r300 driver.
What is your DDX version ? Can you try to first run an xserver with fglrx driver then use the ati driver. We are missing some initialization on radeon card that fglrx have. I think your lockup is related to this.
I tried to run the fglrx first I did this: 1. run X -config /etc/X11/xorg-fglrx.conf 2. rmmod fglrx 3. run "normal Session" and it freezes. The DDX is the 2D Part of the driver? I took the ati driver from the X.org 7.1 Release and compiled it for my install. Forcing to indirect rendering leeds to no freezes so I asumed a problem in the r300 driver. I'll attach the startup log and my xorg.conf (the "ATI Technologies, Inc. RV350 [Mobility Radeon 9600 M10]-Dual" Section is freezing - I'll try the singlehead version now).
Created attachment 5827 [details] Startup without fglrx
Created attachment 5828 [details] xorg.conf
ok, it's no problem in the r300 driver, but the combination of the xorg 7.0 and the 7.1 radeon DDX. switching back to the 7.0 DDX made neverball/neverputt+blender work like a charm ... Now running the old ddx with Mesa CVS works and I think we can close the bug :-/ And for the record the chipset works without the help of fglrx
Ok, but you might experience lockup there not consistant and may take some times to happen. I hope you won't experience such, if you do please don't reopen a bug there are already bug opened for that.
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.