watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-sleep:25196]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
18.04LTS Bionic Beaver - When the computer is set to automatic suspend the CPU gets stuck and crashes when resuming from suspend mode
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelMo
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sat Apr 14 22:40:12 2018
Failure: oops
HibernationDevice: RESUME=
InstallationDate: Installed on 2017-05-31 (318 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
IwConfig:
enp3s0 no wireless extensions.
lo no wireless extensions.
tun0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-
UpgradeStatus: Upgraded to bionic on 2018-03-08 (37 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.