watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]

Bug #1791545 reported by Chris Allen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned
Cosmic
Fix Released
High
Unassigned

Bug Description

FYI, getting this error message on my gemini-lake-based laptop when running the daily 18.10 build

ProblemType: KernelOops
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-9-generic 4.17.0-9.10
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: callen 1691 F.... pulseaudio
Date: Sun Sep 9 13:13:25 2018
Failure: oops
InstallationDate: Installed on 2018-08-16 (23 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
MachineType: Acer Swift SF114-32
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.03
dmi.board.name: Sapporo_GL_S
dmi.board.vendor: GLK
dmi.board.version: V1.03
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.03
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03:
dmi.product.family: Swift 1
dmi.product.name: Swift SF114-32
dmi.product.version: V1.03
dmi.sys.vendor: Acer

Revision history for this message
Chris Allen (callen92) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) 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 :

Can you see if this bug still exists in the latest Cosmic 4.18 based kernel?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-key
Revision history for this message
Chris Allen (callen92) wrote :

It stopped since the last 4.17 kernel update via apt so I think it's been resolved.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the update. I'll mark this bug as Fix Released. Just move it back to confirmed if the bug comes back.

Changed in linux (Ubuntu Cosmic):
status: Confirmed → Fix Released
Brad Figg (brad-figg)
tags: added: cscc
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.