Bug 353801 - error INVALID CPU TIME DATA
Summary: error INVALID CPU TIME DATA
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: procps
Version: 3.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Novotny
QA Contact: Brian Brock
URL:
Whiteboard:
: 353791 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-26 09:23 UTC by linda
Modified: 2018-10-19 20:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 07:55:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
error screen capture (849.50 KB, application/msword)
2007-10-26 09:23 UTC, linda
no flags Details

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


Note You need to log in before you can comment on or make changes to this bug.