Bug 127702

Summary: procps: top Reports CPU Utilization above 100%
Product: [Fedora] Fedora Reporter: Matt Siemens <msiemens>
Component: procpsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-07-20 16:46:51 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:
Attachments:
Description Flags
Top showing the problem. none

Description Matt Siemens 2004-07-12 18:44:56 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1

Description of problem:
When using top to monitor a system under heavy load (in my case, a
system undergoing stress testing), top will occasionally display an
idle value of 3624114749255314.0% or similar.  See the enclosed
screenshot for details.

SYSTEM DETAILS:
2 x 2.4 GHz Xeon CPUs with Hyperthreading enabled
1 GB RAM
Kernel 2.4.22-1.2194.nptl (SMP)

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

How reproducible:
Always

Steps to Reproduce:
Force your system to use all CPU time, and monitor the system with
top.  Within the first minute you should see the odd reading.
Comment 1 Matt Siemens 2004-07-12 18:46:29 UTC 
Created attachment 101821 [details]
Top showing the problem.
Comment 2 Daniel Walsh 2004-07-20 15:24:09 UTC 
Does procps-3.2.2-1 still show this behaviour?
Comment 3 Matt Siemens 2004-07-20 15:45:42 UTC 
Where can I find a copy of procps-3.2.2-1 for FC1?
Comment 4 Daniel Walsh 2004-07-20 16:05:11 UTC 
http://download.fedora.redhat.com/pub/fedora/linux/core/development/
Comment 5 Matt Siemens 2004-07-20 16:45:34 UTC 
I compiled and installed procps-3.2.2-1 for FC1, and ran the same
stress tests as before.  I wasn't able to reproduce the problem found
in the older version of top. It looks like this newer version of
procps fixes the bug in top.