Acer Aspire One ZA3 751h does not resume from suspend

[Hankyone]

Binary package hint: pm-utils

When going into suspend mode on a Acer Aspire One ZA3 751h, the computer does not resume when pressing a key or the power button.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pm-utils 1.3.0-2
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
Architecture: i386
Date: Mon Jul 5 12:17:11 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100705)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: pm-utils

---
Architecture: i386
DistroRelease: Ubuntu 10.10
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100714)
Package: xorg 1:7.5+6ubuntu2
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Tags: maverick maverick
Uname: Linux 2.6.35-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/01/2009
dmi.bios.vendor: Acer
dmi.bios.version: V0.3209
dmi.board.name: JV11-ML
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV0.3209:bd09/01/2009:svnAcer:pn:pvrNotApplicable:rvnAcer:rnJV11-ML:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-7-generic

[Ameet Paranjape (ameetp)]

@Anouar,

Please follow https://wiki.ubuntu.com/DebuggingKernelSuspend and attach the log to the bug. Thanks.

[Ameet Paranjape (ameetp)]

Spoke with Anouar and this system is having some hardware issues. He is working to fix those and then he will try to recreate this bug.

[Ameet Paranjape (ameetp)]

Anouar,

Can you verify that this is still a problem in the latest 10.10 kernel of the day and provide the logs from that.

[Sebastien Bacher (seb128)]

Thank you for the bug report, it might be something for the kernel team rather than our team though but letting a chance to pitti to comment about it since he knows that stack better

[Martin Pitt (pitti)]

I do not see any suspend attempt in this dmesg. Please precisely describe the behaviour:

 - After you trigger suspend, does the power light etc. indicate that the machine is actually suspended, instead of being turned off entirely?

 - What does "not resume" mean exactly? Does it attempt to resume, but you get a black screen, but the hard disk, power light, etc. comes back? Or it stays in suspend mode even if you open the lid or press the power button?

If pressing the power button does absolutely nothing, then this is a hardware/BIOS problem. If it does resume, but not correctly, then we need to find out which quirks your machine needs.

[Hankyone (hankyone)]

After triggering suspend the green LED turns into an orange blinking LED.

To resume, I hit the power button and the LED then turns green and the hard disk LED blinks once but nothing happens after that, The screen stays black

[Martin Pitt (pitti)]

Thanks for confirming. So that means that everything should be alright with the hardware. What kind of graphics card does this machine have? For information around your hardware it would be easiest if you could run "apport-collect -p xorg 602029", this will collect the necessary info.

As for finding the actual quirk(s) I'm afraid we need to get a little dirty. It's probably best if you run that from a live system, so that you avoid any data corruption on the hard disk from hard power cycles on failed attempts. What you need to do is to try running "pm-suspend --quirk-..." with each of the available quirks until you find one which gets you a good resume again. On a failure, reboot the machine. The set of available quirks is documented in "man pm-suspend", section "OPTIONS". For example:

  sudo pm-suspend --quirk-dpms-on

(obviously you don't need to try the radon quirks if you do not have a Radeon/ATI card).

Please note that it might also necessary to have more than one quirk, but let's try the single options first. Also, once you send your hardware data with apport-collect, I might be able to give you a more precise list of quirks to try, by comparing with similar models.

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Hankyone (hankyone)]

apport information

[Martin Pitt (pitti)]

Ah, thanks for the logs. So you are using the VESA driver (there is no open source driver for the Intel Poulsbo).

You could try this one first:

 sudo pm-suspend --quirk-s3-bios --quirk-s3-mode --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3

Does this work? If not, please try all available options (except the radeon ones) one by one.

[Hankyone (hankyone)]

Unfortunately it did not.

Going to try all the options now.

[Hankyone (hankyone)]

Good news! "sudo pm-suspend -quirk-vbestate-restore" did the trick!

[Martin Pitt (pitti)]

Perfect! I'll cook up a patch for pm-utils, send it upstream, and upload it to Debian/Ubuntu.

[Martin Pitt (pitti)]

Hm, unfortunately the BIOS on this machine is broken, it does not provide a product name at all. So we can't actually match against this device in the quirks database. You should be able to fix it locally with

  sudo pm-suspend --quirk-vbestate-restore --store-quirks-as-lkw

[Martin Pitt (pitti)]

Setting to wontfix, because of the broken DMI information from the BIOS.