Bug 111216 - /usr/bin/top fails to show idletime etc...
Summary: /usr/bin/top fails to show idletime etc...
Keywords:
Status: CLOSED DUPLICATE of bug 109484
Alias: None
Product: Fedora
Classification: Fedora
Component: procps
Version: 1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-30 11:23 UTC by Jens Andersen
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jens Andersen 2003-11-30 11:23:29 UTC 
Description of problem: 
 
Running /usr/bin/top on a newly installes and updated Fedora Core 1 
it fails to show proper summary values. The following line from the 
top header: 
 
CPU states:  cpu    user    nice  system    irq  softirq  iowait    
idle 
           total    0.0%    0.0%    0.0%  33.3%    33.4%   33.2%    
0.0% 
 
never shows user/nice/idle values. However, the irq/softirq/iowait 
values switches between 0.0 and "1/3", as above, every time the 
display is updated. 
 
Version-Release number of selected component (if applicable): 
 
Fedora Core I, /usr/bin/top from the procps-2.0.17-1 RPM. 
 
How reproducible: 
 
Happens every time... 
 
Steps to Reproduce: 
 
1. Simply run 'top' 
2. 
3. 
   
Actual results: 
 
Valid, thrustworth time values 
 
Expected results: 
 
Clearly bogus values 
 
Additional info:
Comment 1 Jens Andersen 2003-11-30 11:27:29 UTC 
Forgot to mention my platform/configuration. I'm running Fedora on 
an Intel P3/650Mhz ASUS laptop, 192Mb of memory. Nothing really 
special about it - definitely not to make top fail like this...:-)
Comment 2 Jens Andersen 2003-11-30 11:36:09 UTC 

*** This bug has been marked as a duplicate of 109484 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:00:14 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.