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.
DescriptionHelio Chissini de Castro
2015-08-17 18:11:30 UTC
Created attachment 1064025[details]
Patch for RHEL 6 Gnome
glibtop not provides the number of cpus on the machine directly, relying on a list with the current load of each core.
Original code assume that a 0 load core is the end of cpu list, which is invalid in cases of machines with high number of cores, that happens to some cores stay idle with 0 load.
Since this can happens in any core number, if a machine has 192 cores, but the core number 5 has 0 load, then 4 cores will be wrongly reported.
Using standard sysconf api solves the issue in a simple way.
Comment 1Helio Chissini de Castro
2015-08-17 18:12:40 UTC
While testing a multi-core machine with gnome-system-monitor-2.28.0-13.el6, I was able to see the correct amount of cores listed, as well as the idle cores at 0.0%.
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://rhn.redhat.com/errata/RHBA-2017-0578.html
Created attachment 1064025 [details] Patch for RHEL 6 Gnome glibtop not provides the number of cpus on the machine directly, relying on a list with the current load of each core. Original code assume that a 0 load core is the end of cpu list, which is invalid in cases of machines with high number of cores, that happens to some cores stay idle with 0 load. Since this can happens in any core number, if a machine has 192 cores, but the core number 5 has 0 load, then 4 cores will be wrongly reported. Using standard sysconf api solves the issue in a simple way.