kernel crash/freeze during shutdown

[Hadmut Danisch]

Hi,

I have a brandnew HP Microserver Gen10 with a freshly installed and almoste bare Ubuntu 16.04 and its 4.4.0-98-generic kernel, two additional disks, and zfs.

Runs stable, but during shutdown it happened many times that the kernel crashed and the machine completely froze (or hung in shutdown). Since the machine was dead then, the only option to get the details was a "screenshot" of the screen (as attached).

I've running a similar configuration on other machines, including older Microserver models, but never saw that on any other machine.

Reported upstream as

https://bugzilla.kernel.org/show_bug.cgi?id=197853

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Nov 11 22:54 seq
 crw-rw---- 1 root audio 116, 33 Nov 11 22:54 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Sat Nov 11 23:16:03 2017
HibernationDevice: RESUME=UUID=05c2d8e4-5d35-415a-bc30-628c0d1e92e3
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HPE ProLiant MicroServer Gen10
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LC_MESSAGES=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=9550da16-2d0f-44fa-acc6-886dca3f9eb7 ro nomodeset nosplash quiet
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-98-generic N/A
 linux-backports-modules-4.4.0-98-generic N/A
 linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ProLiant MicroServer Gen10
dmi.board.vendor: HPE
dmi.board.version: 871721-001
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: HPE
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd05/25/2017:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring:
dmi.product.name: ProLiant MicroServer Gen10
dmi.product.version: Rev B
dmi.sys.vendor: HPE

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

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

[Hadmut Danisch (hadmut)]

I've made some tests meanwhile with the latest 4.14 ubuntu kernel package, but could not reproduce the bug with the tests under that kernel so far, but that does not really and realiably mean anything, because

- the kernel freeze occures occasionally only, therefore difficult to prove the absence by a few tests.

- the machine needs zfs to use it's additional disks and I don't get the zfs kernel modules with that 4.14 package, so it's unclear whether the bug is somehow caused by zfs modules. Furthermore, I cannot test the machine intensively (and under similar usage) without zfs.

To be comparable, the 4.14 kernel package would need to be compiled in the very same way as the 4.4 kernel that comes with 16.04.