[Acer, inc. Aspire 4530] suspend/resume failure [non-free: nvidia]

[Asif Youssuff]

Starting to test the suspend/resume functionality, this is the first crash while using the

/usr/share/checkbox/scripts/suspend_test --full

script.

I'll be happy to provide more info to help fix this issue.

Description: Ubuntu jaunty (development branch)
Release: 9.04

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer, inc. Aspire 4530
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=174a75e7-79b8-415d-9b91-d8f326394e3a ro quiet splash quiet
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend
Title: [Acer, inc. Aspire 4530] suspend/resume failure [non-free: nvidia]
UserGroups:

[Asif Youssuff (yoasif)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Marc Kaplan (marc-kaplan)]

Duplicated......

[Leann Ogasawara (leannogasawara)]

I pointed @yoasif to the following wiki:

https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

[Asif Youssuff (yoasif)]

I rebooted using the no_console_suspend option in grub.

After initiating a pm-suspend in VT1, the computer appeared to suspend successfully. The power button/light blinked slowly with an amber color.

I attempted to resume the machine by pressing the power button.

It appeared to begin to resume, and I got the following messages:

ata2.00:revalidation failed (errno=-5)
ata1.00:revalidation failed (errno=-5)
ata2.00:revalidation failed (errno=-5)
ata1.00:revalidation failed (errno=-5)
...
this was in the original font -- not the new font (setfont) provided.

I got some more messages in the new font:

end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
end-request: I/O error, dev sda sector xxxxxxxx
... (entire screen fulls)
Ext4-fs error (device sda5):ext4_find_entry: reading directory #xxxxxx
Buffer I/O error on device sda6, logical block xxxxxx
JBD2: I/O error, dev sda detected when updating superblock for sda5:8

switching back to VT7 showed me the GDM screen, logging in did not work. went back to VT1, tried to reboot and got error:

sudo: unable to execute /sbin/reboot: input/output error

tried this a couple of times (3 times to be exact), had the same issues each time. i'll be happy to troubleshoot further if necessary.

[Bruno (luny-ymail)]

I can confirm this bug, I was having the same problem since 8.10 and it persisted into 9.04.

Fortunately, I found a workaround for it. If you use the kernel parameter pci=nomsi, you should stop getting those errors. Another parameter I'm using is i8042.reset, it fixes another problem where the keyboard sometimes isn't detected after a successful resume.

But after fixing this, another problem remains. The kernel included in 9.04 (2.6.28) has a suspend bug which causes the suspend behavior to be unreliable.

The default suspend method on 9.04 didn't work for me out of the box. I tried using only pm-suspend with uswsusp, and sometimes suspend would work, other times it would resume instantly. Suspecting the NVIDIA driver, I removed nvidia-glx-180 and installed 180.51, but I believe it's unrelated as the suspend still wouldn't work reliably, even when not loading the nvidia module.

I read somewhere kernel 2.6.29 fixed a suspend bug 2.6.28 had, so I installed it. After this, suspend works perfectly.

To sum it up, the combination that works for my Aspire 4530 is:
- Kernel 2.6.29-020629-generic (you can download the debs here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29/ )
- Kernel parameters pci=nomsi and i8042.reset
- Use SUSPEND_METHODS="pm-utils" on /etc/default/acpi-support
- Use SLEEP_MODULE="uswsusp" on /etc/pm/config.d/00sleep_module
- NVIDIA driver 180.51 (may be irrelevant to this issue; try nvidia-glx-180 from the repositories first)

It was hard getting suspend working, but it was worth it. Let me know how it goes for you.

[Dhanar Adi Dewandaru (dhanar-10)]

Bruno, I think your workaround is a bit overkill....

I am using Ubuntu 9.04 AMD64. These are the workaround I have found.

Workaround #1: using stock kernel 2.6.28
1. Use kernel parameter pci=nomsi. This will prevent sata to fail when resuming. I have read somewhere that currently linux kernel still having resume problem with sata and pci=msi.
2. Disable bluetooth before suspend using the bluetooth button. I believe a script can be made for this. Maybe 50bluetooth can be used as a base.

Workaround #2: using mainline kernel 2.6.29
1. Still need pci=nomsi.
2. No need to disable bluetooth. :)

Based on my observation, this problem has nothing to do with nvidia driver.

One more thing that bothers me is it will take some time for gnome desktop to return after resuming. Is there any workaround to make it faster?

[Asif Youssuff (yoasif)]

I tried adding the pci=nomsi kernel parameter and suspending, but now instead of suspending, it simply restarts Xorg. When logged back into GNOME, networking has been disabled.

I don't have Bluetooth on my machine, so I didn't bother trying to turn it off.

Also, I'm running jaunty-proposed updates.

Running 2.6.28-12-generic #43-Ubuntu

[Dhanar Adi Dewandaru (dhanar-10)]

Asif Youssuff,

First, I think we should compare our Aspire 4530 specification.

My Aspire 4530 specification is in here: http://www.acer.com.my/acer/product.do?link=oln85e.redirect&changedAlts=&CRC=600100215#wrAjaxHistory=0

Which one is yours?

Then, maybe we also need to compare BIOS version. I have some experience that different BIOS version may have different behaviour. It is with Aspire One though....

[Asif Youssuff (yoasif)]

Running

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

on

Linux ubuntu-asif 2.6.30-9-generic #10-Ubuntu SMP Fri Jun 12 13:05:04 UTC 2009 i686 GNU/Linux

Booting with pci=nomsi works to resume from suspend perfectly -- wireless works, the nvidia driver works -- compiz is enabled, etc.

Booting without pci=nomsi still results in not waking up the hard drive -- the machine seems to resume from suspend, but GNOME doesn't come back, and going to tty1 does not allow me to login.

[Asif Youssuff (yoasif)]

On

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

using

uname -a
Linux ubuntu-asif 2.6.31-3-generic #19-Ubuntu SMP Tue Jul 14 16:07:02 UTC 2009 x86_64 GNU/Linux

Hibernate continues to work without issues (other than not waking up wireless, but that is another bug). Suspend continues to work, but waking up still has issues.

Booting with pci=nomsi continues to work, however -- nvidia driver works, compiz works.

[elequeux (etienne-lequeux)]

Got similar problems (suspend works, resume fails with SATA errors) on ACER emachines g620

etienne@mubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

[elequeux (etienne-lequeux)]

Got similar problems (suspend works, resume fails with SATA errors) on ACER emachines g620, using kernel 'server' 32bits (this kernel since I need 32bitness and this laptop has 4G mem)

-> Using pci=nomsi solved resume issues

etienne@mubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

etienne@mubuntu:~$ uname -a
Linux mubuntu 2.6.28-13-server #45-Ubuntu SMP Tue Jun 30 20:51:10 UTC 2009 i686 GNU/Linux

[Robert Irelan (rirelan)]

I don't know how applicable this piece of advice is to this issue, because I am using Fedora 11 with the 2.6.29.6-217.2.16.fc11.x86_64 kernel (i.e. on a 64-bit install). In any case, I was trying to solve the occasional flickering that I was noticing and came across this site:
http://www.ubuntusolutions.org/2009/02/screen-flickering-with-nvidia-on-ubuntu.html
Specifically, the advice that proved useful was to add the following lines to /etc/modprobe.d/options (actually, any file in the /etc/modprobe.d/ directory; e.g. I used /etc/modprobe.d/nvidia):

options nvidia NVreg_RegistryDwords='PerfLevelSrc=0x2222'
options nvidia NVreg_Mobile=1

Apparently, the equivalents of these registry values from the Windows driver are not enabled by default in Fedora (and I suppose not in Ubuntu, either, because I have never been able to resume successfully from suspend in Ubuntu or Fedora until now). Perhaps pci=nomsi is also needed, although I haven't checked if that option is needed. For me, when both the modprobe lines and the kernel option are active, I can suspend and resume using the nvidia driver successfully, and access my disks as well, which I couldn't do before, even with the pci=nomsi kernel option. I'm just posting this here because it might help some of the reporters of this bug. I will do more experiments later.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.