Hibernate failure?

Bug #14735 reported by paul hendrick
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

running /etc/acpi/suspend.sh does nothing at all, no output at the terminal.
running /etc/acpi/hibernate.sh give me output at the terminal(below), blanks the
screen for a few seconds, and then takes me into the xscreensaver unlock screen.

kernel: 2.6.10/11
laptop: acer aspire 1802
(http://www.acernotebooks.co.uk/Acer_Aspire_1800_Laptop/prod.asp)
latest hoary dist.

hibernate.sh output:
paul@spotlight:~ $ sudo /etc/acpi/hibernate.sh
Password:
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:02:3f:08:9e:8e
Sending on LPF/eth0/00:02:3f:08:9e:8e
Sending on Socket/fallback
DHCPRELEASE on eth0 to 10.0.0.138 port 67
xscreensaver-command: throttled.

xscreensaver-command: activating and locking.

/etc/acpi/resume.sh: line 10: /var/lib/acpi-support/vbestate: No such file or
directory
Warning: Interface name is `eth0' at line 2, can't be mapped reliably.
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:02:3f:08:9e:8e
Sending on LPF/eth0/00:02:3f:08:9e:8e
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 10.0.0.138
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.0.0.138
bound to 10.0.0.9 -- renewal in 3477 seconds.
xscreensaver-command: deactivating.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Suspend-to-RAM is disabled by default. Hibernate works by default on recent
installs, but if you upgraded an older install, you may need to set your resume
partiton in /etc/mkinitrd/mkinitrd.conf. Check dmesg or /var/log/kern.log for
error messages from the hibernate process.

Revision history for this message
paul hendrick (paul-hendrick) wrote :

(In reply to comment #1)
> Suspend-to-RAM is disabled by default. Hibernate works by default on recent
> installs, but if you upgraded an older install, you may need to set your resume
> partiton in /etc/mkinitrd/mkinitrd.conf. Check dmesg or /var/log/kern.log for
> error messages from the hibernate process.

I tried that on my warty install, but still no luck. i've just installed hoary
from today's iso, and hibernate still gives me a black screen. i gave it about 1
- 2 minutes before i shut the machine down, since it didn't seem to be doing
anything at all.

thanks.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Suspend and hibernate are not supported under Warty, only Hoary, and only with
the default 2.6.10 kernel (not the unsupported 2.6.11 kernel from universe)

Revision history for this message
paul hendrick (paul-hendrick) wrote :

(In reply to comment #3)
> Suspend and hibernate are not supported under Warty, only Hoary, and only with
> the default 2.6.10 kernel (not the unsupported 2.6.11 kernel from universe)

i am using the 2.6.10 kernel (smp version) and i've tried with the default hoary
kernel also, but i still just get a black screen when i hibernate. how long
should it take from clicking hibernate until the system is shut down?

Revision history for this message
Matt Zimmerman (mdz) wrote :

It can sometimes take a while (1-2 minutes).

If you set USE_DPMS=false in /etc/default/acpi-support, you should be able to
see status messages during the shutdown.

Revision history for this message
Ben Collins (ben-collins) wrote :

Can the bug submitter confirm that they tried the hoary kernel with hoary
scripts, on a fresh hoary install?

Atleast try Colony 5 live cd, if you can't do an upgrade to breezy. Thanks.

Revision history for this message
Ben Collins (ben-collins) wrote :

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Revision history for this message
Ben Collins (ben-collins) wrote :

Closing, inactive.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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