Ubuntu
kernel-package package

FAKE_NUMA setting changed within kernel config for Ubuntu 16.10 and 16.04.2

Bug #1661610 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
New
Undecided
Unassigned
kernel-package (Ubuntu)
New
Undecided
Skipper Bug Screeners

Bug Description

Original Setting for Ubuntu 16.04 :
cat config-4.4.0-59-generic | grep NUMA
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING=y
# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
CONFIG_NUMA=y
# Select NUMA modes
CONFIG_NUMA_EMU=y

Than changed with Ubuntu 16.10 to
$ grep NUMA config-4.8.0-30-generic
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
# CONFIG_NUMA is not set

Changed again with Ubuntu 17.04 back to original
grep NUMA config-4.9.0-15-generic
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING=y
# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
CONFIG_NUMA=y
# Select NUMA modes
CONFIG_NUMA_EMU=y

The setting for 16.10 and also for 16.04.2 should be changed to the original once

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-151232 severity-high targetmilestone-inin1610
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → kernel-package (Ubuntu)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Bug correctly opened against affected packages is at:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1661620

please reverse mirror that for better tracking. Kernel team is already in progress fixing https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1661620.

Regards,

Dimitri.

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-02-03 08:29 EDT-------

Original Setting for Ubuntu 16.04 :
cat config-4.4.0-59-generic | grep NUMA
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING=y
# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
CONFIG_NUMA=y
# Select NUMA modes
CONFIG_NUMA_EMU=y

Than changed with Ubuntu 16.10 to
$ grep NUMA config-4.8.0-30-generic
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
# CONFIG_NUMA is not set

Changed again with Ubuntu 17.04 back to original
grep NUMA config-4.9.0-15-generic
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING=y
# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
CONFIG_NUMA=y
# Select NUMA modes
CONFIG_NUMA_EMU=y

The setting for 16.10 and also for 16.04.2 should be changed to the original once

------- Comment From <email address hidden> 2017-02-06 07:41 EDT-------
Reverse mirror initiated for 1661620

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2017-02-06 09:24 EDT-------
*** This bug has been marked as a duplicate of bug 151262 ***

------- Comment From <email address hidden> 2017-02-06 09:25 EDT-------
IBM Bugzilla -> closed, as duplicate

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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