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

Bug #347603 reported by Hugh Winkler
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I'm going to assume this problem isn't exactly like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/344184, and let you guys make the call.

Answering some questions I found there:

"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)?"

I have succeeded in resuming many times before upgrading from Intrepid to Jaunty yesterday. I also succeeded resuming once in Jaunty.

" If you could also please include any information as to the circumstances leading up to this failure, for example did your battery run out? "

No.

"Did the machine lock up, did any messages come out? "
On resume, my power button was lit, but my screen was not.

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

It's not 100% reproducible.

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 M2400
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.36
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=004d9658-e87f-4ebb-ae43-ed5bb3837543 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.36-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 M2400] suspend/resume failure [non-free: nvidia]
UserGroups:

Revision history for this message
Hugh Winkler (hughw) wrote :
Revision history for this message
Hugh Winkler (hughw) wrote :

I tried pm-suspend from VT1 as suggested... resumed with no problem.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for all the info Hugh. I know you mention it's not 100% reproducible. Can you give an estimate how many times the issue does pop up, say 1 out of 4? Might also be good to do a few more tests from VT1 just to see if it is reproducible there and hopefully any useful error logs might show up to the screen or either in dmesg. The following wiki might also be helpful - https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . I also see you have an nvidia graphics card which may or may not be an issue. I've just noticed quite a few bug reports which also have nvidia cards which leads me to this assumption. Thanks.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

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

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

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

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.