Hibernation woes

Derek Broughton news at pointerstop.ca
Thu May 8 14:57:03 UTC 2008

Albert Charron wrote:

> Derek Broughton wrote:
>> Oh, so typical...  There _isn't_ a distribution problem.  There's a
>> problem with your configuration.
> Derek... can you explain how to configure this to work properly? 

Perhaps.  Understand, I accept there are systems that don't seem to be able
to hibernate/resume - but Ted's already claimed that he _did_ have it
working, so I'm certain his can be fixed.  Yours might be harder :-(

> I'm 
> following this thread since I have the exact same problem on both my
> laptops and my desktop.  

No, you have a problem.  I'd be really surprised if its the same one.

> Hibernate (Standby has the same problem 
> anyways) have never worked as expected on my hardware, with any Ubuntu
> releases (This works perfectly for me on Doze 

Windows hibernates in a completely different manner.  

> and on at least one other 
> Linux distribution). The machine goes to standby or hibernates yes, but
> there's no way to make the machine usable at the wakeup... most of the
> time, the only thing I can do is to press and hold the power button to
> reset the machine. Some times, I manage to go to cli and do a proper
> reboot...

Forget "standby" for the moment (and I hope you mean "suspend to RAM" rather
than "sleep" - sleep is an entirely different mechanism).  It's possible
that sleep or suspend could merely be turning off your video and failing to
reset it, so that when you resume you can't (apparently) do anything. 
Going right to shutdown would help diagnose that.

So hibernate your machine.

Then power up again, and boot to single user mode (best to use the "quiet"
option or you'll see a lot more than I mention below).  Pay close attention
to the console.  If resume is successful, you won't actually get to
single-user mode, because it boots the original image, but this method lets
you see messages normally hidden by the splash screen.

You should see (copied by hand from my console, so excuse errors - the UUID
and DEVICE words are actual device identifiers on your system):
 Starting up ...
 Loading, please wait...
 kinit: name_to_dev_t(/dev/disk/by_uuid/UUID) = DEVICE
 kinit: trying to resume from /dev/disk/by_uuid/UUID

If it then says:
 kinit: No resume image, doing normal boot...

either (a) it hasn't created a hibernate image (seems unlikely - because it
shouldn't have shut down); (b) DEVICE is not identified correctly; (c) your
swap partition doesn't have the UUID shown.

otoh, if it says it's resuming from that image, it would seem resume really
is working - and if you then lose video, it's a video POST problem

So compare DEVICE as shown to where you know your swapfile is.  After boot,
do "swapon -s" and "vol_id" to make sure your swap is where you think it
is :=) 

derek at bella:~$ swapon -s
Filename                                Type            Size    Used   
/dev/sda5                               partition       3004112 30280   -1
derek at bella:~$ sudo vol_id /dev/sda5 | grep UUID=


> Thanks for your input, and hoping to solve the problem too...
And thanks for asking instead of just bitching.

More information about the ubuntu-users mailing list