Crash on boot

[Jon Wilson]

After an unattended upgrade today my system would no longer boot. Presumably the kernel panic and stack trace info is attached. This is on an HP ProLiant MicroServer Gen8

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-104-generic 4.4.0-104.127
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jan 10 19:43 seq
 crw-rw---- 1 root audio 116, 33 Jan 10 19:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
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: Wed Jan 10 19:50:06 2018
HibernationDevice: RESUME=/dev/mapper/honk--vg-swap_1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HP ProLiant MicroServer Gen8
PciMultimedia:

ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/hostname--vg-root ro noquiet nomodeset radeon.modeset=0 systemd.recover_state=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-104-generic N/A
 linux-backports-modules-4.4.0-104-generic N/A
 linux-firmware 1.157.14
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrJ06:bd11/02/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP

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

This change was made by a bot.

[Jon Wilson (u-ubuntu-n)]

The kernel version in the report is the previous, working version which I booted into to file the report. The broken version is linux-image-4.4.0-108-generic

[Joseph Salisbury (jsalisbury)]

This may be a duplicate of bug 1741934, which was fixed in the 4.4.0-109 kernel. Can you upgrade to the 4.4.0-109 kernel and see if this bug still exists?

[Jon Wilson (u-ubuntu-n)]

It is indeed not happening after upgrading to 4.4.0-109. Many thanks for the lightning-quick response!