Description: I have a MSI K8D Dual Opteron Board and I am having problems getting DRI support to work for any Radeon PCI cards. I have tried both a 7000 and 7500. Both cause a rapidly looping error when X starts up with the "ForcePCIMode" option. (EE) RADEON(0): GetBuffer timed out, resetting engine... (EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP start -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020 (EE) RADEON(0): GetBuffer timed out, resetting engine... (EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP start -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020 (EE) RADEON(0): GetBuffer timed out, resetting engine... I understand some work may have been done on the DRI CVS with regards to the Radeon PCIGard but I was having problems compiling monday's snapshot on the Opteron. The machine is having some hardware work done at present so I can't get the exact packages but I am pretty sure they packages are stock. Some updates were run so it is possible that the system is running the newest RedHat kernel. Steps to Reproduce: 1. Setup X for Radeon 2. Modify XF86Config to "ForcePCIMode" 3. Startx Actual Results: The system becomes unresponsive and fills the XFree86.0.log repeatly with the following message. (EE) RADEON(0): GetBuffer timed out, resetting engine... (EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP start -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020 (EE) RADEON(0): GetBuffer timed out, resetting engine... (EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP start -1020 (EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020 (EE) RADEON(0): GetBuffer timed out, resetting engine... Expected Results: X starts up and glxinfo shows DRI enabled. Additional Information: Dual Opteron 240 MSI K8D Motherboard 3ware 7000-2 120GB Western Digital JB 64MB Radeon 7500 or 7000 VIA 3 Port Firewire Adaptor GinGin64 Beta 2x1GB PC2100 4x64 Reg ECC
*** This bug has been marked as a duplicate of 86157 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.