HAL failed to hibernate

Ubuntu ->hal

I guess it doesn't actually hibernate, in these 10 seconds it prepares to hibernate.

Can you please start hal in debugging mode, as described on the second half of https://wiki.ubuntu.com/DebuggingRemovableDevices, try to hibernate while that is running, and attach the log afterwards? Thank you!

I have been facing the same issue on fiesty. Please find the attached hal.log file.

I am sorry I have forgot to add the lspci -v. I am running fiesty on a HP Tablet PC TC4200.

I am experiencing this exact problem. Hibernate worked for Edgy, but after I upgraded to Feisty Beta hibernate is now broken. gnome-power-manager keeps reporting that HAL failed to hibernate.

Here are relevant entries in my /var/log/messages file that seem relevant.

Mar 28 14:17:42 atlantis gnome-power-manager: (kyle) An unknown error occured code='32' quark='g-exec-error-quark'
Mar 28 14:17:42 atlantis gnome-power-manager: (kyle) Resuming computer
Mar 28 14:17:42 atlantis gnome-power-manager: (kyle) hibernate failed

Hibernate is still broken for me as of 14/4/07 with all updates applied. If it is any help, here is my attached hal.log.

I have seven ubuntu users who upgraded from edgy to fiesty and lost hibernate/suspend support after the upgrade.

I can add that this bug was never solved at all... Even after a clean install.

The Hibernate and Suspend were working 100% in edgy, until I installed Fiesty. (I am assuming the same issues would exist on *ALL* HP Laptops having the same chipset)

I have the same problem with an Acer 4001 and Feisty. It worked really fine in Edge and Dapper. Until Feisty following happens:
When hibernating the screen gets locked immediately. Suspend powers off the laptop but resuming fails (black screen after pressing a key - restart needed).

Could we get those who have issues with suspend in fiesty to try
suspend/hibernate from the gdm login screen. IE during your session
use the switch user feature or logout to get back to the gdm screen and
then try to suspend. I have some conflicting reports on whether or not
this works.

Jonah

On Thu, 2007-04-26 at 15:50 +0000, craffels wrote:
> I have the same problem with an Acer 4001 and Feisty. It worked really fine in Edge and Dapper. Until Feisty following happens:
> When hibernating the screen gets locked immediately. Suspend powers off the laptop but resuming fails (black screen after pressing a key - restart needed).
>
>
> ** Attachment added: "Hal Debug File"
> http://librarian.launchpad.net/7411290/hal.log
>

I tried to hibernate/suspend from the dgm login screen and it makes no difference. It still fails to hibernate with the same HAL error. It hibernated and suspended perfectly in Edgy.

This is being felt by quite a number of users. See ubuntuforum threads 420296 and 413792.

I have tried all the workarounds suggested in the forums and none work.

For me, the failure of HIBERNATE on a laptop is a major issue. It cuts down boot and application start time, thus saving battery - vital on a business trip.

Suspend to RAM works with no apparent problem

Suspend to Disk apparently works, with disk acivity, then a period of quiscence, then some graphic mess in the top few lines of the screen, then a blank screen and a password box.

In /var/log/debug I have the lines
Apr 29 21:55:54 localhost kernel: [ 961.696000] agpgart-intel 0000:00:00.0: LATE suspend
Apr 29 21:55:54 localhost kernel: [ 961.696000] Back to C!
Apr 29 21:55:54 localhost kernel: [ 977.696000] agpgart-intel 0000:00:00.0: EARLY resume

Another Hibernate attempt produces the following:
Apr 29 22:53:36 localhost kernel: [ 4440.212000] agpgart-intel 0000:00:00.0: LATE freeze
Apr 29 22:53:36 localhost kernel: [ 4440.212000] swsusp: Normal pages needed: 123927 + 1024 + 24, available pages: 135355
Apr 29 22:53:36 localhost kernel: [ 4441.212000] agpgart-intel 0000:00:00.0: EARLY resume

The "page" problem gets worse with each subsequent HIBERNATE attempt (next lines generated with <grep swsusp ./debug>
Apr 29 21:32:08 localhost kernel: [ 139.516000] swsusp: Normal pages needed: 89454 + 1024 + 24, available pages: 172182
Apr 29 22:02:40 localhost kernel: [ 1385.060000] swsusp: Normal pages needed: 111273 + 1024 + 24, available pages: 131069
Apr 29 22:08:40 localhost kernel: [ 1744.928000] swsusp: Normal pages needed: 115827 + 1024 + 24, available pages: 129717
Apr 29 22:31:04 localhost kernel: [ 3088.172000] swsusp: Normal pages needed: 118392 + 1024 + 24, available pages: 129662
Apr 29 22:42:14 localhost kernel: [ 3758.224000] swsusp: Normal pages needed: 123826 + 1024 + 24, available pages: 132656
Apr 29 22:53:36 localhost kernel: [ 4440.212000] swsusp: Normal pages needed: 123927 + 1024 + 24, available pages: 135355

I upgraded to Feisty in early April, and did not notice the Hibernate problem until late April, viz after a flurry of updates (but I cant remember which).

Hope this helps.

Richard

Looking at other hibernate bugs, the following look very similar:
23090
68069
63078
73805

Tried to hibernate and suspend from the gdm window but both failed.

I tried to run /etc/acpi/hibernate.sh directly and get nearly the same output as in bug #94332 (an error that acpi_sbs module is not found).
Maybe some of you should also try to run the hibernate script directly and check the output.

My Hp suspends/hibernates and resumes sucesfully about 30% of the time. I actually don't have a use for hibernate as it takes to long. I have gotten fiesty to suspend to ram with no issues (if you turn off beryl) .

 if anyone else has a proposed solution please post it. if you look at the hal errors posted on launchpad youll notice no one really tries to fix hal.

 Richard Hainsworth , Have you tried running rmmod agpgart-intel prior to suspend/hibernate?

I have similar problems with hibernate/suspend after upgrade to Feisty. However, in addition to the above errors, I also experience complete lockups (Bug #100087), and that the computer powers up on opening the lid and other events (sometimes it powers up in my backpack for no reason at all), no matter if the computer is shut down or hibernated. Everything worked excellent in Edgy, so this is really an issue. I actually consider downgrading.

Stefan

I've got the exact same problem on a Clevo D900K laptop, with fresh install of i386 Ubuntu Feisty from shipit CD.
When asking GDM to hibernate, the screen blinks twice, and after three seconds the GDM locked screen appears. When i enter my password, gnome is still running fine. /var/log/messages says hibernation failed with "An unknown error occured code='32' quark='g-exec-error-quark' ".
I hope these attachments help...

lspci -vv

/var/log/messages

I found the cause, it's the nvidia driver. When i switch to nv, hibernate works perfect!

My dilemma is that the nv driver does not support my two screens (both 1920x1200), it uses only one.

I too am experiencing this problem with a Dell XPS M140. Relevant lines from /var/log/messages:

Jun 10 02:47:07 stocksxps gnome-power-manager: (bobby) Hibernating computer beca
use the lid has been closed on ac power
Jun 10 11:10:21 stocksxps gnome-power-manager: (bobby) An unknown error occured
code='32' quark='g-exec-error-quark'
Jun 10 11:10:24 stocksxps gnome-power-manager: (bobby) Resuming computer
Jun 10 11:10:25 stocksxps gnome-power-manager: (bobby) hibernate failed

Suspend doesn't work either. I have the same problem as described above. It goes into suspend ok, but in attempting to resume the screen stays completely black and the computer requires a restart. I have tried switching from the xserver-xorg-video-i810 to the xserver-xorg-video-intel as described by https://wiki.ubuntu.com/LaptopTestingTeam/DellInspiron630m with no luck.

I experience the same problem on my both workstation and notebook (HP nx7400) since I have upgraded to Fiesty Fawn.
My workstation hardware configuration is
#lspci

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

I was getting the same error, but now I have "a" form of hibernate working.

Here's what I did.

     sudo apt-get install hibernate

Then edit "/etc/acpi/hibernate.sh" add on the second line put:

     exec /usr/sbin/hibernate

Now hibernate works.

A possible workaround for people that have this problem sometimes: sudo /etc/init.d/dbus restart

Weird but it worked for me. It seems that dbus gets in some odd state after a series of hibernations/updates.

Fwiw...
I experienced the exact symptoms described here: hibernation works in edgy, doesn't work any more after upgrading to feisty.
These days, I didn't get around doing a clean new install of feisty -- and hibernation works now, on the same computer it didn't work on yesterday.
My personal conclusion is therefore that the update edgy->feisty broke it.

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

I was also getting the error in Feisty:
An unknown error occured code='32' quark='g-exec-error-quark'

For me it started after I resized my swap partition and formatted it using gparted. You can tell if swap is working by running 'sudo swapon -s'. If the swap disk (eg /dev/sda1) appears in the output then it is setup and working. The 'free' command also reports swap usage. If not try turning it on using 'sudo swapon -a'. This didn't work for me because I got:

$ sudo swapon -a
swapon: cannot stat /dev/disk/by-uuid/9be7c290-84e3-4fbb-99b0-727bcead8e8d: No such file or directory

Because of the modifications I did to the swap partition, the uuid had changed, which could be seen running:
$ ls -la /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 100 2008-05-06 23:14 .
drwxr-xr-x 5 root root 100 2008-05-06 23:14 ..
lrwxrwxrwx 1 root root 10 2008-05-06 23:14 0031c2e0-d523-49f9-86b8-9f100e6f949e -> ../../sda1
lrwxrwxrwx 1 root root 10 2008-05-06 23:14 86afa7d7-d76d-485a-af40-cb4b7ed87e62 -> ../../sda3
lrwxrwxrwx 1 root root 10 2008-05-06 23:14 fda4423e-e722-4be4-a520-7ec178f192aa -> ../../sda2

sda1 is my swap partition and /etc/fstab had a different uuid for sda1. By editing /etc/fstab to use the uuid reported by /dev/disk/by-uuid and running 'sudo swapon -a' to turn the swap back on, suspend starting working again. Here it is with the swap summary:

$ sudo swapon -s
Filename Type Size Used Priority
/dev/sda1 partition 3903752 0 -1

One other piece of information, the above got my suspend to work, but it would not resume. I had to edit
/etc/initramfs-tools/conf.d/resume with the correct UUID for my swap partition in order for resume to work properly. Also run this:

sudo update-initramfs -u

More details in bug 105490: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/105490

Browsing these postings has convinced me there's something very wrong with Ubuntu POWER MANAGEMENT that needs to be fixed. I've experienced similar frustrating problems myself and have given up on HIBERNATE, for reasons outlined above i.e. not being able to hibernate increases boot time and consumes battery power. My only alternative is SUSPEND ... which consumes more power. Anyone for Microsoft?

Nope, not for Microsoft...

But you are right. There is definitely something wrong. It seems every time
I upgrade ubuntu, suspend/hibernate either start working again, or they
worked in the previous version and now they stop working. It also seems to
flip-flop based on the architecture.

For example, my desktop (64bit ubuntu) used to hibernate/suspend fine prior
to the most recent release and now it won't do either. My laptop (xps m140)
was having intermittent problems hibernating/suspending prior to the most
recent release and now it works fine....

On Wed, Jul 30, 2008 at 2:50 AM, wordsmyth <email address hidden>wrote:

> Browsing these postings has convinced me there's something very wrong
> with Ubuntu POWER MANAGEMENT that needs to be fixed. I've experienced
> similar frustrating problems myself and have given up on HIBERNATE, for
> reasons outlined above i.e. not being able to hibernate increases boot
> time and consumes battery power. My only alternative is SUSPEND ...
> which consumes more power. Anyone for Microsoft?
>
> --
> HAL failed to hibernate
> https://bugs.launchpad.net/bugs/68258
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Robert Stockdale
<email address hidden>