Bug 177445

Summary: Please consider upping NR_CPUS to 16 for x86_64
Product: Red Hat Enterprise Linux 4 Reporter: Martin Knoblauch <knobi>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0132 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-07 21:10:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 168429    

Description Martin Knoblauch 2006-01-10 19:23:23 UTC 
Description of problem:

 On a 4 CPU, dual-core, HT-enabled EM64T system only 8 "CPUs" are recognized.
Please consider building the x86_64 kernels with NR_CPUS set to 16 or more.

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

2.6.9.EÃ-22

How reproducible:

Always

Steps to Reproduce:
1. Boot system
2.
3.
  
Actual results:

 There should be 16 CPUs visible

Expected results:

 Only 8 CPUs are visible, dmesg shows that the limit of NR_CPUS=8 is exceeded.

Additional info:
Comment 1 Jason Baron 2006-01-11 12:59:58 UTC 
hi Martin,

We're adding a 'largesmp' kernel in U3 that will support 64 cpus for x86_64. You
can test that kernel out via the beta channel. 

thanks.

*** This bug has been marked as a duplicate of 163641 ***
Comment 2 Martin Knoblauch 2006-01-11 15:23:40 UTC 
Jason,

 thanks for the update. For some reason I did not find 163641. Apparently I did
not look hard enough :-) What will be the limit in the U3 kernel?

Martin
Comment 3 Jason Baron 2006-01-18 16:22:26 UTC 
64 cpus
Comment 5 Red Hat Bugzilla 2006-03-07 21:10:37 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0132.html