[Sony Corporation VGN-P11Z_G] suspend/resume failure

[George Iosif]

Suspending (to RAM) the laptop seems to complete ok.
However, on trying to resume the system, although the screen is activated (i.e. the video card is re-activated properly), there is nothing displayed, neither on the graphical part (i.e. X), nor if I switch to a console.
This works on another distro.
FYI, I have to provide 'ADD_PARAMETERS="--quirk-vbemode-restore"' in /etc/pm/config.d/gma500 for suspend/resume to work on this laptop (which I've done here too).

ProblemType: KernelOops
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-16-generic 3.5.0-16.25
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: giosif 1903 F.... xfce4-volumed
                      giosif 1925 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Sun Sep 30 19:45:59 2012
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=caf82bbd-2ed1-4241-bc49-8ed2e5d55175
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
InterpreterPath: /usr/bin/python3.2mu
MachineType: Sony Corporation VGN-P11Z_G
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 psbfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=894782cf-1bb8-406b-93c2-c06e5d894199 ro mem=1920mb 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.5.0-16-generic N/A
 linux-backports-modules-3.5.0-16-generic N/A
 linux-firmware 1.94
SourcePackage: linux
Title: [Sony Corporation VGN-P11Z_G] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/13/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: R2073U3
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:bvnINSYDE:bvrR2073U3:bd01/13/2010:svnSonyCorporation:pnVGN-P11Z_G:pvrJ003NN7L:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-P11Z_G
dmi.product.version: J003NN7L
dmi.sys.vendor: Sony Corporation

[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.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.6-quantal/

[George Iosif (giosif)]

Hi,

I've installed kernel 3.6, but there was no change in behavior.
However, the actual problem was somewhere else: in my /etc/pm/config.d/gma500 file.
You see, in other distro's I tried, I used the '"ADD_PARAMETERS="--quirk-vbemode-restore"' option with two dashes before the "quirk" word, and that worked fine.
Now, I remember reading somewhere that, in some cases, it only works with one dash (i.e. "-quirk..."), not two, which seems to be the case here too.
So, I now have a working suspend/resume setup on my laptop (it works in both the current distro kernel and with mainline 3.6).

Thank you for the support and apologies for not validating all options before opening the bug!

Best regards,
George Iosif

[Launchpad Janitor (janitor)]

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