NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [Xorg:1028]

Bug #1435411 reported by Jeff Burns
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Was in KDE environment and rebooted after installing this mornings updates. Upon logging in selected Ubuntu and received this error. System appears to be operational though.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: fglrx
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jburns 2281 F.... pulseaudio
Date: Thu Mar 19 08:56:32 2015
Failure: oops
HibernationDevice: RESUME=UUID=63579326-0de4-44ec-a9f2-b0841a9e5e60
InstallationDate: Installed on 2015-03-03 (19 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: Supermicro H8DG6/H8DGi
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:

SourcePackage: linux
Title: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s! [Xorg:1028]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.5
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: H8DG6/H8DGi
dmi.board.vendor: Supermicro
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.5:bd11/25/2013:svnSupermicro:pnH8DG6/H8DGi:pvr1234567890:rvnSupermicro:rnH8DG6/H8DGi:rvr1.0:cvnSupermicro:ct17:cvr1234567890:
dmi.product.name: H8DG6/H8DGi
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro

Revision history for this message
Jeff Burns (admiraljkb) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.0-rc5-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jeff Burns (admiraljkb) wrote :

Its looking like it might have been a one time thing. It did occur right after an update (but not a kernel update). I've rebooted twice since and have had no re-occurrence. I'm attaching my update history in case that might shed some light on it.

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
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.