[Dell Inc. Precision M6400] suspend/resume failure [non-free: nvidia]

[Cycle]

Description: Ubuntu jaunty (development branch)
Release: 9.04

expected a 'clean' resume

happened a 'normal' boot, crash icon visible in the upper panel, which guided me until here :)

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: Dell Inc. Precision M6400
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-9-generic 2.6.28-9.31
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=f8b46d61-e3f2-4a85-8420-3da91cd91b51 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-9.31-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Dell Inc. Precision M6400] suspend/resume failure [non-free: nvidia]
UserGroups:

[Leann Ogasawara (leannogasawara)]

Hi Cycle,

Is this reproducible every time, or say over 10 cycles. Has suspend ever worked in the past, if so which kernel release (cat /proc/version_signature)? If you could also please include any information as to the circumstances leading up to this failure, for example did your battery run out? Did the machine lock up, did any messages come out? If it is reproducible could you try to suspend from VT1, press ctrl-alt-F1, login, and run pm-suspend there. If you could test and report back here that would be helpful. Thanks in advance.

[Cycle (cycle-cyclesoft)]

Hi Leann,
sorry for the late reply (and for the bad english), I made a little bit
testing.....
So far I was not able to reproduce the problem. I tried different
situations such suspending with and without the battery inserted (an
usual situation for me), hybernating with the battery and resuming
without and vice-versa, but always has worked as expected.

Instead I noticed another bug, not serious as the original, just a
little bit annoying:
if I Hybernate with the battery inserted, then resume WITHOUT the
battery, the upper left icon still is a battery, not the plug. The
tooltip correctly reports tha actual situation (running on AC....) just
the icon is wrong.

I will keep trying as the 9.04 release progresses through the
alpha/beta/RC stages, just to be sure.

Please don't exitate to ask me whenever test you need, also relatd to
other bugs.
I purchased this shining new Dell M6400 without windows, exactly to run
ubuntu 9.04, so I'm testing every thing to be sure to have the best
Ubuntu experience!

Thank you!!

Leann Ogasawara wrote:
> Hi Cycle,
>
> Is this reproducible every time, or say over 10 cycles. Has suspend ever
> worked in the past, if so which kernel release (cat
> /proc/version_signature)? If you could also please include any
> information as to the circumstances leading up to this failure, for
> example did your battery run out? Did the machine lock up, did any
> messages come out? If it is reproducible could you try to suspend from
> VT1, press ctrl-alt-F1, login, and run pm-suspend there. If you could
> test and report back here that would be helpful. Thanks in advance.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[Thomas Meixner (tom-meixner)]

I've just had the same problem on an Dell E6400 which is basically the same hardware so I post my additional info here:
I'm on Kubuntu 9.04:

uname -a
Linux lt2-tom 2.6.28-11-generic #36-Ubuntu SMP Fri Mar 20 19:51:24 UTC 2009x86_64 GNU/Linux

Usually sleep works just fine.
Unfortunately I haven't been able to reproduce the crash but here is what happened:

Watched some movies with VLC and changed power Profile from "Performance" to "Presentation".
Shut lid as usual but realized that under "Presentation" ubuntu doesn't go to sleep, it just switches of the screen.
Reopened lid, changed power profile back to performance and closed lid again.
Noticed that this time although the lid was closed the screen was still lit (light lit lit?), no sound as usual when sleep has been activated.
Waited about a minute and reopened the lid - Screen was lit but black, no message, no response to any keys so I did a hard reset.
Upon next boot I was greeted with the kernel error warning.

I hope this is helpful of any kind,

Thomas

[Cycle (cycle-cyclesoft)]

Hi, today I tried the test script:

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

The 1st part, that with manual intervention, was ok.
The 2nd one, the suspend/resume loop, was ok for some iteration (I was not in front of the PC, I can't be more precise sorry) but at some point, it suspended and never resumed.
Well, never means that after say 1 hour without resume, I thinked that something was wrong, and tried to manually resume.
It don't worked, the screeen was black but with little light.
I forced a shutdown pressing the power button for 4 seconds, end after booted normally.

Theare is some sort of log left around by the script I can send to you ?

[Cycle (cycle-cyclesoft)]

Found the log in /var/lib/pm-utils/stress.log

Here it is.

[Paolo Redaelli (paolo-redaelli)]

It also occour on a freshly upgraded Karmic Koala on

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]