[Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume failure

[Sascha Biermanns]

When opening the lip, to resume after suspend, the computer was frozen and some LED's where blinking in a regular rhythmn. I had to reset the Toughbook to restart it.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: boot/vmlinuz-3.19.0-7-generic]
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: skb 2372 F.... pulseaudio
Date: Wed Mar 4 10:16:51 2015
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2015-03-02 (1 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150302)
InterpreterPath: /usr/bin/python3.4
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic root=UUID=00bc12a3-0121-4e30-8834-27fafd4a0666 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.
SourcePackage: linux
Title: [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/10/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.00L11
dmi.board.name: CF19-2
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-19FHGAXBG
dmi.product.version: 002
dmi.sys.vendor: Matsushita Electric Industrial 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.0 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/v4.0-rc2-vivid/

[Sascha Biermanns (skbierm)]

I just installed Ubuntu 15.04 yesterday, and so I can only say, it happened with the installation from yesterdays actual kernel.

[Sascha Biermanns (skbierm)]

Suspend work in kernel 4.0.0-040000rc2-generic, installed via package linux-image-4.0.0-040000rc2-generic_4.0.0-040000rc2.201503031836_amd64 from kernel mainline builds

[penalvch (penalvch)]

Sascha Biermanns, the next step is to fully reverse commit bisect from kernel 3.19 to 4.0-rc2 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]