I also get this bug on an Intel P915GM chipset laptop with a Celeron M processor. For all intents and purposes the suspends seems to work fine - everything shuts down and the power led starts blinking, indicating the computer is sleeping, and when I resume the battery isn't drained more than expected.

From syslog, edited for brevity, full log attached:
Jun 10 01:15:46 molotov gnome-power-manager: (nino) Suspending computer because the DBUS method Suspend() was invoked
-- snipped messages from network interfaces going down, DHCP releases etc --
Jun 10 01:15:59 molotov kernel: [ 2687.540000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jun 10 01:15:59 molotov kernel: [ 2687.664000] ACPI: PCI interrupt for device 0000:06:02.0 disabled
Jun 10 08:02:14 molotov gnome-power-manager: (nino) An unknown error occured code='32' quark='g-exec-error-quark'
Jun 10 08:02:14 molotov gnome-power-manager: (nino) Resuming computer
Jun 10 08:02:14 molotov gnome-power-manager: (nino) suspend failed
Jun 10 08:02:14 molotov kernel: [ 2690.256000] PM: Preparing system for mem sleep
Jun 10 08:02:14 molotov kernel: [ 2690.256000] Disabling non-boot CPUs ...
Jun 10 08:02:14 molotov kernel: [ 2690.256000] Stopping tasks ... done.
Jun 10 08:02:14 molotov kernel: [ 2691.028000] Suspending console(s)

Here the computer seems to be entering suspension again, after the fact? lots of suspend messages edited out...

Jun 10 08:02:14 molotov kernel: [ 2692.688000] pci 0000:00:02.1: suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] pci 0000:00:02.0: suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] agpgart-intel 0000:00:00.0: suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] acpi acpi: suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] ACPI: Transitioning device [FAN0] to D0
Jun 10 08:02:14 molotov kernel: [ 2692.688000] ACPI: Transitioning device [FAN0] to D0
Jun 10 08:02:14 molotov kernel: [ 2692.688000] PM: Entering mem sleep
Jun 10 08:02:14 molotov kernel: [ 2692.688000] platform bluetooth: LATE suspend
-- snipped --
Jun 10 08:02:14 molotov kernel: [ 2692.688000] HDA Intel 0000:00:1b.0: LATE suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] pci 0000:00:02.1: LATE suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] pci 0000:00:02.0: LATE suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] agpgart-intel 0000:00:00.0: LATE suspend
Jun 10 08:02:14 molotov kernel: [ 2692.688000] Back to C!
Jun 10 08:02:14 molotov kernel: [27059.688000] agpgart-intel 0000:00:00.0: EARLY resume
Jun 10 08:02:14 molotov kernel: [27059.688000] pci 0000:00:02.0: EARLY resume
Jun 10 08:02:14 molotov kernel: [27059.688000] pci 0000:00:02.1: EARLY resume
Jun 10 08:02:14 molotov kernel: [27059.688000] HDA Intel 0000:00:1b.0: EARLY resume
-- snipped --
Jun 10 08:02:14 molotov kernel: [27059.688000] platform bluetooth: EARLY resume
Jun 10 08:02:14 molotov kernel: [27059.688000] PM: Finishing wakeup.
Jun 10 08:02:14 molotov kernel: [27059.688000] acpi acpi: resuming
Jun 10 08:02:14 molotov kernel: [27059.688000] ACPI: [Power Resource - CTHT] resume failed: -8
Jun 10 08:02:14 molotov kernel: [27059.688000] ACPI: Transitioning device [FAN0] to D3
Jun 10 08:02:14 molotov kernel: [27059.688000] ACPI: Transitioning device [FAN0] to D3
Jun 10 08:02:14 molotov kernel: [27059.704000] agpgart-intel 0000:00:00.0: resuming
-- snipped --
Jun 10 08:02:14 molotov kernel: [27061.152000]  hci0: PM: resume from 0, parent 4-1:1.0 still 2
Jun 10 08:02:14 molotov kernel: [27061.152000] Restarting tasks ... <6>usb 4-1: USB disconnect, address 2
Jun 10 08:02:14 molotov kernel: [27061.224000] done.
Jun 10 08:02:14 molotov kernel: [27061.224000] Enabling non-boot CPUs ...

After this my network interfaces start up and normal things happen.

I'm not sure how the kernel is supposed to act when suspending - is it normal that messages from the suspension are logged after the computer resumes?

Mariano Draghi : I don't think your bug #112659 is a dup of this one - our computers suspend and stay suspended, we just get a spurious error message.