Suspend does not work Sony VAIO VGN-NW11S/T

[Anton Kanishchev]

Suspend does not work.

1- I click suspend, it attempts to suspend and shuts off with the power button blinking-as it does normally when it suspended in windows.

2-however when it comes out of suspend it simply reboots- as in displays the vaio logo then goes to bootloader and then boots from HDD activity light on for 10-15 seconds and it eventually boots to login screen.

****************RARING UPDATE******************

Raring test 27 Dec 2012

In Raring environment the problem is fixed, however it appears that between 3.2.xx (12.04 current kernel ) and 3.5.6 there was also a kernel problem that caused this to happen. In 13.04 daily (i.e. 3.7.0.7 -generic at the time of writing ) the problem is fixed. However the issue remains with the flgrx driver, even on 3.7.0.7.

*************RARING- UPDATE- ENDS*****************************

Reverse mainline kernel version bisect revealed:
v3.5.6-quantal --> doesn't work
v3.5.7 & v3.5.7.1 experienced stability issues hence could not test them.
v3.5.7.2-quantal --> suspend works in this one.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.37
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: anton 1769 F.... pulseaudio
 /dev/snd/controlC0: anton 1769 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4a00000 irq 46'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d3a00,00100302 HDA:14f12c06,104d1700,00100000'
   Controls : 17
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd0030000 irq 48'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,104d3a00,00100100'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Sat May 5 13:03:39 2012
HibernationDevice: RESUME=UUID=84d193ac-adde-4162-a2ad-7513f1ff7004
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: Sony Corporation VGN-NW11S_T
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=f752714f-ab5b-4157-9a45-ca36a063d9ea ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic-pae N/A
 linux-backports-modules-3.2.0-24-generic-pae N/A
 linux-firmware 1.79
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0180Y4
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.:bvrR0180Y4:bd08/27/2009:svnSonyCorporation:pnVGN-NW11S_T:pvrC601PLF4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NW11S_T
dmi.product.version: C601PLF4
dmi.sys.vendor: Sony Corporation

[Richard Elkins (texadactyl)]

This might be related to Bug #990305. The symptoms there are also observed while resuming from suspend. The difference in symptoms might be attributable to the differences in hardware.

[Anton Kanishchev (ak12-deactivatedaccount)]

Have recently tried the same approach on another laptop-old compaq t2500 1gb ram--suspend works 100 percent under all conditions (lid close ,button, with programs open, no programs open-all works) . The only difference apart from hardware is that it does not have any proprietary drivers installed. Have recently uninstalled my graphics drivers on the first affected system(sony laptop) but problem still persists. My best guess is the fact that the system suspends fine-it keeps the ram active and refreshed. My thoughs are that it does not know whether ram is active at startup therefore boots as if from shutdown. Is there any .conf file that I can edit to test whether this is the case???

P.S. are these bugs forwarded to the developer/programmer team in any way, or do we have to do it ourselves?

[penalvch (penalvch)]

Anton Kanishchev, thank you for reporting this and helping make Ubuntu better. Could you please provide all information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, if you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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'.

Please let us know your results. Thanks in advance.

[Anton Kanishchev (ak12-deactivatedaccount)]

Have just tested linux kernel linux-image-3.4.0-030400rc5-generic-pae_3.4.0-030400rc5.201205011817_i386.deb
This has not improved anything. Therefore reverting back to 3.2.24 kernel

[penalvch (penalvch)]

Anton Kanishchev, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about the status. Thanks in advance.

[Anton Kanishchev (ak12-deactivatedaccount)]

I am currently registering at
https://bugzilla.kernel.org/createaccount.cgi

will post back the link to the upstream bug

[Anton Kanishchev (ak12-deactivatedaccount)]

Have registered and submitted bug :;

Bug 43220

https://bugzilla.kernel.org/show_bug.cgi?id=43220

[penalvch (penalvch)]

Anton Kanishchev, thank you for your comments. Please answer the following questions:

1) Did suspend work for you in a release prior to Precise? If so, which?

2) As well, could you please test the latest upstream kernel available (v3.7-rc2-raring) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory 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.7-rc2-raring

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

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Anton Kanishchev (ak12-deactivatedaccount)]

I have just tested the 3.7rc-8 build (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc8-raring/) and everything seems to work. I can suspend (and resume) as normal. Seems like the bug is fixed. I assume I dont need to test -v3.7-rc2-raring kernel?

[penalvch (penalvch)]

Anton Kanishchev, thank you for testing the mainline kernel. The next step would be to identify the last mainline kernel release that the problem is demonstrated in, followed consecutively in version by the first mainline kernel release that fixes this problem (reverse mainline kernel version bisect). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Anton Kanishchev (ak12-deactivatedaccount)]

If I understood correctly I know that the problem is present in linux-image-3.4.0-030400rc5-generic-pae , and it is fixed in 3.7-rc8.
Hence I need to test ,3.6 to see whether my problem is solved?, then try every rc of that kernel to find where my problem was fixed, correct?, if it isnt solved try 3.7,3.5 etc? Or am I oversimplifying/complicating things?

[Anton Kanishchev (ak12-deactivatedaccount)]

Missed out question 1) completely, the last time suspend worked was in 11.04,then I clean installed 12.04 (kernel 3.2.0.23 IIRC) and thats when all the problems started.

[penalvch (penalvch)]

Anton Kanishchev, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995052/comments/17 :
>"If I understood correctly I know that the problem is present in linux-image-3.4.0-030400rc5-generic-pae , and it is fixed in 3.7-rc8.
Hence I need to test ,3.6 to see whether my problem is solved?, then try every rc of that kernel to find where my problem was fixed, correct?, if it isnt solved try 3.7,3.5 etc?"

Yes please.

[Anton Kanishchev (ak12-deactivatedaccount)]

I have tested the following
currently on 3.2.0-34-generic-pae, problem still there.

v3.4-rc7-precise/ -->problem still there.

v3.5.6-quantal/ --> doesnt work

v3.5.7.2-quantal/ --> problem fixed., suspend works in this one.

Since v3.7-rc8-raring/ worked i dont need to test between 3.5.7.2 and 3.7.xxx, is that correct?

[Anton Kanishchev (ak12-deactivatedaccount)]

RE: comment #20

have tested v3.5.7, and v3.5.7.1 kernels, but experienced stability issues hence could not test them.

[penalvch (penalvch)]

Anton Kanishchev, could you please test for this in a Raring environment via http://cdimage.ubuntu.com/daily-live/current/ and comment to the results?

[Anton Kanishchev (ak12-deactivatedaccount)]

UPDATE 27 th DEC
**************************
Re: Raring environment test.

steps that I have done:

1- load image to usb stick and boot.

2- when prompted click try ubuntu

3- click suspend when desktop loads up.

Should have suspended normally ( i.e. when using 3.5.7.2). Exact same problem. It suspends, light is flashing, telling me that it suspended. Pressing a key wakes up the machine, but it does not resume as expected (straight to login screen) but POST's , displays vaio logo etc. After a few seconds boot manager is displayed( since this test was with live usb only).

I have tried the live environment to confirm whether it is a possible conflict when ubuntu is not the only OS that is installed.
( see below for more info.)

*****************************
Installing 13.04

Have installed 13.04 raring onto a 10gb partition on my hdd.

1-for completeness my boot manager is set up as follows. If the computer is booted from cold, it displays the truecrypt boot manager ( along the lines of http://www.dsl.sk/images/articles/2008-02-07-truecrypt-8.png ).

2- press esc and boot linux. Testing the live cd confirmed that this suspend problem is probably not due to a dual boot configuration.

Once 13.04 is installed, (and updated) the problem persists ONLY if the proprietary flgrx drivers are installed. Leaving the system with open source radeon drivers does not trigger the problem. However this does not explain why the live usb option fails to work, as no flgrx drivers are loaded as far as i am aware.
 ********************

Based on my findings It has become apparent that i should retest the kernel-bisect kernels, with both flgrx and open source.

Have retested the kernels (the originals that were installed and not deleted for the initial kernel-bisect ) first with radeon open source driver and afterwards proprietary driver.

Here are the conclusions

v3.4-rc7-precise Using radeon or proprietary --- problem still there

v3.5.6-quantal/ --> same as above, however if using radeon driver the problem is extremely rare ( less than 1 in 100 cases, resumes normally). This was tested in a variety of configurations, programs open or not, video running (i.e. radeon driver used heavily), different devices connected to usb, hdmi, vga etc.

v3.5.7.2-quantal/ --> problem fixed. However installing flgrx driver reintroduces the problem. using the radeon open source driver and repeating for multiple configurations does not reintroduce the problem(have tried for about 30 min of suspend resume cycle, has not failed once).

********************
Raring test 27 Dec 2012
Conclusion

In Raring environment the problem is fixed, however it appears that between 3.2.xx (12.04 current kernel ) and 3.5.6 there was also a kernel problem that caused this to happen. In 13.04 daily (i.e. 3.7.0.7 -generic at the time of writing ) the problem is fixed. However the issue remains with the flgrx driver, even on 3.7.0.7.

[penalvch (penalvch)]

Anton Kanishchev, please answer the following questions:
+ Just to clarify your update, you can suspend in Raring while using the Radeon drivers, but not fglrx correct? If so, if you change the fglrx drivers from fglrx to fglrx-updates, does this change anything?
+ In Precise, if you purge the fglrx driver, and only use the radeon one, can you suspend?
+ Were you able to suspend while using the fglrx drivers in a release prior to Precise?

[Anton Kanishchev (ak12-deactivatedaccount)]

Prior to precise I could suspend using s2ram on 11.10, with fglrx drivers .

 I can not suspend on 12.04 with current kernel (3.2.035),
I am now running on radeon drivers (i.e. purged flgrx) on 12.04, the problem is the same.

In Raring, with latest drivers (for my system amd catalyst 12.6 ), the problem persists. this is using the latest drivers from the website. Suspend works with radeon drivers. I am unable to install the flgrx-updates from additional drivers menu as installation always fails. Hence I resorted to installing the latest drivers from amd's website.

[penalvch (penalvch)]

Anton Kanishchev, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995052/comments/25 :
>"Prior to precise I could suspend using s2ram on 11.10, with fglrx drivers ."

This is the fglrx drivers provided by the Ubuntu repositories correct? If so, which one(s)?

>"I can not suspend on 12.04 with current kernel (3.2.035), I am now running on radeon drivers (i.e. purged flgrx) on 12.04, the problem is the same."

Ok.

>"In Raring, with latest drivers (for my system amd catalyst 12.6 ), the problem persists. this is using the latest drivers from the website."

Thank you for providing results of testing the upstream driver. Could you please provide a direct URL for the upstream driver you are using?

As well, just to be clear, Ubuntu does not provide support for upstream drivers downloaded from AMD's website.

>"Suspend works with radeon drivers. I am unable to install the flgrx-updates from additional drivers menu as installation always fails. Hence I resorted to installing the latest drivers from amd's website."

Ok. In Precise, with the fglrx drivers provided by the Ubuntu repository https://launchpad.net/ubuntu/+source/fglrx-installer could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Anton Kanishchev (ak12-deactivatedaccount)]

Christopher , Yes that is correct ,in 11.10 the drivers were installed via the repositories ( via additional drivers tool in 11.10).

Sure, here is the link to the driver http://support.amd.com/us/gpudownload/linux/legacy/Pages/legacy-radeon_linux.aspx

This is the most up to date driver that works with my card. Note that I downgraded x.org to 1.12(in 13.04 only ) to make it work(known issue due to amd driver ).

I will test the https://wiki.ubuntu.com/DebuggingKernelSuspend and post the results in a couple of days.

[Anton Kanishchev (ak12-deactivatedaccount)]

I have followed https://wiki.ubuntu.com/DebuggingKernelSuspend . Looked through the log, no "hash matches" or anything. Uploading output here (dmesg.txt)

[penalvch (penalvch)]

Anton Kanishchev, as per https://wiki.ubuntu.com/DebuggingKernelSuspend :
3. While booted into the newest mainline kernel, please attach to your report:
cat /proc/acpi/wakeup > wakeup

[Anton Kanishchev (ak12-deactivatedaccount)]

 Here is the output from acpi/wakeup

[penalvch (penalvch)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because as you noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995052/comments/25 the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure