Bug 635062

Summary: Xorg high CPU consumption in rawhide
Product: [Fedora] Fedora Reporter: Matthew Miller <mattdm>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 18:44:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Miller 2010-09-17 17:39:19 UTC 
Description of problem:

With latest rawhide, Xorg takes between 50% and 100% of one CPU constantly.

This is with both systemd and upstart, 


Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg-1.9.0-10.fc15.x86_64
xorg-x11-drv-ati-6.13.1-1.20100705git37b348059.fc14.x86_64

How reproducible:

Always. 

Steps to Reproduce:
1. Boot computer.
2. Look at Xorg CPU usage
  
Actual results:

High CPU.


Expected results:

Next-to-nothing, unless something is really going on.


Additional info:

Happens on both ATI Mobility Radeon HD 2600 XT (ChipID = 0x9583) and ATI Radeon 
HD 2400 Pro (ChipID = 0x94c3).

It's possible this has been happening for a while and I just didn't notice -- both systems are multi-core, so one jammed CPU doesn't necessarily kill interactive performance.
Comment 1 Matthew Miller 2010-09-25 22:29:02 UTC 
Still happening:

xorg-x11-server-Xorg-1.9.0-10.fc15.x86_64
xorg-x11-drv-ati-6.13.1-0.4.20100705git37b348059.fc15.x86_64
kernel-2.6.36-0.26.rc5.git4.fc15.x86_64
Comment 2 Matthew Miller 2010-11-10 18:43:30 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=635062
Comment 3 Matthew Miller 2010-11-10 18:44:46 UTC 

*** This bug has been marked as a duplicate of bug 650934 ***