[Notebook P15SM] suspend/resume failure

[gomez]

while trying to suspend, ubunto was shutting down, the screen was black, but not off. in this state i waited for quite a while but finally i shut the computer off by the 4 second press on the power button.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-20-generic 3.13.0-20.41
ProcVersionSignature: Ubuntu 3.13.0-20.41-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gomez 1949 F.... pulseaudio
 /dev/snd/controlC0: gomez 1949 F.... pulseaudio
Date: Sat Mar 29 17:28:16 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=617acc90-a350-4c3a-8929-4e73f2f10418
InstallationDate: Installed on 2014-03-27 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
InterpreterPath: /usr/bin/python3.4
MachineType: Notebook P15SM
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=f5e5f03d-2e96-4a17-9474-298b562d185a 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:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [Notebook P15SM] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: P15SM
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/26/2013:svnNotebook:pnP15SM:pvrNotApplicable:rvnNotebook:rnP15SM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: P15SM
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.14-trusty/

[gomez (gomez-jinrin)]

Hi Joseph,
i installed the Kernel and headers (
linux-image-3.14.0-031400-generic_3.14.0-031400.201403310035_amd64.deb
linux-headers-3.14.0-031400_3.14.0-031400.201403310035_all.deb
linux-headers-3.14.0-031400-generic_3.14.0-031400.201403310035_amd64.deb
) , i also have Nvidia drivers 331 installed and running with bumblebee, which is working fine.
I think the Notebook is not suspending with loaded nvidia drivers. so perhaps the Kernel Oops might have come from that?
.
I already Booted the Kernel and suspended too times (just intel graphics)
Now i will try with an application with loaded nvidia driver. This is working fine too.

BTW i could not reproduce the suspend Problem again. i don't know if it would happen again.

Thanks in advance.
When it happens again with the loaded 3.14 Mainline Kernel i will get back to this bug. for now it seems fixed upstream

Kind Regards
Thomas

[gomez (gomez-jinrin)]

BTW
As i am not very good in going through logfiles and decyphering them, do you see anything how i could reproduce the error?

i don't want to let this be marked as fixed, and i dont know what should be fixed ;)

Glad to help and if there is some more testing, i try to help.

Regards
Thomas