[SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA] suspend/resume failure

[Maxim Baskakov]

Don't wake up after gibernation

ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-15-generic 4.4.0-15.31
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system from resuming properly.
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ksaver1 1520 F.... pulseaudio
 /dev/snd/controlC0: ksaver1 1520 F.... pulseaudio
Date: Tue Mar 22 02:07:51 2016
DuplicateSignature: suspend/resume:SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA:09PW.ME13.20121101.SKK
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=b782452f-51f9-40a8-bc11-9d17250476d5
InstallationDate: Installed on 2014-09-11 (557 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140905)
InterpreterPath: /usr/bin/python3.5
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=1d3eb423-3f2f-4529-a70d-6e8c0e028ce6 ro noplymouth ipv6.disable=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-15-generic N/A
 linux-backports-modules-4.4.0-15-generic N/A
 linux-firmware 1.157
SourcePackage: linux
Title: [SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lp
dmi.bios.date: 11/01/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 09PW.ME13.20121101.SKK
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 305V4A/305V4A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 09PW
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr09PW.ME13.20121101.SKK:bd11/01/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn305V4A/305V5A/3415VA:pvr09PW:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305V4A/305V4A:rvr09PW:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 305V4A/305V5A/3415VA
dmi.product.version: 09PW
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

[Maxim Baskakov (ksaver)]

This issue started happening since upgrading from 4.4.0-11 kernel to 4.4.0-12 from main repo and so on to 4.4.0-15. While tested v.4.5, the bug still exists.

[b]tags[/b]: kernel-bug-exists-upstream