[TOSHIBA PORTEGE Z830] suspend/resume failure

[manfreed]

No additional details. I suspended my computer normally, later when I started it apport offered me to report a bug, so I did it.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-2-generic 3.10.0-2.10
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: manfreed 2629 F.... pulseaudio
 /dev/snd/pcmC0D0p: manfreed 2629 F...m pulseaudio
Date: Wed Jul 10 23:38:15 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=10256df4-bbdb-45f5-8a43-3a83b6a9b111
InstallationDate: Installed on 2013-04-29 (72 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterpreterPath: /usr/bin/python3.3
MachineType: TOSHIBA PORTEGE Z830
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-2-generic root=/dev/mapper/hostname-root ro quiet libata.force=noncq splash pcie_aspm=force i915.i915_enable_fbc=1 i915.lvds_downclock=1 acpi_osi=Linux acpi_backlight=vendor elevator=noop vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-2-generic N/A
 linux-backports-modules-3.10.0-2-generic N/A
 linux-firmware 1.110
SourcePackage: linux
Title: [TOSHIBA PORTEGE Z830] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-06-24 (16 days ago)
UserGroups:

dmi.bios.date: 07/31/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.70
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:bvrVersion1.70:bd07/31/2012:svnTOSHIBA:pnPORTEGEZ830:pvrPT224E-017014HU:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE Z830
dmi.product.version: PT224E-017014HU
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

manfreed, thank you for reporting this and helping make Ubuntu better. As per http://www.toshiba.hu/innovation/jsp/supportMyProduct.do?LNG=23&service=CE an update is available for your BIOS (1.80). If you update to this, does it change anything?

If not, could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[manfreed (manfreed)]

Hi! I've upgraded my BIOS a few days ago. Since I reported this bug I only experienced the issue now.

I wanted to restart my computer. Since I was in a terminal I issued an "init 6" command. The computer started to shut down (apps started to close), but for some reason It suspended itself instead of a reboot (the power light started to pulse).

Might be important to mention that the lid was closed the whole time since I use external monitors. After I opened the lid the laptop started itself automatically (normal boot process), and apport showed up immediately.

My BIOS info:
Version 1.80
04/18/2013

[penalvch (penalvch)]

manfreed, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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. For example:
kernel-fixed-upstream-v3.11-rc1

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. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-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.

[manfreed (manfreed)]

Hi!

I apologize for not being able to test in the past few weeks.
I tried to reproduce the issue with v3.11-rc3-saucy, but I wasn't able to do so.
I'm not certain if the problem got fixed, because I couldn't even reproduce using the kernel I've used when I reported the issue.

I'm not certain wich tags should I add, or remove.

[penalvch (penalvch)]

manfreed, we can keep an eye on it, as it may be an intermittent suspend issue. If it happens again we can take it from there.

[Launchpad Janitor (janitor)]

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