[FUJITSU LIFEBOOK A544] suspend/resume failure

[Colin Law]

On resume the screens (laptop + external) showed windows as before suspend but the machine was completely unresponsive.

This happens around 1 in 10 times I suspend. I am suspending using pm-suspend or via the cog > Suspend.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-14-generic 4.2.0-14.16
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system from resuming properly.
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: colinl 1670 F.... pulseaudio
 /dev/snd/controlC1: colinl 1670 F.... pulseaudio
Date: Thu Oct 8 19:33:00 2015
DuplicateSignature: suspend/resume:FUJITSU LIFEBOOK A544:Version 1.19
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2014-10-21 (352 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
InterpreterPath: /usr/bin/python3.4
MachineType: FUJITSU LIFEBOOK A544
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
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.2.0-14-generic N/A
 linux-backports-modules-4.2.0-14-generic N/A
 linux-firmware 1.149
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
Title: [FUJITSU LIFEBOOK A544] suspend/resume failure
UpgradeStatus: Upgraded to wily on 2015-08-31 (38 days ago)
UserGroups:

dmi.bios.date: 04/01/2015
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.19
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Colin Law, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Colin Law (colin-law)]

Tested with mainline kernel 4.3.0 rc5 and got the same failure, though it seemed to take longer before it failed. Likely just the statistics working themselves out though.

[penalvch (penalvch)]

Colin Law, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Colin Law (colin-law)]

After several weeks running with the suspend command
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
with both the latest mainline kernel I was unable to make it fail. I reverted to the current kernel and it still refused to fail. I then resorted to just using pm_suspend (with current kernel) and it did fail. I don't know whether it is necessary to have
echo 1 > /sys/power/pm_trace
on every suspend but from dmesg > dmesg.txt I see
$ grep -i "hash matches" dmesg.txt
[ 2.322145] bdi 1:12: hash matches
[ 2.322151] tty ttyS14: hash matches

Suggestions on what I should do next please?