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:
pcp atop shows "?K" in the PSIZE column

Version-Release number of selected component (if applicable):
pcp-5.1.1-2.el8 

How reproducible:
always

Steps to Reproduce:
# pcp atop -m

Actual results:
pcp atop shows "?K" in the PSIZE column

Expected results:
actual data should be in the PSIZE column

Additional info:
the new proc.smaps.pss metric works as expected

This is behaving as designed - because the smaps metrics are deemed quite expensive to sample (by atop devs - indeed they are, see below) they've added a -R flag which must be used in order to enable this column.

$ time  pminfo -f proc.psinfo.pid
[...]
real	0m0.028s

$ time  pminfo -f proc.smaps.pss
[...]
real	0m0.201s


I've confirmed that testing with this option enabled, all is well and the column is displayed with values.

Thanks Nathan and I am sorry for the false alarm. I missed this design feature.

It works as expected with the '-R' flag.
Verified on pcp-5.1.1-2.el8 build.

Heh, I also didn't realize this - sorry!

I was about to suggest to hide the PSIZE column in this case, but the original atop tool also shows the PSIZE column with "0K" it the -R flag is not enabled - so it's probably best to leave it as it is now.

No problem guys - thanks for testing it out.