Watchdog detected hard LOCKUP on cpu 9

Bug #1450910 reported by TK
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Experiencing system lockups while idle on Ubuntu 14.04.2, kernel 3.16.0-36. Appears to be related to Bug 1004313

Description: Ubuntu 14.04.2 LTS
Release: 14.04

Attached are the details from syslog:

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-36-generic 3.16.0-36.48~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9
Uname: Linux 3.16.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
Date: Fri May 1 13:27:07 2015
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 1 11:30 seq
 crw-rw---- 1 root audio 116, 33 May 1 11:30 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.10
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:
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg: [22218.731864] init: tty1 main process ended, respawning
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=65cea15a-996b-45f6-80fe-200ee1f11ab4
MachineType: Dell Inc. PowerEdge R430
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=8070b71a-7af3-4a37-a8a6-679255d4ee49 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-36-generic N/A
 linux-backports-modules-3.16.0-36-generic N/A
 linux-firmware 1.127.11
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.16.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/17/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.2
dmi.board.name: 03XKDV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd11/17/2014:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn03XKDV:rvrA00:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R430
dmi.sys.vendor: Dell Inc.

Revision history for this message
TK (biotech) wrote :
Revision history for this message
penalvch (penalvch) wrote :

TK, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1450910

affects: linux-lts-utopic (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
TK (biotech) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
TK (biotech) wrote : IwConfig.txt

apport information

Revision history for this message
TK (biotech) wrote : Lspci.txt

apport information

Revision history for this message
TK (biotech) wrote : Lsusb.txt

apport information

Revision history for this message
TK (biotech) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
TK (biotech) wrote : ProcInterrupts.txt

apport information

Revision history for this message
TK (biotech) wrote : ProcModules.txt

apport information

Revision history for this message
TK (biotech) wrote : UdevDb.txt

apport information

Revision history for this message
TK (biotech) wrote : UdevLog.txt

apport information

Revision history for this message
TK (biotech) wrote : WifiSyslog.txt

apport information

Revision history for this message
TK (biotech) wrote :

Thanks Christopher, I just submitted the report.

Revision history for this message
penalvch (penalvch) wrote :

TK, could you please post to this report a screenshot or preferrably export to CSV, of the Lifecycle firmware versions screen for all your hardware?

Revision history for this message
TK (biotech) wrote :

Here you go - csv is attached.

Revision history for this message
penalvch (penalvch) wrote :

TK, as per http://www.dell.com/support/home/us/en/04/product-support/product/poweredge-r430/drivers an update to your computer's buggy and outdated firmware is available:
BIOS > 1.1.10
iDRAC > 2.10
Lifecycle Controller > 2.10
Broadcom Ethernet > 7.10.59
HDDs > ?

If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, again provide the firmware inventory CSV?

For more on firmware updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note you don't have to create a new bug report.

Once the all the firmware is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

Revision history for this message
TK (biotech) wrote :

Hello,

I just wanted to update that since updating all of the firmware I haven't experienced the problem anymore. I'll keep monitoring the issue, but so far this looks promising.

Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
penalvch (penalvch) wrote :

TK, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450910/comments/16 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Expired → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.