[Sony VAIO VPCF119HX] suspend/resume failure non-free: nvidia

[Adam Colligan]

I have now reproduced this bug with suspend using only Xorg video drivers and the latest kernel. The issue is that upon resume from suspend, the computer kicks all the way down to the boot sequence and cannot restore a session. A Kernal Oops is reported by apport check resume on login. Attempted hybrid suspend from command line.

Upstream post: http://thread.gmane.org/gmane.linux.power-management.general/42208

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-12-generic 3.8.0-12.21
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
NonfreeKernelModules: nvidia
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: adam 3039 F.... pulseaudio
 /dev/snd/controlC0: adam 3039 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Wed Mar 13 18:51:12 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=211ef7b9-3f94-4709-a92b-3cad2e8dacb2
InstallationDate: Installed on 2013-02-12 (29 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
InterpreterPath: /usr/bin/python3.3
MachineType: Sony Corporation VPCF119HX
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-12-generic root=/dev/mapper/4lgroup-root ro quiet splash acpi_backlight=sony
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-12-generic N/A
 linux-backports-modules-3.8.0-12-generic N/A
 linux-firmware 1.104
SourcePackage: linux
Title: [Sony Corporation VPCF119HX] suspend/resume failure [non-free: nvidia]
UpgradeStatus: Upgraded to raring on 2013-03-09 (4 days ago)
UserGroups: fuse
dmi.bios.date: 05/14/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0280Y6
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.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF119HX:pvrA222GY5F:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCF119HX
dmi.product.version: A222GY5F
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.

[Adam Colligan (adam-p)]

As of today, still tracking with the latest updates:

Hibernate appears to be functioning (re: bug 1153323).

The suspend failure has reverted to something that looks like this original bug report. The machine enters what appears to be a suspend power state (e.g., pulsing orange power light). But upon resume, a full boot sequence ensues, the session does not appear to be saved, and error messages appear indicating resume failure.

I have therefore marked this bug confirmed per Brad Figg's message on 2013-07-19; I will continue to update when any changes are noticed.

[penalvch (penalvch)]

Adam Colligan, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Launchpad Janitor (janitor)]

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

[Brad Figg (brad-figg)]

This change was made by a bot.

[Adam Colligan (adam-p)]

I have now had a chance with the latest OS version and kernel to re-run this bug for upstream submission. I am re-opening it here and will shortly attach the information to be emailed to the pm maintainer.

[Adam Colligan (adam-p)]

Here is the report for maintainer e-mail.

[penalvch (penalvch)]

Adam Colligan, did this problem not occur in a release prior to Raring?

[Adam Colligan (adam-p)]

The problem has occurred in various forms since I started using Ubuntu during Precise. There was a brief period in which it did work correctly; I think that may have been during the Raring cycle. So technically it may be a regression, but it isn't a new one, and I don't think I can pinpoint the window in which it worked on this machine.

[penalvch (penalvch)]

Adam Colligan, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Adam Colligan (adam-p)]

Just to be clear, I am currently running and testing on Saucy.

[Adam Colligan (adam-p)]

Additional information from https://wiki.ubuntu.com/DebuggingKernelSuspend attached here.

[penalvch (penalvch)]

Adam Colligan, just to clarify, when you performed your testing in releases other than Raring (Precise, Saucy) were you using the nvidia drivers or nouveau?

[Adam Colligan (adam-p)]

I got an earlier email update on this thread as

<blockquote>Adam Colligan, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked.

Thank you for your understanding.</blockquote>

I have followed all of those instructions to the best of my ability. I sent the full initial report to the maintainer address listed in my attachment at comment #9, and this morning I sent the same address the additional debugging information attached to #15. Those instructions included providing a link to a Launchpad bug report, which is why I re-opened this report, so that there would be a live and current target for such a link. I am not sure about how to find a link to my actual email to <email address hidden> ; I do not see it at http://rss.gmane.org/messages/excerpts/gmane.linux.power-management.general . I don't know if this means it could have been filtered for some reason; it was a very long plain text message with everything in-line, which I believe is what was instructed. I don't know if it's possible that it being PGP/SMIME could mess it up? I don't want to spam the list with duplicates.

Re: video drivers used for testing --

My nominal setup is to use Nvidia drivers. However, testing upstream kernels tends to break my entire video setup and has necessitated very long periods of recovery to resume any function. I think that previous failures have taken place with both Nvidia and nouveau drivers.

For the latest testing, I switched to nouveau drivers before downloading and booting on the latest kernel. Therefore, all of the current debugging information involves no proprietary drivers. While this is unfortunate because it is not my normal setup, suspend (and hibernate, for that matter) still fails as usual, and I am too run down by this issue to spend more hours un-breaking my configuration after each test.

[Adam Colligan (adam-p)]

Please do let me know if there is anything further that I can do to move the bug off of "incomplete".

[penalvch (penalvch)]

Adam Colligan, please provide a direct URL to your upstream report so that it may be tracked.

[Adam Colligan (adam-p)]

Please see my post above as to why I could not provide a link.

I have gone to http://vger.kernel.org/majordomo-info.html and discovered that the list system filters messages over 100 000 characters.

By following the wiki instructions verbatim, my error report message is over 1 000 000 characters.

Please advise on how the report needs to be split or cut down in order to be both acceptably complete and small enough for the list.

[Adam Colligan (adam-p)]

I have now re-run the full reporting process on the latest kernel from today. That report is attached here. I have also truncated the report to get it under 100 000 characters and sent that to the mailing list. I will update here if it makes the list and therefore has a URL to which I can link

[Adam Colligan (adam-p)]

And here is the URL:

http://thread.gmane.org/gmane.linux.power-management.general/42208

[Adam Colligan (adam-p)]

I have removed the addition of Hibernate to the workaround description. Hibernate is also broken on this machine. I have not had time to create and manage the second bug report for Hibernate, however.

[Adam Colligan (adam-p)]

As there has been no mailing list activity on this bug since it appeared on 2014-01-21, would there be any use in cross-reporting it to the kernel bugzilla? Or would that still be redundant?

[penalvch (penalvch)]

Adam Colligan, before re-engaging upstream, it would be best to retest for this in Trusty, and if reproducible, the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc6-trusty/ .