Bug 154406 - System monitor doesn't show 2nd core of a dual core processor
System monitor doesn't show 2nd core of a dual core processor
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gnome-system-monitor (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Søren Sandmann Pedersen
Depends On:
  Show dependency treegraph
Reported: 2005-04-11 11:15 EDT by Gregory Feiner
Modified: 2014-06-18 05:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:04:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gregory Feiner 2005-04-11 11:15:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
RHEL 4 x86 and X86_64 U1 Partner Beta
Server BL45p (4way, Dual Core AMD Opteron 875)

Problem:  When the server is loaded with 4 dual core processors, System Monitor only shows 4 processors.  It should show 8.  /proc/cpuinfo shows all 8 processors.

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

How reproducible:

Steps to Reproduce:
1. Install the OS on a AMD Dual core server (default settings are fine)
2. Run system monitor and look that the number of processors shown.

Actual Results:  Incorrect number of processors shown

Expected Results:  Should have shown 8 processors. System monitor is not setting the 2nd core of each processor.

Additional info:
Comment 1 Jiri Pallich 2012-06-20 12:04:30 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.