Ubuntu 16.04.4 HWE kernel lockup: Upstream commit missing

[Per Allansson]

I experience random lockups when disabling CPUs, with symptoms very much as described here:

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

and when double-checking the source code for 4.13.0-36.40~16.04.1 I can see that upstream commit d47924417319e3b6a728c0b690f183e75bc2a702 is indeed missing.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Mar 5 19:30 seq
 crw-rw---- 1 root audio 116, 33 Mar 5 19:30 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: FUJITSU PRIMERGY RX2530 M4
Package: linux (not installed)
PciMultimedia:

ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/image1/kernel root=/dev/czvg/image1 ro console=tty0 console=ttyS0,115200 earlyprintk=ttyS0 rootdelay=300 net.ifnames=0 biosdevname=0 nomodeset scsi_mod.scan=sync cz-boot-fs=/dev/sda1 cz-state-fs=/dev/czvg/state1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic N/A
 linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 10/05/2017
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.12 R1.11.0 for D3383-A1x
dmi.board.name: D3383-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3383-A12 WGS03 GS04
dmi.chassis.asset.tag: System Asset Tag
dmi.chassis.type: 23
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: RX2530M4R1
dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.11.0forD3383-A1x:bd10/05/2017:svnFUJITSU:pnPRIMERGYRX2530M4:pvrGS01:rvnFUJITSU:rnD3383-A1:rvrS26361-D3383-A12WGS03GS04:cvnFUJITSU:ct23:cvrRX2530M4R1:
dmi.product.family: SERVER
dmi.product.name: PRIMERGY RX2530 M4
dmi.product.version: GS01
dmi.sys.vendor: FUJITSU

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1753583

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.

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Per Allansson (per-allansson)]

apport information

[Joseph Salisbury (jsalisbury)]

I built a test kernel with commit d47924417319. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753583

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

[Per Allansson (per-allansson)]

I tested it yesterday with my own build - ie applied d47924417319 on the latest hwe kernel - and it worked[1] for me. But I will test your build too.

[1] ie I ended up getting another kernel issue - which is that the megaraid driver can't handle CPUs being disabled - which is discussed in detail here (and not solved upstream afaict): https://lkml.org/lkml/2017/8/8/884

[Per Allansson (per-allansson)]

I can confirm that your build works (as described in my previous comment).

[Joseph Salisbury (jsalisbury)]

Commit d47924417319 has been requested in Artful in bug 1733662, but it has not yet been applied:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089403.html

I'll mark this bug as a duplicate since you confirmed the same commit fixes this bug.