hibernation is unreliable

Bug #604559 reported by Teo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have Ubuntu 10.04 installed.

When I hibernate (whether manually or automatically because of critically low battery), any of these three things can happen:

A) it hibernates succesfully, and then resumes succesfully at the next boot
B) It appears to hibernate succesfully, but then when you boot, it silently fails to resume, and it just boots as if it had been shut down. You loose your session and all your unsaved data.
C) It gets stuck _before_ it completes hibernation. It gets stuck at an empty black screen with a text cursor blinking at the upper-left corner, and stays there forever. You have to shut it down by holding the power button. Obviously it will fail to resume at the next boot.

This can cause data loss and should be considered critical.
May be related to #50437 but i can't tell. I didn't touch anything related to partitions.
I think there's more than one bug here. The resulting issue is that you just can't trust hibernation.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi matteo,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please 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 604559

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Teo (teo1978) wrote :

Hi,
I'm sorry I cannot provide all that information.

I am not a developer, I can't play around with the system with the risk of messing it up. I am just a user.

Is there a way I can upgrade to the development release you're talking about without reinstalling ubuntu from scratch???

And I don't know what an "upstream" kernel is.

I can only say that it happens almost EVERY TIME the system hibernatres automatically when the level of the battery is critically low.
Today it CRASHED while hibernating: I got a black screen with a lot of error messages (the word "stack" appeared) and it got stuck without powering off. When I rebooted it booted cleanly and obviously I lost all my unsaved data.

When I hibernate it manually, most of the times all works fine; but not always: sometimes it does fail.

I also notice that this bug is marked for expiration if no further activity occurs. Well it happens i cannot provide further information and tests, but I don't think it is a reason for closing the bug unless you are SURE it is fixed (in which case I'd like to know how to get the update that fixes it).

This is a very CRITICAL bug that can cause disastrous data destruction.

Revision history for this message
Teo (teo1978) wrote :

Once again:
- battery critically low
- it automatically started hibernating. No error messages nor sign of failure whatsoever except that:
- just before the power turned off automatically, the prompt for user password appeared, the same as when you suspend and resume, but i thought that may be normal
- then it powered off automatically.
- then when I powered it on again, it booted freshly as if it had never been hibernated. No error message.

URGENT: Is there any log I can look at so that I can post some useful information?

Revision history for this message
Teo (teo1978) wrote :

I think this is a duplicate of #577916

Revision history for this message
il-mixu (michelbugeja) wrote : Start earning the salary you deserve by obtaining the appropriate Unviersity Dergee. business start up

De tn gre oet e - ad ds van pk cem xhc ent

Ac wc ade sm mic Qu ji alifi ajb cati asy ons available from prestigious
Non-Ac xwa cre rg dit czh ed Un sj ive xe rsi qem ties

Do you have the kn tau owl rro edge and the experience but lack the qua uf lifica bxi tio wb ns?

Are you getting turned down time and time again for the job of your
dreams because you just don't have the right letters after your name?

Get the pre kk sti ril ge that you deserve today!

Move ahead in your ca us re pma er today!

Bache xv lors, Mast ab ers and Doct ef orate Degr oup ees available in y our field!

No exa ph minations! No cl ihb asses! No textbo kj oks!

Call to register and receive your qu kr alifi rz catio bk ns within days!

Leave a Mes zmx sage 24 ho ywk urs a day 7 da pug ys a we gxh ek!

+ 1 - 64 hc 6 - 5 ill 37 - 17 aiz 32

Co jvq nfid rm enti ko ali aw ty as aa su yn red!

Revision history for this message
penalvch (penalvch) wrote :

matteo sisti sette, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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.