Bug 1866487

Summary:	Memory tracing won't work if there is a large memory hole
Product:	Red Hat Enterprise Linux 8	Reporter:	Kairui Song <kasong>
Component:	memstrack	Assignee:	Kairui Song <kasong>
Status:	CLOSED ERRATA	QA Contact:	Li Wang <liwan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	liwan, ruyang
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	memstrack-0.1.11-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:54:49 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1814488

Description Kairui Song 2020-08-05 17:31:05 UTC

Description of problem:
Memstrack will error out on start if machine have very large memory hole.

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


How reproducible:
100%

Steps to Reproduce:
The issue is mostly likely seen in kdump environment with high reservation used, as this will create a big hole in crash kernel's memory map.
 
1. Find a machine with large memory (eg. 1T memory)
2. Set crashkernel=512M,high
3. Add rd.memdebug=5 in kdump kernel params.
4. restart kdump and trigger panic

Actual results:
Memstrack failed

Expected results:
Memstrack works and prints memory usage info

Additional info:

Comment 6 errata-xmlrpc 2020-11-04 01:54:49 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 (memstrack bug fix and enhancement update), 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/RHEA-2020:4516