Suspend does not work on eeepc 1101ha (Karmic)

[Fabs]

Binary package hint: pm-utils

When asked to suspend the machine turns of and shows to suspend properly (the battery led keps blinking after shutdown like windows). I am using the lid to suspend, so when the lid is open again, the computer seens to not awake. The keyboard does not respond (tryed caps lock to see the light) and the screen does not power up. If power button is pressed the machine restarts.

ProblemType: Bug
Architecture: i386
Date: Tue Sep 1 12:05:04 2009
DistroRelease: Ubuntu 9.10
Package: pm-utils 1.2.5-2ubuntu4
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SourcePackage: pm-utils
Tags: ubuntu-unr
Uname: Linux 2.6.31-8-generic i686

[Serge Hallyn (serge-hallyn)]

Please reply if this is still an issue on a supported release.

[Joshua Bell (eages)]

Experiencing the same issue on my 1101HAb. Tested in Lubuntu 14.04 LTS with current release's kernel (3.13) and upstream's kernel (3.15rc2). The good news is, another 1101HA in the house doesn't exhibit this problem. It's running the previous release of Lubuntu and is able to suspend/resume. I've tried multiple distros on my device though and I'm sure it's not a Lubuntu-specific issue.

Other info:
Currently, I'm booting the kernel with "acpi_osi=Linux" to fix a well-known backlight adjustment issue.
I get many errors from apportcheckresume each time I boot.
To get the other laptop working, I remember having to adjust a cups config file. Unfortunately, I don't remember which. I'm not sure if this is relevant to the latest kernel release.

[Joshua Bell (eages)]

Workaround found! If the machine has been put into hibernate, consequent suspends can be resumed.

To reproduce:
1. Hibernate ("sudo pm-hibernate")
2. Wake up.
3. Suspend ("sudo pm-suspend" or close lid)
4. Machine now wakes up when power button is pressed.

I hope this can help the devs in some way. In the meantime, it's as good as I can do.

[Joshua Bell (eages)]

I've set the status to confirmed because I've observed the problem on two machines running different distributions. I'm not sure if doing this usurps any authority. If so, I apologise.

[penalvch (penalvch)]

Fabs, thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in the latest release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ ?

If so, please execute the following via a terminal in order for the necessary debugging information to be attached:
apport-collect 422472

[Joshua Bell (eages)]

ApportVersion: 2.14.7-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2260 F.... pulseaudio
CasperVersion: 1.346
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141207)
MachineType: ASUSTeK Computer INC. 1101HA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.138
Tags: vivid
Uname: Linux 3.16.0-25-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0323
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0323:bd12/01/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[Joshua Bell (eages)]

apport information

[penalvch (penalvch)]

Joshua Bell, please do not apport-collect to a report you are not the original reporter of. If you want your problem addressed, and so your hardware and problem may be tracked, please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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