Bug 189524

Summary: System gives kernel: OUt of Memory errors
Product: Red Hat Enterprise Linux 4 Reporter: Mike Rhyner <michael.rhyner>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-20 20:23:46 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 Mike Rhyner 2006-04-20 18:37:20 UTC 
Description of problem:
System spews kernel: Out of memory errors and kills processes. The system never 
attempts to swap. Based on some other bug reports, there are conflicting 
answers to resolving this. One is use 2.6.16 kernel, which is not available for 
Enterprise version 4 (fully supported). 

Version-Release number of selected component (if applicable):
2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux

How reproducible:
when system runs for several days

Steps to Reproduce:
1. Run software development builds (via ClearCase)
2.
3.
  
Actual results:
Mar 30 09:38:51 il94llb01 kernel: Out of Memory: Killed process 4483 (sshd).
Mar 30 09:39:00 il94llb01 kernel: Out of Memory: Killed process 820 (cleartool).
Mar 30 09:39:06 il94llb01 kernel: Out of Memory: Killed process 818 (clearmake).
Mar 30 09:51:06 il94llb01 kernel: Out of Memory: Killed process 1294 (vim).
System eventually hangs

Expected results:
Processes should run clean and the system should not hang.

Additional info:
ClearCase version 
clearcase_p2003.06.00-29 (Mon Nov 21 22:31:55 EST 2005)
@(#) MVFS version 2003.06.10+ (Sat Oct  1 02:29:23 2005) VNODE built $Date: 
2005-10-01.09:38:44 (UTC) $
Comment 1 Jason Baron 2006-04-20 20:23:46 UTC 

*** This bug has been marked as a duplicate of 189523 ***