Bug 353801

Summary: error INVALID CPU TIME DATA
Product: Red Hat Enterprise Linux 3 Reporter: linda <i_ayin79>
Component: procpsAssignee: Daniel Novotny <dnovotny>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: low    
Version: 3.0CC: albert
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 07:55:20 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
error screen capture none

Description linda 2007-10-26 09:23:59 UTC 
Description of problem:
when i running top command, while the server running sometimes INVALID CPU 
TIME DATA happen. please see file attach. this server is running as a database 
server. database engine install is mySQL 5.0.21


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

LSB Version:    1.3
Description:    Red Hat Enterprise Linux AS release 3 (Taroon)
Release:        3


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
- do this INVALID CPU TIME DATA effect to the server performance and data
- what is the cause of this error can happen and how to solve it

Additional info:
Comment 1 linda 2007-10-26 09:23:59 UTC 
Created attachment 238691 [details]
error screen capture
Comment 2 Adam Tkac 2007-10-29 10:48:09 UTC 
*** Bug 353791 has been marked as a duplicate of this bug. ***
Comment 3 Adam Tkac 2007-10-29 10:54:33 UTC 
This is not telnet problem. Reassigning to procps component
Comment 4 Tomas Smetana 2007-10-29 11:17:47 UTC 
This happens when top command computes the CPU time as 0 (zero).  This has no
effect on the system performance, it's just a bug in the old top command.  Since
this is not critical or security issue, it probably won't be fixed.
Comment 6 Daniel Novotny 2010-03-30 07:55:20 UTC 
No further updates are planned for RHEL3. As the bug is not present in RHEL4
and higher, we suggest to upgrade to later RHEL release. Closing WONTFIX