Bug 1376661

Summary: RFE: Enhance memory info debugging for kdump kernel
Product: Red Hat Enterprise Linux 7 Reporter: Xunlei Pang <xlpang>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: high    
Version: 7.4CC: dracut-maint-list, dyoung, jstodola, kdump-team-bugs, lnykryn, mhruscak, ruyang, salmy, xlpang
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: dracut-033-492 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:06:54 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:
Bug Depends On:    
Bug Blocks: 1380361, 1394638, 1404314    

Description Xunlei Pang 2016-09-16 06:28:04 UTC 
Description of problem:
The current method for kdump is using dracut "rd.memdebug=[0-3]", it is not enough. For example, when we want to find out which kernel module consumes a large amount of memory, "rd.memdebug" won't help too much.

A better way is needed to achieve this requirement, this is very useful for kdump OOM debugging.
Comment 2 Dave Young 2016-11-08 03:06:07 UTC 
Xunlei posted patches to dracut upstream, kdump code does not need any changes.
Comment 3 Lukáš Nykrýn 2016-11-22 11:38:47 UTC 
Can you please reference the upstream pull requests here?
Comment 4 Xunlei Pang 2016-11-29 07:16:34 UTC 
(In reply to Lukáš Nykrýn from comment #3)
> Can you please reference the upstream pull requests here?

Hi Lukas,

Sorry for the late reply, I just requested the PR here:
https://github.com/dracutdevs/dracut/pull/183

but seems there are some failures, which are beyond my head, could you please help have a check? Many thanks!

Xunlei
Comment 11 Marek Hruscak 2017-05-02 11:45:06 UTC 
Dracut now registers higher level than 0-3 (e.g. rd.memdebug=4), which produce more verbose output.
Comment 12 errata-xmlrpc 2017-08-01 21:06:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2076