[Dell XPS M1530 / Nvidia GeForce 8600M] suspend/resume problem [non-free nvidia]

Bug #324031 reported by Rocko
38
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Apport picked this up. The computer had failed to resume from suspend (USB lights off, blank screen) and had to be hard-reset.

ProblemType: KernelOops
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
FlagFile: suspend
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
OopsText: Suspend/Resume or hibernate problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-6-generic 2.6.28-6.17
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=64bcbd04-2786-4a89-8276-6e7974db59b1 ro quiet splash User Namefstype=ext4 i8042.nomux
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-6.17-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups:

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

Hi Rocko,

I notice you have an Nvidia graphics card. This may be a duplicate of bug 322657 so you should likely monitor that bug as well. Thanks.

Revision history for this message
Andy Whitcroft (apw) wrote : Re: [Dell XPS M1530 / Nvidia GeForce 8600M] suspend/resume problem

 Is this reproducible say over 10 cycles. Has suspend ever worked in the past, if so which kernel release (cat /proc/version_signature)? Please include any information as to the circumstances leading up to this failure, for example did your battery run out? If this is reproducible it is worth trying the moving to VT-1, press ctrl-alt-F1, login, and run pm-suspend. This may give us more information.

Changed in linux:
status: New → Incomplete
Revision history for this message
Rocko (rockorequin) wrote :

I suspend/resume often. It _usually_ works. In Hardy, it was close to 100% reliable; in Intrepid, it usually worked, but sometimes I had to hard-reboot after resume (ie with the blank screen). In Jaunty it has been fairly reliable but occasionally the kernel crashes and I have to hard reboot. This morning after I resumed X restarted (ie I had to log in again after resume and I lost the apps that were running when I suspended) - but this is the first time I've seen that.

I have put SUSPEND_MODULES="nvidia" in the file /etc/pm/config.d/modules in case that is relevant. In the past, nvidia recommended this.

It's nothing to do with the battery running out - I just select suspend from the System / Shut Down menu option and then restart the PC at some point later.

On the occasions where it crashes after resume, I can't select VT-1 or even ssh from another machine.

The only other observation I have is that the crashes usually (but not always) happen after I've physically moved the laptop between my home office and the work office. This usually means I've suspended, then unplugged the external monitor I have at home, then resumed in the office without it plugged in. Or vice versa.

Revision history for this message
Andy Whitcroft (apw) wrote :

It would cirtainly be worth testing with removing the external monitor and telling X that is it has gone before suspending for a few times to see if we can confirm that is the trigger.

Changed in linux:
status: Incomplete → In Progress
status: In Progress → Incomplete
Revision history for this message
Rocko (rockorequin) wrote :

The problem is that Jaunty is behaving itself pretty well these days - better than Intrepid, so I'm having trouble reproducing the error consistently, which makes it hard to figure out the trigger.

It could also be something to do with hal - when I move from home to the office, I unplug a set of external drives. I've noticed that sometimes Jaunty thinks they're mounted upon resume (though they aren't plugged in anymore) and as well, Jaunty doesn't always shut down properly, and I wonder if that's something to do with it being unable to properly unmount the drives.

Revision history for this message
Rzulf (rzulfeek) wrote :

Same problem. I also have second monitor at home and it usually fails to resume when I am at university. From what I experienced Ubuntu fails to resume if I change X configuration through nvidia-settings disabling the second display then suspend and resume it while it is running on battery. The screen is totally black without even any backlight. Nothing work so I have to hard reboot it.

I am using iterpid right now and it happens quite often. On hardy resume was almost 100% successful :)

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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