[Sony Corporation VGN-FW235J] suspend/resume failure

[Stephen Cradock]

laptop suspended after minor update Feb 10th 2013; did not resume, rebooted.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-5-generic 3.8.0-5.10
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
Uname: Linux 3.8.0-5-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sc 2105 F.... pulseaudio
Date: Sun Feb 10 09:39:59 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=25e8dad4-8431-4c6f-a510-6fb007bf5bee
InstallationDate: Installed on 2012-10-21 (111 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python3.3
MachineType: Sony Corporation VGN-FW235J
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 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.8.0-5-generic N/A
 linux-backports-modules-3.8.0-5-generic N/A
 linux-firmware 1.101
SourcePackage: linux
Title: [Sony Corporation VGN-FW235J] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation

[Brad Figg (brad-figg)]

This change was made by a bot.

[Brad Figg (brad-figg)]

There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.

You can update to the latest kernel by simply running the following commands in a terminal window:
    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the
bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Stephen Cradock (s-cradock)]

OK - checked as you asked. I'm currently running kernel 3.10.0-3-generic, and the behavior is exactly as before - "sudo pm-suspend" puts the machine into suspend state, but attempting to resume (enter, mouse,...) causes a reboot. The pm-suspend.log file ends at "performing suspend"; there are no entries relating to resuming.

Changed to Confirmed.

[penalvch (penalvch)]

Stephen Cradock, 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 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-rc3

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.

[Stephen Cradock (s-cradock)]

OK - done that, with kernel 3.11-rc4. Same behaviour - suspend occurs, but attempt to wake up leads to reboot.

Marked as Confirmed and tags added as requested.

[penalvch (penalvch)]

Stephen Cradock, thank you for testing the latest mainline kernel. Did this problem not occur in a release prior to Raring?

[Stephen Cradock (s-cradock)]

The same failure occurs with Precise (kernel 3.2.0-52) on this machine.

I cannot tell when this started - I don't use the suspend function normally, and I only test it sporadically. I've been running this machine with successive versions of Ubuntu for somewhere around a couple of years, I believe.

[penalvch (penalvch)]

Stephen Cradock, for regression testing purposes, could you please test Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[Stephen Cradock (s-cradock)]

The machine recovers from suspend as expected using Lucid. I tried both selecting Suspend from the close-down menu and typing the command "sudo pm-suspend" in the terminal.

In both cases the recovery occurred without problems.

[Stephen Cradock (s-cradock)]

Update: I have checked the resume from suspend using the Ubuntu Saucy kernel (3.10.0-6-generic), AFTER the successful suspend and resume in Lucid. It works perfectly!

[Stephen Cradock (s-cradock)]

Also checked with mainline kernel 3.11-rc4 - resumes perfectly from suspend.

[penalvch (penalvch)]

Stephen Cradock, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

[Stephen Cradock (s-cradock)]

Thanks for asking. I don't believe the kernel is at fault here - more likely something in the hardware got stuck and didn't return to normal until the resume in Lucid. I can't see any other reason for an error that shows up in ALL installs (6 or so on this machine at the moment) and then magically goes away in ALL of them as far as I've checked.

Now solving THAT would be great - but I'm not holding my breath. Maybe I'll just keep the Lucid install around in case it happens again...

One possible contributor - some of the installs are on a USB external disk, but the original Raring report came from the internal HD. This machine has difficulty booting the installs on the external drive, because it isn't mounted at startup, and something similar might be happening with suspend.

Yes, please close the bug.

[penalvch (penalvch)]

Stephen Cradock, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121312/comments/11 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.