[Toshiba Tecra R850-14Q] suspend/resume failure

[Paweł Stołowski]

Resume doesn't work for me in Ubuntu 14.04. When I close the lid, or issue pm-suspend manually, the system gets suspended, but opening the lid results in black screen and laptop fan gets really loud. There is no way to recover from that. Reproducible every time.

WORKAROUND: Use kernel boot parameter:
nox2apic

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-34-generic 3.13.0-34.60
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pawel 4150 F.... pulseaudio
Date: Fri Aug 29 08:52:53 2014
DuplicateSignature: suspend/resume:TOSHIBA TECRA R850:Version 3.00
ExecutablePath: /usr/share/apport/apportcheckresume
ExecutableTimestamp: 1406572220
Failure: suspend/resume
InstallationDate: Installed on 2014-04-12 (138 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140411)
InterpreterPath: /usr/bin/python3.4
MachineType: TOSHIBA TECRA R850
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcCwd: /
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=c52f003e-a221-4500-a0ee-11d9d7617244 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-34-generic N/A
 linux-backports-modules-3.13.0-34-generic N/A
 linux-firmware 1.127.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [TOSHIBA TECRA R850] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/06/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.00
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.00:bd08/06/2011:svnTOSHIBA:pnTECRAR850:pvrPT525E-00V00QPL:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA R850
dmi.product.version: PT525E-00V00QPL
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This change was made by a bot.

[Paweł Stołowski (stolowski)]

Hi Christopher, thanks for pointers, I've updated the BIOS as requested (neither wine nor VM with Windows running provided any help due to a check for toshiba hardware early on startup of the downloaded exe; what did the trick for me was cabextract for obtaining bios file & updater + a bootable freedos iso).

That didn't help, unfortunately. Here is dmidecode output:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Version 4.10
01/08/2013

This is what happens:
1) sudo pm-suspend suspends my laptop.
2) pressing the power button should resume it - the display gets turned on but remains black, and shortly after that the fan gets very loud and runs at full speed.
3) there is no way to recover from that - except for forced shutdown with power button.

Symptoms are exactly the same if I configure my desktop to suspend on lid closing.

[penalvch (penalvch)]

Pawel Stolwski, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.17-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Paweł Stołowski (stolowski)]

Ok, tested with the latest mainline kernel found here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc2-utopic/

$ uname -a
Linux mordor 3.17.0-031700rc2-generic #201408251935 SMP Mon Aug 25 23:36:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The problem persists, marking as Confirmed.

[penalvch (penalvch)]

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

[Paweł Stołowski (stolowski)]

I've followed that wiki instructions but didn't find anything useful following "Magic number" dmesg message... Attaching dmesg output (after sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" and forced shutdown and restart) and /proc/acpi/wakeup contents.

[penalvch (penalvch)]

Pawel Stolowski, did this problem not occur in a release prior to Trusty?

[Paweł Stołowski (stolowski)]

I had no problems with suspend/resume prior to Trusty.

Also, I *think* it worked around 14.04 was released (I've been running Trusty beta since approximately March/April); however, I've just tried an older linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb (from May 5th) but that didn't help, so either I was running an older (beta) kernel at the time it worked, or the problem is somewhere else (is it possible a userland component causes a regression?).

[penalvch (penalvch)]

Pawel Stolowski, the next step is to fully commit bisect the kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Paweł Stołowski (stolowski)]

Hi Christopher, I haven't done kernel bisect, but instead did a lot of googling, and found this bug:

https://bugzilla.kernel.org/show_bug.cgi?id=42977

which is affects some other Toshiba Tecra laptop, but have same symptomps and moreover, the proposed workaround with nox2apic kernel commandline option seems to be working for me!

Apparently, the problem has been present in the kernel for quite some time, which really confuses me, as I'm pretty sure suspend/resume worked for me for at least some time before; unfortunately I don't know the good kernel version to start with, which makes bisecting impossible. Also, out of curiosity I tested my laptop with a live version of debian-7.6.0, and it also hangs with same symptomps.