Bug 104724

Summary: top occasionally consumes 1 CPU
Product: Red Hat Enterprise Linux 2.1 Reporter: aaron bos <aaron.bos>
Component: procpsAssignee: Tomas Smetana <tsmetana>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: krader
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:24:05 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:

Description aaron bos 2003-09-19 20:04:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)

Description of problem:
At random intervals, maybe once a month across 30 servers, I'm alerted to high 
CPU utilization on a server, and find a "top" command using 100% of a CPU.  
Typically the command has been running for several hours, and is running as a 
non-root user.


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

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
1.  Can't reproduce.  Happens randomly, infrequently.
2.
3.
    

Additional info:

Servers are Compaq DL360-G2s w/ 2 CPUs, 4 GB RAM.  Running 2.4.9-e.9smp.

Comment 1 Daniel Walsh 2004-02-11 13:43:16 UTC
Can you reproduce this using 3.1.15 version?

Dan

Comment 2 Albert Cahalan 2004-07-20 17:33:19 UTC
It appears that sometimes the kernel will fail to sent SIGHUP
to the foreground process group when the session leader dies.
I've seen it after doing "su" in an xterm and then killing
the xterm. This is one way to cause the problem you're seeing.


Comment 3 Kurtis D. Rader 2005-02-21 22:20:33 UTC
This also happens with procps-2.0.17-10 from RHEL AS 3 U3.

The primary problem is that top(1) doesn't terminate when a read of stding
returns an EOF indication. Specifically, after a "read(0, buf, 1)" returns
zero top(1) continues running. The secondary problem is that certain login
shells (such as the real ksh, not pdksh) don't propagate SIGHUP correctly.


Comment 4 RHEL Program Management 2007-10-19 19:24:05 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.