Description of problem: Vanilla kernels (i.e. 2.6.27, next-20081128, next-20081219) which worked fine with Fedora 9 hang randomly with Fedora 10 on my Pentium M / 855PM / RV350 laptop. Fedora kernels are not affected since they ship and use CONFIG_DRM_RADEON_KMS. Version-Release number of selected component (if applicable): all fc10 versions including xorg-x11-drv-ati-6.9.0-62.fc10.i386 How reproducible: fully reproducable Steps to Reproduce: 1. get kernel from kernel.org 2. build it 3. try to use it Actual results: hang Expected results: no hang Additional info: Downgrading driver to xorg-x11-drv-ati-6.8.0-19.fc9.i386 fixes hangs. Same for rebuilding xorg-x11-drv-ati-6.9.0-61.fc10 and reverting radeon-gem-cs branch's commit 5c5736604e6a1bc280821bd92f3714e0c9e7d7d3 ("radeon: no need for this anymore"). Sorry but narrowing it down further the issue is impossible without some help due to complete lack of radeon-gem-cs's bisectability between: commit 44fb767aa95e5f0725386106b89d0782fd53b768 ("radeon: fixup modesetting code after rebasing to master") and commit 12e71eaf7999520d23d50cfbcfc0299b2bdf7a9d ("port to using drm header files") With xorg-x11-drv-ati-6.9.0-62.fc10 things got worse as it lockups on gdm login screen (surprisingly mouse is still working but that's it...). More details at: http://lkml.org/lkml/2008/12/13/77
On Powerbook G4 PPC Fedora 10 with RV350, xorg-x11-drv-ati-6.9.0-62.fc10 also causes hard lockup on gdm login. Just came in via system update... :-( Thousands of messages in /var/log/gdm/:0.log: (EE) RADEON(0): Idle timed out, resetting engine... [mi] EQ overflowing. The server is probably stuck in an infinte loop. After downgrading to xorg-x11-drv-ati-6.9.0-54.fc10, everything works again.
The issue still happens with xorg-x11-drv-ati-6.10.0-2.fc10.i386 and 2.6.25-rc5.
uh, 2.6.29-rc5
Do you still have this issue with fedora 12 (you can test livecd from http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/) ?
Sorry, I'm no longer using this machine actively so this bug should probably be closed.
Ok closing this bug, reopen if you ever use the hw again and have the issue with newer fedora like fedora 12.