TOSHIBA Satellite L875D suspend/resume failure

[Ian Nicholson]

When I resume from suspend, the screen doesn't turn on. This requires me to press the power button to trigger a shutdown. This error occurred after that happend and I started my computer again.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ian 2165 F.... pulseaudio
 /dev/snd/controlC0: ian 2165 F.... pulseaudio
Date: Fri Aug 30 16:42:06 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=83dc2a46-b947-41a8-b1bc-49ad9b58807c
InstallationDate: Installed on 2013-08-09 (21 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterpreterPath: /usr/bin/python3.3
MachineType: TOSHIBA Satellite L875D
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-4-generic root=/dev/mapper/ubuntu--vg-root ro i8042.nomux=1 i8042.reset quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-4-generic N/A
 linux-backports-modules-3.11.0-4-generic N/A
 linux-firmware 1.113
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [TOSHIBA Satellite L875D] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-08-09 (21 days ago)
UserGroups:

dmi.bios.date: 12/06/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PLCSC8
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L875D
dmi.product.version: PSKFQU-003034
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Ian Nicholson, could you please provide the full computer model as noted on the sticker?

[Ian Nicholson (imnichol)]

Model number is L875D-S7111

[penalvch (penalvch)]

Ian Nicholson, did this problem not occur in a release prior to Saucy?

[Ian Nicholson (imnichol)]

On 09/02/2013 03:53 PM, Christopher M. Penalver wrote:
> Ian Nicholson, did this problem not occur in a release prior to Saucy?
>
> ** Tags removed: needs-full-computer-model
> ** Tags added: latest-bios-6.30
>
I don't know. I bought this system about a month ago and immediately
installed 13.10.

[penalvch (penalvch)]

Ian Nicholson, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ ?

[Ian Nicholson (imnichol)]

On 09/02/2013 05:57 PM, Christopher M. Penalver wrote:
> Ian Nicholson, for regression testing purposes, could you please test
> for this in Precise via http://releases.ubuntu.com/precise/ ?
>
I'm using this as my daily driver, so it's possible, but at the moment I
don't have time to reinstall with 12.04. Unless there's a way to
downgrade without reinstalling.

[penalvch (penalvch)]

Ian Nicholson, one may test suspend in the live environment.

[Ian Nicholson (imnichol)]

On 09/02/2013 06:32 PM, Christopher M. Penalver wrote:
> Ian Nicholson, one may test suspend in the live environment.
Oh, awesome. I'll see what I can do.

[Ian Nicholson (imnichol)]

I'm closing this because it no longer affects me. Suspend/Resume began working around the time that I installed the proprietary video drivers, and I suspect that the root problem was that the screen was not turning on when the system resumed.