Ubuntu 14.04 LTS Server Kernel Crash

[Sami Pietila]

A Dell R720 server with Ubuntu 14.04 LTS crashed with following (see attachment) kernel messages scrolling on the terminal screen.

The server is a production server. It is not possible to install an upstream kernel.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 marra 17 09:54 seq
 crw-rw---- 1 root audio 116, 33 marra 17 09:54 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.5
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:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Nov 17 10:03:33 2014
InstallationDate: Installed on 2014-02-26 (263 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140219)
MachineType: Dell Inc. PowerEdge R720
PciMultimedia:

ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=c03eb237-955a-4dee-bba1-deded53df372 ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.2.2
dmi.board.name: 0DCWD1
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.2.2:bd01/16/2014:svnDellInc.:pnPowerEdgeR720:pvr:rvnDellInc.:rn0DCWD1:rvrA01:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R720
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Sami Pietila (sampie)]

The server has always been 14.04 LTS, so no big kernel upgrades. There was however an installation of a new VM machine ongoing. Perhaps something in that caused the host server to crash.

[Joseph Salisbury (jsalisbury)]

Do you have a way to reproduce the crash, or was it a one time event?

[Sami Pietila (sampie)]

The crash has occurred only once. Unfortunately, I don't know how to reproduce the problem. The server had been running with high computational load for several days. Perhaps that was contributing to the problem.