[LENOVO 64606YG] intermittent suspend/resume failure [non-free: nvidia]

[Jon Eliot]

Intermittent error. Suspend and hibernate has appeared to work, but the system failed to resume the last time from suspend, booting instead and flashing a "serious kernel problem" message after login.
The system had been hibernated once and suspended several times since last boot. Wakeup from the earlier hibernation was a bit odd, taking a long time even before the disk indicator was turned on, producing peculiar screen images. The system was suspended while on battery, and resumed in a docking station.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 64606YG
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=84418c90-5b1e-4714-a6b4-5c862db9aa85 ro quiet splash
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: [LENOVO 64606YG] suspend/resume failure [non-free: nvidia]
UserGroups:

[Steve Conklin (sconklin)]

A lot of the reported bugs with suspend/resume have been fixed since this report.

Are you still experiencing the problem with the latest release? If so then we can continue to troubleshoot this.
If not, we can close the bug.

Thanks!

[Jon Eliot (jon-stromme)]

There have been apparent and welcome improvements, but yes, there still
are problems.
Changed to kernel 2.6.30-10 today, so I will add an update in about a
week on how things are going with a real workload on that kernel.

The procedure to provoke a freeze in either suspend or resume from suspend:

1) Use the machine with an external monitor (I normally use
    SubSection "Display"
        Virtual 3840 1200
    EndSubSection
    in xorg.conf, but it does not seem to matter what is in there for
this bug)

2) Suspend the machine and take it out of the docking station (Optional:
go home after work ;-).)

3) Resume the machine as a standalone laptop. Change the display to 1920
1200.

4) Suspend the machine. (Optional: go back to work the next morning.)

5) Resume the machine in the docking station. Change the display to 3840
1200.

6) Repeat steps 2-5 a small number of times.

The number of repeats used to be less than 1, ie. the first resume or
the second suspend in the docking station normally failed, or even the
first resume at home. Now the number of successful repeats is typically
something like 5, which means normally one week at a time without any
trouble (at least after I changed the GdmXserverTimeout to 20).

Do I have the last version:

$ uname -a
Linux vora.uninett.no 2.6.30-10-generic #12-Ubuntu SMP Fri Jun 26
00:29:02 UTC 2009 x86_64 GNU/Linux

Repository:
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main

$ dpkg -l | grep nvidia | grep 180
ii nvidia-180-kernel-source
185.18.14-0ubuntu1~xup~1~jaunty
NVIDIA binary kernel module source
ii nvidia-180-libvdpau
185.18.14-0ubuntu1~xup~1~jaunty
Video Decode and Presentation API for Unix
ii nvidia-180-libvdpau-dev
185.18.14-0ubuntu1~xup~1~jaunty
Video Decode and Presentation API for Unix development files
ii nvidia-180-modaliases
185.18.14-0ubuntu1~xup~1~jaunty
Modaliases for the NVIDIA binary X.Org driver
ii nvidia-glx-180
185.18.14-0ubuntu1~xup~1~jaunty
NVIDIA binary Xorg driver
ii nvidia-glx-180-dev
185.18.14-0ubuntu1~xup~1~jaunty
NVIDIA binary Xorg driver development files
ii nvidia-settings
180.25-0ubuntu1
Tool of configuring the NVIDIA graphics driver

Thanks for all the good work! To get from an unbearable situation to a
reasonably good situation is fine, anything more will be a bonus.

Rgds, Jon Eliot

Steve Conklin wrote:
> A lot of the reported bugs with suspend/resume have been fixed since
> this report.
>
> Are you still experiencing the problem with the latest release? If so then we can continue to troubleshoot this.
> If not, we can close the bug.
>
> Thanks!
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided...

[Jon Eliot (jon-stromme)]

There are still infrequent crashes, about once every week, typically a
failure to suspend completely, suspend light blinks. But the automatic
crash report fails, i.e. it seems to refuse to recognize the 30-10
kernel as a genuine Ubuntu package.

I will be happy to send a report with the relevant dumps, if someone can
point me to doc on how to do it manually.

Rgds

Jon Eliot wrote:
> There have been apparent and welcome improvements, but yes, there still
> are problems.
> Changed to kernel 2.6.30-10 today, so I will add an update in about a
> week on how things are going with a real workload on that kernel.
>
> The procedure to provoke a freeze in either suspend or resume from
> suspend:
>
> 1) Use the machine with an external monitor (I normally use
> SubSection "Display"
> Virtual 3840 1200
> EndSubSection
> in xorg.conf, but it does not seem to matter what is in there for
> this bug)
>
> 2) Suspend the machine and take it out of the docking station (Optional:
> go home after work ;-).)
>
> 3) Resume the machine as a standalone laptop. Change the display to 1920
> 1200.
>
> 4) Suspend the machine. (Optional: go back to work the next morning.)
>
> 5) Resume the machine in the docking station. Change the display to 3840
> 1200.
>
> 6) Repeat steps 2-5 a small number of times.
>
> The number of repeats used to be less than 1, ie. the first resume or
> the second suspend in the docking station normally failed, or even the
> first resume at home. Now the number of successful repeats is typically
> something like 5, which means normally one week at a time without any
> trouble (at least after I changed the GdmXserverTimeout to 20).
>
> Do I have the last version:
>
> $ uname -a
> Linux vora.uninett.no 2.6.30-10-generic #12-Ubuntu SMP Fri Jun 26
> 00:29:02 UTC 2009 x86_64 GNU/Linux
>
> Repository:
> deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main
> deb-src http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main
>
> $ dpkg -l | grep nvidia | grep 180
> ii nvidia-180-kernel-source
> 185.18.14-0ubuntu1~xup~1~jaunty
> NVIDIA binary kernel module source
> ii nvidia-180-libvdpau
> 185.18.14-0ubuntu1~xup~1~jaunty
> Video Decode and Presentation API for Unix
> ii nvidia-180-libvdpau-dev
> 185.18.14-0ubuntu1~xup~1~jaunty
> Video Decode and Presentation API for Unix development files
> ii nvidia-180-modaliases
> 185.18.14-0ubuntu1~xup~1~jaunty
> Modaliases for the NVIDIA binary X.Org driver
> ii nvidia-glx-180
> 185.18.14-0ubuntu1~xup~1~jaunty
> NVIDIA binary Xorg driver
> ii nvidia-glx-180-dev
> 185.18.14-0ubuntu1~xup~1~jaunty
> NVIDIA binary Xorg driver development files
> ii nvidia-settings
> 180.25-0ubuntu1
> Tool of configuring the NV...

[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.