Laptop hibernate correctly, but reboot instead shutdown

With the kernel version available at Gusty, the laptop hibernate correctly.
Issue at hardy

I've got this issue as well. Before the thing reboots, I get some error messages:

cpufreq: suspend failed to assert current frequency is what timing core thinks it is
cpufreq: resume failed to assert current frequency is what timing core thinks it is
i8042 aux 00:03: activation failed

I've tried adding all the cpufreq related modules to the list to remove/reload in /etc/default/acpi-support, as well as messed around with a variety of options (laptop_mode, disable_dma, hibernate_mode), but nothing seems to do the trick.

My system is a Sharp TN10W, Intel Banias 1.1 Ghz processor, Intel i810 graphics, no desktop effects. Hibernation used to work fine in Gutsy, although the fan would always spin up full speed right when the computer shut down.

I have this with latest release Hardy on an Acer Aspire 4315.

Also occurred in Gutsy, with the same behavior on hibernate. Now, hibernate works correctly, suspend reboots instead of waking. In my case, nothing is written to the screen.

I have been asked to create a custom CD for this laptop for presentation to Acer NZ. It would be nice to include suspend functionality so I am motivated here. What should I be looking at?

Simon, I'd love to help you (and I will, if I can figure out what's going on). I really have no idea where to start looking though - I thought it was a cpufreq related problem, but I disabled all those modules and still had an issue. Strange that mine can suspend but not hibernate, and yours is the other way around. Do you get any error messages (in logs, etc)?

Simon, maybe you'd better open a new bug, since you have another problem now.

Please check bug #226069 and see if it's the same issue and if the workaround there works for you.

The workaround proposed in bug #226069
"
WORKAROUND:
Edit /usr/lib/pm-utils/functions and replace "platform" with "shutdown".
"
works.

Bug #226069 is marked as fix released, but if I had to do it by hand, bug isn't fixed in Hardy, right?

It's fixed in intrepid (current development version). I nominated it for getting it fixed in hardy, but no luck yet.

Since the workaround works for you, it's surely the same issue, and I'll mark this one as a duplicate.