radeon git slackware-current (32 and 64) X lockup

forum1793 · 07-17-2009, 07:50 PM

Hi,

I'm not sure if any other slackers are trying out the changes to drm/mesa/ati/radeonhd gits for 3D in AMD/ATI HD graphics cards.

But with the recent changes, including xorg-server, X is hard-locking. Luckily the front power button is working so I don't have to go through fsck every time. This only impacts using the experimental 3D code. The hard locks did not occur before the recent package upgrades. Is there a simple way to revert these one at a time to see which offends? My guess is one of the xorg-server packages.

Recent package changes are:

Code:

/var/log/packages/dri2proto-2.1-i486-1
/var/log/packages/inputproto-1.5.1-noarch-1
/var/log/packages/libFS-1.0.2-i486-1
/var/log/packages/libXaw-1.0.6-i486-1
/var/log/packages/libXt-1.0.6-i486-1
/var/log/packages/mozilla-firefox-3.5.1-i686-1
/var/log/packages/pixman-0.15.16-i486-1
/var/log/packages/util-macros-1.2.2-noarch-1
/var/log/packages/xf86-video-cirrus-1.3.1-i486-1
/var/log/packages/xf86-video-dummy-0.3.2-i486-1
...
/var/log/packages/xf86-video-voodoo-1.2.2-i486-1
/var/log/packages/xorg-server-1.6.2-i486-1
/var/log/packages/xorg-server-xephyr-1.6.2-i486-1
/var/log/packages/xorg-server-xnest-1.6.2-i486-1
/var/log/packages/xorg-server-xvfb-1.6.2-i486-1

forum1793 · 07-17-2009, 09:06 PM

[edit] I should point out I had to compile a pre 2.6.29 kernel to do this and am using a 2.6.27.xx kernel. Those of you running the current 2.6.29.6 kernel will probably not be able to try this code and should not get these lockups.

Also getting lockups with the experimental code and radeonhd.

The lockup only seems to occur when opening window in X, such as terminal or firefox, clicking on top bar, and dragging. Upon only slight movement the screen (basically everything) locks up.

The lock up does not occur if in the section with driver radeon, I use Option "DRI" "off". Not sure if these observations help isolate or not to which recent package change is causing problem.

forum1793 · 07-18-2009, 07:08 AM

As posted in similar thread, changing pixman back to 0.15.10 resolved this problem.