[Hardy] laptop fails to resume from suspend to ram

This bug was fixed in the package hal-info - 20080215-1ubuntu1

---------------
hal-info (20080215-1ubuntu1) hardy; urgency=low

  * New upstream snapshot with updated hardware quirks and attributes.
    - Do not consider 0x05e3:0x0702 as a music player, since this chip is also
      present in some IDE drives like the Adaptec ACS-120 USB Enclosure.
      (LP: #182051)
    - Adds Sansa e140 music player. (LP: #134849)
  * Merge from debian unstable, remaining changes:
    - 01_dell_cdrom_nopoll.patch: Re-introduce disabling of
      Dell Inspiron laptop CD-ROMs (GCC-4240N), since due to a weird hardware
      bug they cause extreme slowdown. (LP #48499)
    - 02_laptop_panel_brightness_in_hardware.patch: Some Thinkpads have ACPI
      brightness controls, disable laptop_panel.brightness_in_hardware for
      them.
  * Add debian/patches/03_olympus_ds2.patch: Add Olympus DS-2 voice recorder
    (LP: #94924)
  * Add debian/patches/04_nokia5300.patch: Add Nokia 5300 music player
    (LP: #103831)
  * Add debian/patches/05_mobile_media_tech_usb.patch: Add No-name music
    player sold as "Lavod", with a chip from Mobile Media Tech.
    (LP: #114443)
  * Add debian/patches/06_samsung_ypk3.patch: Add Samsung Yepp YP-K3 music
    player. (LP: #120413)
  * Add debian/patches/07_asus_v6v_pm_quirk.patch: Use s3_bios PM quirk for
    the Asus V6V. (LP: #191737)
  * Add debian/patches/08_asus_p5l_quirk.patch: Add video quirks for Asus
    P5LD2. (LP: #190456)
  * Add debian/patches/09_lyra_th1501.patch: Add Lyra TH1501 music player.
    (LP: #157904)
  * Add debian/patches/10_sony_w880i.patch: Add Sony Ericsson W880i Walkman
    Phone. (LP: #117809)

hal-info (20080215-1) unstable; urgency=low

  * New upstream release.
    - Fixes a typo in 20-video-quirk-pm-lenovo.fdi. (Closes: #462012)
  * debian/patches/00_disable_mpio_hd300_detection.patch
    - Removed, merged upstream.
  * debian/control
    - Bump Standards-Version to 3.7.3. No further changes required.

hal-info (20071212-2) unstable; urgency=low

  * debian/patches/00_disable_mpio_hd300_detection.patch
    - Added. Disable MPIO HD300 detection. The exact same usb controller is
      used in some common usb disks, causing very annoying false positives
      (Closes: #456675)

 -- Martin Pitt <email address hidden> Thu, 28 Feb 2008 17:11:42 +0100

This problem persist with Hardy 8.04 Alpha 6 release on my Asus F5N laptop. After suspending to RAM, laptop wakes up to a black screen, no backlight. Keyboard works, and pressing power button shuts down the laptop. Suspend was no problem in Gutsy 7.10

Detailed information about this laptop is found at https://wiki.ubuntu.com/LaptopTestingTeam/AsusF5N
And I am attaching the output of lspci -vvnn command.

The only warning in log files are about 1 client disconnected on reusme in /var/log/acpid and not suspending / not resuming usb_stk11xx_driver in /var/log/kern.log

I can confirm this bug. My Laptop hangs after resuming from suspend to ram.
I've just installed Hardy Beta with latest updates. In Gutsy suspend to ram worked quite well.
It's very impractical, that it is not working anymore because it worked so well and I use it really often.
There is only a black screen after resuming, strg+alt+f1 does nothing. I can only turn of the computer with long pressing the power button.
There is no difference whether compiz is enabled or disabled.

Hardware:
intel 945gm graphic
intel core duo processor

Kernel is:
Linux 2.6.24-15-generic #1 SMP Tue Apr 8 00:33:51 UTC 2008 i686 GNU/Linux

I've attached following files (in the same order) in "log_files.txt":
Xorg.0.log
kern.log
dmesg
acpid
pm_suspend.log

@Olivier: What do you mean with "I discovered that I need to add both s3_mode and s3_bios quirks to get it to resume reliably."... How?

Thanks a lot for all help!

Lex and Kev, your problems are runrelated to this bug. Suspend now works as it should on my V6V : Thanks Martin !

Have a look at http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html and try various quirks. Once you found the ones working with your computer, open a new bug giving the relevant info. good luck !

Thanks for your answer, Olivier.
After the latest update it is now working for me, really great :)!