BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]

Bug #1280642 reported by rajesh
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-8-generic 3.13.0-8.28
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.13.2-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 1380 F.... pulseaudio
                      dinesh 2037 F.... pulseaudio
Date: Sat Feb 15 09:18:15 2014
DuplicateSignature:
 BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]
 EIP: 0060:location EFLAGS: 00000202 CPU: 1
Failure: oops
HibernationDevice: RESUME=UUID=4cc2dadc-c747-43d9-8938-ea8bf907df2b
InstallationDate: Installed on 2013-11-05 (102 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MachineType: Hewlett-Packard HP Compaq 6710s (GP167PA#ACJ)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=2bc9b372-0240-46b3-bf0d-d43bef7fdcdc ro quiet splash
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-3ubuntu4
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.06
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.26
dmi.chassis.asset.tag: CNU7240WZS
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.06:bd04/14/2007:svnHewlett-Packard:pnHPCompaq6710s(GP167PA#ACJ):pvrF.06:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.26:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6710s (GP167PA#ACJ)
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
rajesh (bhatt-rajesh20) wrote :
tags: removed: need-duplicate-check
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 :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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/v3.14-rc3-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
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
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Derrell Durrett (derrelldurrett) wrote :

I am currently affected by this bug. I would like to help, but it's not at all obvious to me what tools I would use to investigate this. I am an experienced software developer, just not in the kernel, nor in the kernel's debugging tools/process. I am subscribed to emails for this bug, and would gladly do anything helpful to solve this as it impacts my development.

Thanks,

Derrell

Revision history for this message
Derrell Durrett (derrelldurrett) wrote :

/var/log/syslog attached.

penalvch (penalvch)
no longer affects: xorg (Ubuntu)
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.