hibernate/resume failure [non-free: nvidia]

[Daniel Hahler]

Similar to bug 348200 (also reported by me), but now on Karmic (and not Jaunty).
I cannot say however until now, if hibernation would normally work for me - IIRC this was the first time I've tried it after upgrading.

Hibernation has taken more than ~5 minutes and I was in a hurry, therefore I've rebooted - maybe it would have worked out, after some more minutes.

However, then the bug would be unusual long duration of the wakeup process.

ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
Architecture: i386
Date: Wed May 20 12:01:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 1a7c:0068
 Bus 002 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NonfreeKernelModules: nvidia
Package: linux-image-2.6.30-5-generic 2.6.30-5.6
ProcCmdLine: root=UUID=73d091ef-8ee9-4ad2-9243-1ece878c1024 resume=/dev/fastrcvg/swaplv ro acpi_use_timer_override usbcore.autosuspend=1 splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.30-5.6-generic
RelatedPackageVersions: linux-backports-modules-2.6.30-5-generic N/A
SourcePackage: linux
Tags: resume hibernate
Title: hibernate/resume failure [non-free: nvidia]
Uname: Linux 2.6.30-5-generic i686
UserGroups:

dmi.bios.date: 03/08/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9c
dmi.board.name: NF-CK804
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9c:bd03/08/2007:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnNF-CK804:rvrx.x:cvn:ct3:cvr:

[Paul Price (price-ifa)]

I have this problem too on my Dell Inspiron 1501 laptop. It is present in Karmic, and not in Jaunty.

I am not using nvidia drivers:

01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]

I'm happy to provide further information as requested.

[Paul Price (price-ifa)]

Working through the DebuggingKernelSuspendHibernate sequence:

Is this really a failure? Yes: machine was connected to AC power all the way through hibernate and resume. There is no reason to suspect a machine problem.

Is this a repetition of a previous failure? Not that I know of.

Did the machine break while going to sleep or waking up? While waking up. The machine happily boots, displays a blank screen with glowing white Ubuntu logo, then blanks and nothing happens.

Is it reproducible? Yes, though I think I can remember once when it resumed fine, yet the problem occurs more than half (probably > 80%) of the time.

Did it work before? Hibernate/resume worked in Ubuntu 9.04 Jaunty. It failed after I upgraded to Karmic.

Do you end up with flashing caps-lock or similar? I have not noticed, but I haven't looked for it. I will look for it next time.

[Jeremy Foshee (jeremyfoshee)]

Hi Daniel,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 378683

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[Paul Price (price-ifa)]

Hi Jeremy.

Thanks for getting back to us (even if automated). I've just checked, and this problem still remains, with the same symptoms as before. I'd prefer not to have to upgrade my machine to a development version. Can I get back easily and safely, or, better yet, install it in parallel with Karmic? I tried the mainline kernel and got an OOPS within a couple of seconds.

Thanks,

Paul.

[Jeremy Foshee (jeremyfoshee)]

Hi Paul,
     Thank you for the update. My apologies for the automated update of the case. There are simply too many bugs to work through without it. I'm not sure, but there may be a way for you to test with the daily liveCD. Let me look around a bit and see if I can find anything that makes sense to test with.

Thanks!

~JFo

[Daniel Hahler (blueyed)]

Update from me (reporter): I'm using the "nv" driver currently and could successfully hibernate and resume (although it took so long that I've pressed Alt-SysRq-I which displayed me some 93% output and I've kept waiting).
This took probably ~5 minutes.
I have not tried hibernation with nvidia recently, but have put it on my list (at least nvidia appears to work, where nouveau started to fail recently).

[Daniel Hahler (blueyed)]

Setting back to Triaged: the requested information has been provided.

I've just reported bug 569122 though, with more information about the current state of failure for me (using nvidia-current or nouveau).

Please feel free to mark as duplicate as you see fit.

[Daniel Hahler (blueyed)]

Closing as Fixed, since it is for me in Lucid.

Although it takes far too long (as far as I can see), it came back up without any problems (using nvidia-current).

Paul, if you still experience problems in this regard, please file a new bug (using "ubuntu-bug linux"). Thanks.