Hide Forgot
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.
Xunlei posted patches to dracut upstream, kdump code does not need any changes.
Can you please reference the upstream pull requests here?
(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
Dracut now registers higher level than 0-3 (e.g. rd.memdebug=4), which produce more verbose output.
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