Bug 1040449

Summary: Enhancement : Auto trigger kdump after all CPU usage reached 95% or specified trigger point.
Product: Red Hat Enterprise Linux 6 Reporter: Venkata Rama Krishna Boddu <venkat.boddu>
Component: kexec-toolsAssignee: Minfei Huang <mhuang>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: ruyang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-01 10:19:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Venkata Rama Krishna Boddu 2013-12-11 12:53:07 UTC
Description of problem: It a Enhancement not Bug.
At present, there is not much we can do, If all CPU resources are consumed upto 100% and if system went into hang state because of a some not so good programs. In this case we are left with no option but to hard reset the entire Linux box.

Now, after reboot what we left with is just /var/log/messages for debugging if my not so good program uses syslog for logging some debug messages about what it is doing, otherwise we don't have any proof of evidences.

Version-Release number of selected component (if applicable):
Name        : kexec-tools
Arch        : x86_64
Version     : 2.0.0
Release     : 258.el6
Size        : 771 k
Repo        : installed
From repo   : Red Hat Enterprise Linux
Summary     : The kexec/kdump userspace component.


How reproducible:

Steps to Reproduce:
1. When system is idle and not doing any thing, just execute the below command.
2. while [ 1 ]; do dd if=/dev/zero of=/dev/null & done

Actual results:
Linux kernel just hangs and doesn't response to SSH or console commands.


Expected results:
Linux kernel should terminate the excessive processes it can't handle beyond a certain limit or kdump should be trigger internally.

Additional info:
This is especially useful, when firefox consume lots of amount of memory because of heavy number of opened pages.

Comment 2 Minfei Huang 2014-12-01 10:19:22 UTC
This is not a bug.