BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udevd:16098]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I get multiple system problems upon every boot. it seems CPU#0 is getting stuck for a number of seconds and the system problem notifications all allude to the times that CPU#0 has been stuck.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.13.0-48-generic i686
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.14.4-
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Thu Apr 2 09:20:09 2015
DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [systemd-
Failure: oops
HibernationDevice: RESUME=
InstallationDate: Installed on 2015-02-05 (63 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
SourcePackage: linux
Title: BUG: soft lockup - CPU#0 stuck for 23s! [systemd-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.43
dmi.board.
dmi.board.name: 3629
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 18.50
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1442706, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.