Ubuntu
linux package

CONFIG_NUMA is missing from the 4.8 kernels on s390x

Bug #1661620 reported by Dimitri John Ledkov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Triaged
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Canonical Kernel Team
Ubuntu ubuntu-17.02
Xenial
Invalid
Undecided
Unassigned
Yakkety
Triaged
High
Canonical Kernel Team
linux-hwe-edge (Ubuntu)
Invalid
Undecided
Canonical Kernel Team
Xenial
Triaged
High
Canonical Kernel Team
Yakkety
Invalid
Undecided
Unassigned

Bug Description

CONFIG_NUMA is not set in the 4.8 kernels (16.10 & linux-edge) when it should have been, on s390x.

It is set in 4.4 (xenial) and 4.9 (zesty).

This is regression of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690

$ grep CONFIG_NUMA -r linux-4.*/debian.master/config/s390x/config.common.s390x
linux-4.4.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA=y
linux-4.4.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
linux-4.4.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_EMU=y
linux-4.8.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA is not set
linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA=y
linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_BALANCING=y
linux-4.9.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_EMU=y

This is a release regression and linux-edge regression.

Dimitri John Ledkov (xnox)
Changed in linux-hwe-edge (Ubuntu):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Changed in linux (Ubuntu Xenial):
status: New → Invalid
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Yakkety):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Changed in linux-hwe-edge (Ubuntu):
status: New → Invalid
Changed in linux-hwe-edge (Ubuntu Yakkety):
status: New → Invalid
Changed in linux-hwe-edge (Ubuntu Xenial):
status: New → Triaged
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
importance: Undecided → High
Dimitri John Ledkov (xnox)
tags: added: regression-release regression-update
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-02-06 09:23 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 09:24 EDT-------
*** Bug 151232 has been marked as a duplicate of this bug. ***

tags: added: architecture-s39064 bugnameltc-151262 severity-high targetmilestone-inin1610
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2017-03-15 11:17 EDT-------
IBM Bugzilla -> closed, already fixed with LP1557690

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.