Red Hat Bugzilla – Bug 203341
X server hanging with latest ATI driver
Last modified: 2018-04-11 06:30:22 EDT
Description of problem:
With the latest ATI driver from rawhide, the problem of X taking up nearly all
the CPU time has returned.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot laptop in runlevel 5
Login is unusable because the X server is taking up nearly all CPU time. If I
move to a virtual console, it is just about usable - enough to get bug report
The graphical login works normally.
This is the same system in
Created attachment 134557 [details]
X server log file
I can confirm that this is actually worse with the latest updates as of today
(22/8/2006) in that I can't even login via GDM as the CPU is so busy.
Currently running xorg-x11-drv-ati-6.6.1-9 and xorg-x11-server-Xorg-1.1.1-26
This bug is still present with kernel 2.6.17-1.2630.fc6 and
xorg-x11-drv-ati-6.6.2-1.fc6 - at the moment this system can only run X with the
VESA driver in 1024x768.
Created attachment 135937 [details]
Syslog entries after activating DRI debug
The problem seems to be there when both GL and DRI are enabled together. In my
case if I disable DRI I can login. But if I boot the system using Xen kernel the
CPU utilization is high again.
I am using an ATI AIW 8500 DV RADEON card
I have another system with a duplicate configuration except the graphic card is
an Intel 810, and everything seems to be working OK with no High CPU utilization.
This problem is still present in FC6 final.
Just checked with 6.6.3-1.fc6 and the freezes still happen.
Check the new fglrx driver at
This still seems to be happening with the driver in Fedora 7.
Actually, it worked for a while with the latest updated driver, but has crashed
as the old one used to, with the screen "burning up".
Reporter, just to be sure (and with regards to misleading comment 8) -- are we
talking about open source ati driver or fglrx?
The open source ati one, yes.
Option "RenderAccel" "false"
in the driver section of xorg.conf solve this?
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Haven't used that laptop in a while but I'll try it as soon as I can.
OK, that month timeframe is still here.
I ended up upgrading to F7 and it seems to be behaving.
Closing per reporter's request in comment 17.