Bug 99015 - ps shows bogus CPU information
Summary: ps shows bogus CPU information
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-11 17:57 UTC by acount closed by user
Modified: 2007-04-18 16:55 UTC (History)
0 users

Clone Of:
Last Closed: 2004-06-10 09:18:50 UTC

Attachments (Terms of Use)

Description acount closed by user 2003-07-11 17:57:28 UTC
Description of problem:

xose      7533 44.9  0.1  1496  276 pts/0    R    23:02   1:43 ./lucifer 
xose      7538 34.4  0.1  1492  276 pts/0    R    23:03   0:59 ./lucifer 
xose      7544 26.2  0.1  1504  380 pts/0    R    23:04   0:30 ./lucifer 
xose      7559 25.1  0.1  1488  276 pts/0    R    23:05   0:15 ./lucifer 

CPU is more than 100% -> impossible

but top, mpstat, vmstat are ok

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


How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Alexander Larsson 2003-09-25 08:58:53 UTC
This is probably not a procps bug, but just the usual poor process accounting
that Linux does. However, that should show up in top too. When you say you don't
see it in top, do you mean the total cpu usage or in the actual process listings?

Comment 2 acount closed by user 2003-09-25 21:42:34 UTC
ps shows impossible CPU values. But with top, mpstat or vmstat I get correct CPU

This is a very clear ps bug

Comment 3 acount closed by user 2003-09-25 23:46:23 UTC
I forgot it. top shows _correct values_ in the total cpu usage _and_ in the
actual process listings.

Comment 4 Daniel Walsh 2004-03-29 02:27:42 UTC
Is this fixed by version 3.1.15 or later versions?

Comment 5 acount closed by user 2004-04-02 21:40:09 UTC
I will see it....

Comment 6 Daniel Walsh 2004-05-28 17:50:36 UTC
Upstream procps says that this is a kernel problem.

Comment 7 acount closed by user 2004-06-10 09:18:50 UTC
ok. I'm going to close it, now RHL is dead.


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