Created attachment 331938 [details] lspci -vvv Description of problem: Sometime between kernel-PAE-2.6.27.4-68.fc10.i686 and kernel-PAE-2.6.27.12-170.2.5.fc10.i686 DRI has caused my RV350 to hardlock any time any accelerated 3D graphics are displayed with KMS enabled Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.10.0-2.fc10.i386 kernel-PAE-2.6.27.12-170.2.5.fc10.i686 How reproducible: Almost always with kernel-PAE-2.6.27.12-170.2.5.fc10.i686, never with kernel-PAE-2.6.27.4-68.fc10.i686 Steps to Reproduce: 1. Boot kernel-PAE-2.6.27.12-170.2.5.fc10.i686 2. Run a DRI application, glxgears isn't always enough to trigger this, supertuxkart will 100% of the time Actual results: Screen goes black "Input out of range" and system hardlocks Expected results: 3D graphics Additional info: I have attached the output of lspci -vvv; an Xorg.0.log and the output of dmesg. FWIW, this also occurs with the non-PAE kernels.
Created attachment 331939 [details] dmesg
Created attachment 331940 [details] Xorg.0.log
Can you download some kernels from koji and test them to try and pinpoint when this started? Or just test whatever kernels are currently installed?
Ok, my results: 2.6.27.4-68.fc10.i686.PAE - Good 2.6.27.5-117.fc10.i686.PAE - "Input signal out of range" 2.6.27.9-159.fc10.i686.PAE - System Freezes, but no out of range 2.6.27.12-170.2.5.fc10.i686.PAE - "Input signal out of range" 2.6.27.15-170.2.24.fc10.i686.PAE - "Input signal out of range" It seems that something introduced in 2.6.27.5 has broken DRI.
Just thought I'd report that this issue seems to have gone away now (kernel-PAE-2.6.27.19-170.2.35.fc10.i686 or possibly earlier).