failure to resume from s3 suspend on sony vaio fs315-s

[jrb114]

Fresh install of feisty.

To reproduce:

Log in to gnome, choose power, suspend. System goes to sleep (s3) fine.
Press power button to wake up.

Expected result:
System restores itself fine

Actual result:
System fails to bring up gnome, or any other tty, it's just blank.
The memory stick led lights up, and the lights on my usb hub also light up. But caps lock fails to turn on the led on the laptop indicating it is activated. This is with the nv driver.

With the nvidia driver, the memory stick light fails to turn on, and the lights on the usb hub also don't light up, this may be a separate bug.

I've tried many, many work arounds, including acpi_sleep=s3_bios and acpi_sleep=s3_mode.

This is a regression from dapper. On dapper, to get s3 to work with nvidia and nv, I had to set

USE_DPMS=false
and stop the bluetooth service in /etc/defaults/acpi-support

s3 sleep also did not work in edgy.

I will attach dmesg, lspci -vn lspci -vvn and kern.log.0. If required, I can attach these from dapper, I don't know if that will help.

This bug sounds similar

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86099

except the computer does not reboot itself on "resume", it just sits with the fans running at full speed and the blank screen with the unresponsive keyboard etc.

[jrb114 (j-r-blake)]

Output from dmesg on the vaio fs315-s

[jrb114 (j-r-blake)]

output from lspci -vn

[jrb114 (j-r-blake)]

lspci -vvn on the fs315-s

[jrb114 (j-r-blake)]

kern.log.0 from a failed attempt to resume on the fs315-s with the nv driver.

[unggnu (unggnu)]

Maybe this https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend could help you with the binary nvidia driver. Since Feisty suspend works fine for me with my Sony TX2.

[bengibbs (benjgibbs)]

I am experiencing similar problems on a vaio VGN-FE11H. I have just tried Enola Gay's fix, alas to no avail.

My symptons are similar. Suspending or hibernating seems to work in as much as it powers down. Resuming does not go so well. X only partially returns, the scren remains black except for a square area around the mouse cursor, which is just displays broken artifacts. Opening a different terminal and killing X allows the gnome to come back normally, though my network connection is lost and no amount of modprobe-ing or ifup/down-ing will revive it.

I have attached a lsmod, dmesg and /var/log/messages from around the time of hibernate.

==================================================================
lsmod
==================================================================

Module Size Used by
nls_iso8859_1 5120 1
nls_cp437 6784 1
vfat 14208 1
fat 53916 1 vfat
usb_storage 72256 1
libusual 17936 1 usb_storage
battery 10756 0
ac 6020 0
thermal 14856 0
fan 5636 0
button 8720 0
ipw3945 118816 1
ieee80211 34760 1 ipw3945
e100 36232 0
mii 6528 1 e100
binfmt_misc 12680 1
rfcomm 40856 0
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
sonypi 23196 0
ppdev 10116 0
acpi_cpufreq 10056 0
cpufreq_powersave 2688 0
cpufreq_ondemand 9228 2
cpufreq_stats 7360 0
freq_table 5792 3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats
cpufreq_userspace 5408 0
cpufreq_conservative 8200 0
tc1100_wmi 8068 0
sony_acpi 6284 0
pcc_acpi 13184 0
dev_acpi 12292 0
ipv6 268704 10
sbs 15652 0
container 5248 0
dock 10268 0
i2c_ec 5888 1 sbs
asus_acpi 17308 0
video 16388 0
backlight 7040 1 asus_acpi
arc4 2944 0
ecb 4480 0
blkcipher 6784 1 ecb
ieee80211_crypt_wep 6144 0
nls_utf8 3072 3
ntfs 107764 3
eeprom 8336 0
i2c_i801 9356 0
sbp2 23812 0
parport_pc 36388 0
lp 12452 0
parport 36936 3 ppdev,parport_pc,lp
fuse 46612 0
snd_hda_intel 21912 1
snd_hda_codec 205440 1 snd_hda_intel
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
pcmcia 39212 0
joydev 10816 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_mi...

[jrb114 (j-r-blake)]

Hi,

Without my having done anything different (i.e. before even installing the backported hal library) I've randomed left the laptop for a long time whilst attempting to resume (something like longer than 5 mins). And it works, although the system seems to be pretty slow, by that a top shows sys and wait are using a lot of power (up to 90%).

Anyway, the point is that it does resume. I tried, twice, and here are my dmesg outputs in the attachment. There certainly seems to be a bug in nvidia...

[Xavier Verne (xavier-verne)]

I confirm this bug on Sony VAIO VGN-FE11H with exactly the same symptoms.

With suspend to RAM, on resume it would just display the cursor after waking X-server up. See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/110102/comments/6

for details.

Looks like a regression, AFAIK It was working on Dapper Drake.

[Philipp Höhn (philipp-philipp-hoehn)]

Same bug here on a ASUS W2JC with an ATI graphics card. Bug report can be found here: https://bugs.launchpad.net/ubuntu/+bug/130844

[jrb114 (j-r-blake)]

In gutsy now, uname -a give 2.6.22-10-generic.

By default, resume doesn't work, _but_ doing these hacks to /etc/default/acpi-support made it work, with some caveats.

== CODE ==
# Should we save and restore state using the VESA BIOS Extensions?
toggle SAVE_VBE_STATE=false to true

# Should we attempt to warm-boot the video hardware on resume?
toggle to POST_VIDEO=false true

# Should we switch the screen off with DPMS on suspend?
toggle to USE_DPMS=false true

# Uncomment the next line to switch away from X and back again after resume.
# This is needed for some hardware, but should be unnecessary on most.
toggle DOUBLE_CONSOLE_SWITCH=false to true

== end code ==

seems to work, sort of. I have to Ctrl+Alt+F1 to tty1 and back again to get X to resume. This seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/50031

[jrb114 (j-r-blake)]

Some more information. Ahem.

I also forgot to mention that I added nvidia to the top of /etc/modules as recommended here: https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend

I've tried sleeping and resuming everytime with the alternate options to previously, and it worked every time, except for Ctrl+Alt+F1 and back to X. (Funny that the DOUBLE_CONSOLE_SWITCH doesn't seem to work. Although it definitely does something, when I didn't do it I had the garbage on the screen until I went to tty1 and back again.) More news on removing nvidia from /etc/modules to follow very soon.

[jrb114 (j-r-blake)]

Well I've just tried removing (technically commenting, is this different?) nvidia from /etc/modules, rebooted, suspended, and it resumed (via tty1 and back again).

So what is causing the problem? I've just tried with my usb hard drive plugged in and turned on, no problems. I am using wired ethernet, but the wifi is turned on if not connected.

Why it has suddenly started working when it didn't work previously I have no idea. Shame I can't trace down the root cause.

[unggnu (unggnu)]

Could you please recheck it with Ubuntu Gutsy Gibbon 7.10. Maybe with the live CD and of course the free nv driver. The proprietary has some suspend problems which could be often fixed with some X options. This is documented in the Wiki.

[bengibbs (benjgibbs)]

Rechecked witha live CD ubuntu-7.10-desktop-i386 on aforementioned vaio fe11h - same behaviour I'm afraid.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[bengibbs (benjgibbs)]

2.6.27-4-generic using 8.10 alpha 5 Suspending and (more importantly) resuming seems to work most of the time. It has failed for me a couple of times. If it does it again I'll attach logs. What would be helpful?

[Leann Ogasawara (leannogasawara)]

Hi bengibbs,

The following links describe some useful debugging information to provide:

https://wiki.ubuntu.com/KernelTeamBugPolicies
https://wiki.ubuntu.com/DebuggingKernelSuspend

[Leann Ogasawara (leannogasawara)]

Hi bengibbs,

Have you been able to test Intrepid's final release? Did you see any improvements? Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

-JFo