Asus EeePC 1101HA wakeup from sleep

Bug #1370689 reported by carrolcoo
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I have lubuntu on my Asus EeePC 1101HA and after suspend I cannot wake up the machine (I tried kubuntu as well).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-35-generic 3.13.0-35.62
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ch 1660 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
CurrentDmesg: [ 25.629421] gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
Date: Wed Sep 17 21:17:01 2014
HibernationDevice: RESUME=UUID=10bdc926-3f4b-42cc-8f14-205011e6f7bc
InstallationDate: Installed on 2014-08-13 (34 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: ASUSTeK Computer INC. 1101HA
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=8e4bcbc4-6498-4b8d-9327-9acee95b85a7 ro quiet splash acpi_backlight=vendor mem=1920mb vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-35-generic N/A
 linux-backports-modules-3.13.0-35-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

Revision history for this message
carrolcoo (karol-zitnansky) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc5-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
tags: added: latest-bios-0323
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Asus EeePC 1101HA wakeup from sleep/PowerButton not working
+ Asus EeePC 1101HA wakeup from sleep
description: updated
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

I tested the latest '3.17.0-031700rc5-generic' kernel and the bug still exists there.
Added tag 'kernel-bug-exists-upstream', changing Status to 'Confirmed'.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-3.17-rc5
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

>> carrolcoo, did this problem not occur in a release prior to Trusty?
Trusty was the first release I installed on this laptop.

I followed requested steps to add missing information with:
ch@chplusjntb:~$ uname -a
Linux chplusjntb 3.17.0-031700rc5-generic #201409151105 SMP Mon Sep 15 16:49:53 UTC 2014 i686 i686 i686 GNU/Linux

>> At this point your computer should enter the suspend state within a few seconds. Usually the power LED will slowly flash when in the suspended state.

I let the LED slowly flash about 10 seconds

>> When that has happened, initiate the resume process by pressing the power button. Observe closely if the disk light comes on briefly. This indicates that resume has begun.

After pressing the power button nothing happened (no disk light was on briefly, no resume started, LED kept flashing slowly)

>> If resume fails to complete, then press the power button until the computer turns off. Power on your computer making sure that it loads the same kernel that exhibited the resume problem.

So I pressed the power button, computer turned off, I released and pressed the power button to start it again. Booted into the above 3.17* kernel. Attaching wakeup and dmesg.txt.

Revision history for this message
carrolcoo (karol-zitnansky) wrote :
Revision history for this message
carrolcoo (karol-zitnansky) wrote :
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

12.04.0 live environment tested:
uname -a gets:
Linux ubuntu 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686 i686 i386 GNU/Linux

- after entering the sleep mode via Fn+F1 (Sleep button) pressing power button does nothing (the same as in Trusty, LED keeps flashing)
- acpi_listen shows nothing after pressing power button
- in a running session no GUI change (I have no idea if a log off/power off dialog should appear) after pressing power button

Revision history for this message
penalvch (penalvch) wrote :

carrolcoo, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
tags: added: precise
Revision history for this message
carrolcoo (karol-zitnansky) wrote :
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

Christopher M. Penalver could you please review the attached 'upstream.mail' file and inform me if it is OK and if it contains all relevant information? I'm not sure in points 2., 5., 6. and 'In addition, please be 100% certain you have included all relevant comment information not included in the Bug Description and a kernel developer should review.'

Many thanks.

Revision history for this message
carrolcoo (karol-zitnansky) wrote :

Next question - I suppose I should report a non-USB bug - which driver should I look for in the MAINTAINERS list?

Revision history for this message
penalvch (penalvch) wrote :

carrolcoo, looks good. One would want to send this to the linux-acpi mailing list.

Revision history for this message
carrolcoo (karol-zitnansky) wrote :

Hi.

Until now I have got no answer from linux-acpi gurus. I hope I send the mail correctly.

Anyway in the meantime I tried another distros but landed again by lubuntu 14.10:
  ch@chplusjntb:~$ uname -a
  Linux chplusjntb 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:13:18 UTC 2014 i686 i686 i686 GNU/Linux

The good news is I found a bug (https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/422472) and the workaround works by me as well!

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.

Is this still an upstream issue? Or should be addressed to pm-utils? I would like to have the suspend working without previous hibernate...

Revision history for this message
penalvch (penalvch) wrote :

carrolcoom, just to clarify, this would have nothing to do with pm-utils.

As well, if this is tested to be an issue in the latest mainline kernel, then it remains an upstream issue. Hence, could you please test the latest mainline kernel 3.18-rc6 and advise to the results?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

Hi.

ch@chplusjntb:~$ uname -a
Linux chplusjntb 3.18.0-031800rc6-generic #201411231935 SMP Mon Nov 24 00:57:52 UTC 2014 i686 i686 i686 GNU/Linux

After reboot and calling 'sudo pm-suspend' the machine gets to the suspended state (LED's are flashing) and it's not possible to wake up the machine - hence still an issue.

I tried to test the workaround but the hibernate seems to be broken: after calling 'sudo pm-hibernate' the machine doesn't get to the hibernate state (stays with black screen with backlight on, LED's and fan are on).

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.18-rc6
removed: kernel-bug-exists-upstream-3.17-rc5
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
carrolcoo (karol-zitnansky) wrote :

Hi.

I recently tried fresh install of Kubuntu 15.04 and the bug seems to be fixed.

ch@chplusj-ntb:~$ uname -a
Linux chplusj-ntb 3.19.0-30-generic #34-Ubuntu SMP Fri Oct 2 22:07:32 UTC 2015 i686 i686 i686 GNU/Linux

Revision history for this message
penalvch (penalvch) wrote :

carrolcoo, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370689/comments/19 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.