Yakkety Server cannot handle more than 256 cores

Bug #1656033 reported by Tymoteusz Kielan
This bug report is a duplicate of:  Bug #1579205: CONFIG_NR_CPUS=256 is too low. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Generic Linux kernel flavor is official Ubuntu Server Linux kernel flavor.
It is supposed to be run on both workstations and servers.

Generic kernel configuration supports max 256 CPUs:

    root@ubuntu02:~# grep CONFIG_NR_CPUS /boot/config-$(uname -r)
    CONFIG_NR_CPUS=256

While running on Intel KNL with Hyper-Threading enabled it cannot accommodate cores over 256.

Probably server flavor should support 512 cores, like it is in RedHat.

Logs attached.

Tags: 16.10
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1656033

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Tymoteusz Kielan (tkielan) wrote :

apport-collect 1656033
ERROR: connecting to Launchpad failed

I'm not feeling comfortable running scripts in corporate network, collecting unknown data.

I think all the details are already here.
If not, please specify what logs you are missing.

I have also given you the root cause:

Generic kernel configuration has CONFIG_NR_CPUS=256

The question is if Ubuntu is willing to change the defaults like RedHat did.

Revision history for this message
Tymoteusz Kielan (tkielan) wrote :

This somehow haven't attached 1st time.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.