BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583]

Bug #1515679 reported by don lesniakowski
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-66-generic 3.13.0-66.108
ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: don 2156 F.... pulseaudio
 /dev/snd/controlC0: don 2156 F.... pulseaudio
CurrentDmesg: [ 48.797509] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Thu Nov 12 10:56:56 2015
DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583] RIP: 0010:location location smp_call_function_many+0x268/0x2d0
Failure: oops
HibernationDevice: RESUME=UUID=ffd2b5a3-0e8e-4f9b-9288-cff133a90145
InstallationDate: Installed on 2011-12-18 (1424 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=9f13b409-27bd-4e42-99c0-59fccdb87241 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: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583]
UpgradeStatus: Upgraded to trusty on 2014-08-18 (451 days ago)
dmi.bios.date: 07/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
don lesniakowski (donles) 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
don lesniakowski (donles) wrote : Re: [Bug 1515679] Status changed to Confirmed
Download full text (50.4 KiB)

A bot? Malicious?
What should I do?
On Nov 12, 2015 11:35 AM, "Brad Figg" <email address hidden> wrote:

> This change was made by a bot.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1515679
>
> Title:
> BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583]
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> version.log - Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
> lspci-vnvn.log -
> 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core
> Processor Family DRAM Controller [8086:0100] (rev 09)
> Subsystem: ASUSTeK Computer Inc. P8P67/P8H67 Series Motherboard
> [1043:844d]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort+ >SERR- <PERR- INTx-
> Latency: 0
> Capabilities: [e0] Vendor Specific Information: Len=0c <?>
>
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation
> Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if
> 00 [Normal decode])
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- <SERR- <PERR-
> BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
> PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
> Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device
> [1043:844d]
> Capabilities: [80] Power Management version 3
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Address: fee0f00c Data: 4171
> Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0
> ExtTag- RBE+
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 128 bytes
> DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
> TransPend-
> LnkCap: Port #2, Speed 5GT/s, Width x16, ASPM not
> supported, Exit Latency L0s <1us, L1 <4us
> ClockPM- Surprise- LLActRep- BwNot+
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMg...

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

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.3-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
don lesniakowski (donles) wrote : Re: [Bug 1515679] Re: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583]

   I began to have problems one or two days ago before I performed an
update today.
The problems were in the form of error notice dialog bubbles that appeared
during normal use.
I spent time yesterday working on spreadsheets, both online (Google) and
locally (LibreOffice).
I don't remember the details.
   Today, I saw the update notice, so I closed Firefox and LibreOffice and
began the update. I came back awhile later and found an error dialog
again. I closed the error dialog but the update was frozen. I should have
taken a screenshot of the update details but did not.
   I tried starting System Monitor and Firefox from the launcher. I got
the little busy symbol while they tried to start but they did not start. I
started Gnucash and closed it. I attempted to restart (via the button at
top right desktop) but that didn't work. I had a terminal window open at
the time and saw the shutting-down broadcast message but it didn't
restart. I selected shutdown but that didn't work either. Finally, I held
the power button down and restarted.
   I was surprised when the restart was successful. I expected to have a
problem because I had a problem months ago with the grub bootloader but
that passed.
   Since the restart, I've worked on LibreOffice sheets and Firefox but not
Google docs. I have experienced error messages and have included two
recent screenshots taken while I've composed this.

   I'm willing to assist but be aware I'm not a computer science major. I
need instruction.

Don Lesniakowski
412-417-4394

On Thu, Nov 12, 2015 at 12:06 PM, Joseph Salisbury <
<email address hidden>> 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.3 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'.
>
> 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.3-wily/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1515679
>
> Title:
> BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:22583]
>
> Status in linux package in Ubuntu:
> Incomplete
>
> ​.....​
>
> <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515679/+subscriptions>
>

penalvch (penalvch)
description: updated
tags: added: bios-outdated-4105
tags: removed: need-duplicate-check
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.