Maximum number of CPUs setting is too low #1771

Closed
jakub-d opened this Issue Jan 23, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@jakub-d

jakub-d commented Jan 23, 2017

Issue Report

I am trying to use CoreOS on a platform with Intel 2nd Generation Xeon Phi processor.
The system boots properly, but it limits number of CPUs to 128.
In the boot log I get:

Jan 21 20:44:07 localhost kernel: APIC: NR_CPUS/possible_cpus limit of 128 reached.  Processor 128/0x2 ignored.
Jan 21 20:44:07 localhost kernel: APIC: NR_CPUS/possible_cpus limit of 128 reached.  Processor 129/0x6 ignored.
Jan 21 20:44:07 localhost kernel: APIC: NR_CPUS/possible_cpus limit of 128 reached.  Processor 130/0xa ignored.

When I run the nproc command, I get 128.
The number should be 255 for this processor.

Please increase the CONFIG_NR_CPUS Kernel setting to at least 512 (RedHat uses 8192).

Bug

CoreOS Version

1284.2.0

Environment

What hardware/cloud provider/hypervisor is being used to run CoreOS?
Bare metal.

Expected Behavior

nproc returns 128

Actual Behavior

nproc should return 255

Reproduction Steps

Install CoreOS on the server with the Intel Xeon Phi 2nd Generation processor.

@jakub-d jakub-d referenced this issue in coreos/coreos-overlay Jan 25, 2017

Closed

Increase CONFIG_NR_CPUS to support Intel Xeon Phi #2395

@crawford crawford added this to the Container Linux Alpha 1313.0.0 milestone Jan 31, 2017

@crawford crawford referenced this issue in coreos/coreos-overlay Feb 2, 2017

Merged

sys-kernel/coreos-kernel: increase CONFIG_NR_CPUS #2410

@crawford

This comment has been minimized.

Show comment
Hide comment
Member

crawford commented Feb 2, 2017

@crawford crawford closed this Feb 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment