[TOSHIBA Satellite M115-S3094] suspend/resume failure

[matti salminen]

As soon as the UI comes up, I get cascading 3 or 4 system errors. Regardless, the system appears to work after those.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-18-generic 3.16.0-18.25
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matti 2648 F.... pulseaudio
Date: Sun Sep 28 13:42:29 2014
DuplicateSignature: suspend/resume:TOSHIBA Satellite M115:1.20
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=d0b9ab97-3086-46a8-b6e3-5ad72e431801
InstallationDate: Installed on 2014-03-02 (210 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140217)
InterpreterPath: /usr/bin/python3.4
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite M115
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic root=/dev/mapper/ubuntu--vg-root 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.16.0-18-generic N/A
 linux-backports-modules-3.16.0-18-generic N/A
 linux-firmware 1.134
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [TOSHIBA Satellite M115] suspend/resume failure
UpgradeStatus: Upgraded to utopic on 2014-09-09 (19 days ago)
UserGroups:

dmi.bios.date: 10/11/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.20
dmi.board.name: MPAD-MSAE Customer Reference Boards
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.20:bd10/11/2006:svnTOSHIBA:pnSatelliteM115:pvrPSMB0U-015007:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Satellite M115
dmi.product.version: PSMB0U-015007
dmi.sys.vendor: TOSHIBA

[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.17 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.17-rc7-utopic/

[matti salminen (salmiset)]

Tested with kernel v3.17-rc7-utopic. The bug persists.

[penalvch (penalvch)]

matti salminen, as per http://support.toshiba.com/support/techPack?mid=1468771#currentBiosDiv an update to your BIOS is available (1.90). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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