[LENOVO 8932GNG] hibernate/resume failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
restart
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.16.0-16-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA:
country EU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Date: Tue Sep 23 11:41:51 2014
DuplicateSignature: hibernate/
ExecutablePath: /usr/share/
Failure: hibernate/resume
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-09-15 (7 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta1 amd64 (20140828)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 8932GNG
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.134
SourcePackage: linux
Title: [LENOVO 8932GNG] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/09/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7OETC4WW (2.24 )
dmi.board.name: 8932GNG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 8932GNG
dmi.product.
dmi.sys.vendor: LENOVO
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 #1372852, 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.