Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLadislav Kolacek
2015-02-10 16:11:48 UTC
Created attachment 990139[details]
screenshots.tar.gz
Description of problem:
Version-Release number of selected component (if applicable):
kernel-3.10.0-229.el7
gnome-system-monitor-3.8.2.1-6.el7
libgtop2-2.28.4-7.el7
How reproducible:
always
Steps to Reproduce:
1. Open gnome-system-monitor
2. Go to Resources tab
3. Watch the Memory and Swap History
4. Open terminal and run: free -mh
Actual results: Utilities display different value of used memory.
e.g. in ppc64: 999MB <> 1.6GiB (1.717 GB)
Expected results: Swap and RAM usage should more or less correspond in both utilities.
Additional info: Screenshots are packaged in attachment.
This discrepancy is not unexpected, given how libgtop determines the amount of free memory. It does so by parsing /proc/meminfo, followed by subtracting Buffers, Cached and MemFree from MemTotal.
The free utility works differently, because it includes the Slab field in its used memory calculation (or uses MemAvailable).
There is an upstream bug report (with a patch) to change the reporting in libgtop to use the MemAvailable field present in kernel 3.14 and above, which would make the libgtop output similar to the free 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/RHEA-2017:2305
Created attachment 990139 [details] screenshots.tar.gz Description of problem: Version-Release number of selected component (if applicable): kernel-3.10.0-229.el7 gnome-system-monitor-3.8.2.1-6.el7 libgtop2-2.28.4-7.el7 How reproducible: always Steps to Reproduce: 1. Open gnome-system-monitor 2. Go to Resources tab 3. Watch the Memory and Swap History 4. Open terminal and run: free -mh Actual results: Utilities display different value of used memory. e.g. in ppc64: 999MB <> 1.6GiB (1.717 GB) Expected results: Swap and RAM usage should more or less correspond in both utilities. Additional info: Screenshots are packaged in attachment.