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.
Description of problem:
The atop does not show the 'PSIZE' values
Version-Release number of selected component (if applicable):
pcp-4.3.0-3.el8.x86_64
How reproducible:
Steps to Reproduce:
1. Run the pcp atop
2. Check the PSIZE column
Actual results:
it does not show the values under the PSIZE column. Looks like the PCP has not implemented the PSIZE matrices
Expected results:
It should show the values under the PSIZE column
Additional info:
The feature will be a great addition in solving the RHEL performance cases.
This is implemented upstream now through the following commits:
commit d8c5b2960b9b1e7b917483c90c1ac8571c4664e7
Author: Nathan Scott <nathans>
Date: Fri Mar 20 14:11:31 2020 +1100
pcp-atop: support PSIZE output from pcp-atop using proc.smaps.pss
Resolves Red Hat BZ #1814520
commit 57741c3e5e44db78538e8ac2bc06593c29a0b68c
Author: Nathan Scott <nathans>
Date: Fri Mar 20 13:31:19 2020 +1100
pmdaproc: correct parsing of lazyfree field in /proc/pid/smaps_rollup
Resolves a failure detected by test qa/1222.
commit 21cdcaa07a64cc7f6b8aa9ae7b3ecbe60f4d2a78
Author: Nathan Scott <nathans>
Date: Fri Mar 20 11:28:43 2020 +1100
pmdaproc: support proc.smaps.* metrics from /proc/pid/smaps_rollup
Resolves https://github.com/performancecopilot/pcp/issues/569
Comment 10Andreas Gerstmayr
2020-06-15 14:45:06 UTC
Moving to ON_QA again:
This future feature is delivered (the new metric proc.smaps.pss show correct values), but contains a bug: the PSIZE column doesn't show the data from the new metric.
This bug will be tracked in: https://bugzilla.redhat.com/show_bug.cgi?id=1847055
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 (pcp 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/RHBA-2020:4684