[HP G62-120EL Notebook PC] Suspend triggered via dbus message on laptop fails

Bug #752881 reported by Carla Sella on 2011-04-06
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Checkbox
Low
Daniel Manrique
checkbox (Ubuntu)
Low
Daniel Manrique

Bug Description

When testing Natty Beta 1 iso on my HP laptop (G62 Notebook PC), during the "Extended Suspend/Resume test" , TEST1 "suspend triggered via dbus message" fails with the message: "SUSPEND FAILED, did not go to sleep".
The test fails both with a live usb persistent key and also installing natty on the hard disk.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC270 Analog [ALC270 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: letozaf 1357 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4400000 irq 43'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0270,103c1425,00100100 HDA:80862804,80860101,00100000'
   Controls : 19
   Simple ctrls : 10
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=bd9ecec1-a6ab-4a10-b29b-096f53cfc0dc
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MachineType: Hewlett-Packard HP G62 Notebook PC
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=523b587b-bcfc-4931-ad39-f47fb570c977 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Regression: No
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
Reproducible: Yes
Tags: natty running-unity kernel-power suspend resume needs-upstream-testing
Uname: Linux 2.6.38-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1425
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.12
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd01/25/2010:svnHewlett-Packard:pnHPG62NotebookPC:pvr049D100000202710000020000:rvnHewlett-Packard:rn1425:rvr54.12:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 049D100000202710000020000
dmi.sys.vendor: Hewlett-Packard
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC270 Analog [ALC270 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: letozaf 5713 F.... pulseaudio
CRDA: Error: [Errno 2] File o directory non esistente
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4400000 irq 43'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0270,103c1425,00100100 HDA:80862804,80860101,00100000'
   Controls : 19
   Simple ctrls : 10
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=bd9ecec1-a6ab-4a10-b29b-096f53cfc0dc
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
MachineType: Hewlett-Packard HP G62 Notebook PC
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.39-3-generic root=UUID=d3a0136f-bc6b-486c-86af-a7e22a353251 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
RelatedPackageVersions:
 linux-restricted-modules-2.6.39-3-generic N/A
 linux-backports-modules-2.6.39-3-generic N/A
 linux-firmware 1.53
Tags: oneiric running-unity unity-2d
Uname: Linux 2.6.39-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1425
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.12
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd01/25/2010:svnHewlett-Packard:pnHPG62NotebookPC:pvr049D100000202710000020000:rvnHewlett-Packard:rn1425:rvr54.12:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 049D100000202710000020000
dmi.sys.vendor: Hewlett-Packard

Related branches

Carla Sella (carla-sella) wrote :

Also affects Natty Beta 2 iso.

Same bug in Dell Vostro 3500 in Beta 2

apport information

affects: ubuntu → linux (Ubuntu)
tags: added: apport-collected kernel-power natty needs-upstream-testing resume running-unity suspend
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Brad Figg (brad-figg) on 2011-05-04
Changed in linux (Ubuntu):
status: New → Confirmed
Carla Sella (carla-sella) wrote :

I'm having the same problem testing Oneiric Alpha 1.

Carla Sella (carla-sella) wrote :

On Oneiric Alpha 1 also the "Extended Suspend/Resume test" , TEST2: suspend with AC disconnected fails, when the notebook comes back from suspension all the applications are closed as if the notebook has been rebooted.

Carla Sella (carla-sella) wrote :

On Oneiric Alpha 1 Test2 failed two times having all the applications closed as if rebooted and the third time I tried I had this message instead: "SUSPEND FAILED, did not go to sleep".

Carla Sella (carla-sella) wrote :

same with *** TEST 3 -- suspend with AC connected got this message:
SUSPEND FAILED, did not go to sleep

Carla Sella (carla-sella) wrote :

same with *** TEST 4 -- loss of AC while suspended got this message:
*** TEST 4 -- loss of AC while suspended

Carla Sella (carla-sella) wrote :

same with *** TEST 5 -- return of AC while suspended same errore message after test:
SUSPEND FAILED, did not go to sleep

description: updated
Carla Sella (carla-sella) wrote :

*** TEST 6 -- battery drain during suspend failed with this error:
SUSPEND FAILED, did not go to sleep
before: 4160 mWh
after: 4128 mWh
consumed: 32 mW
sleep seconds: 1235 sec
overall usage: 93 mW

Carla Sella (carla-sella) wrote :

TEST 7 -- 30 iteration variable delay suspend/resume stress test
All tests failed:

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds

-----

apport information

tags: added: oneiric unity-2d
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

On Oneric Alpha 2 I still have the same problem

Carla Sella (carla-sella) wrote :

In Oneiric Alpha2 also Hibernate/Resume smoke test (to be done on installed systems only, not live environments) fails: laptop does not hibernate, and presents only the password screen as the session has only been blocked, all the opened applications remain opened.

Carla Sella (carla-sella) wrote :

With Oneiric Alpha 3 TEST1 "suspend triggered via dbus message" fails with the message: "SUSPEND FAILED, did not go to sleep".

Carla Sella (carla-sella) wrote :

Also Hibernate/Resume smoke test (to be done on installed systems only, not live environments) fails: laptop does not hibernate, and presents only the password screen as the session has only been blocked, all the opened applications remain opened.

Carla Sella (carla-sella) wrote :

Still having same problems also with Oneiric Beta 1:

*** TEST 1 -- suspend triggered via dbus message
did not work and got message:
SUSPEND FAILED, did not go to sleep

*** TEST 2 -- suspend with AC disconnected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 3 -- suspend with AC connected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 4 -- loss of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 5 -- return of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 6 -- battery drain during suspend
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep
before: 2976 mWh
after: 2944 mWh
consumed: 32 mW
sleep seconds: 1236 sec
overall usage: 93 mW

Carla Sella (carla-sella) wrote :

*** TEST 7 -- 30 iteration variable delay suspend/resume stress test

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAILED, did not go to sleep
wait for 30 seconds
delay 28 ...
SUSPEND FAILED, did not go to sleep
wait for 28 seconds
delay 26 ...
SUSPEND FAILED, did not go to sleep
wait for 26 seconds
delay 24 ...
SUSPEND FAILED, did not go to sleep
wait for 24 seconds
delay 22 ...
SUSPEND FAILED, did not go to sleep
wait for 22 seconds
delay 20 ...
SUSPEND FAILED, did not go to sleep
wait for 20 seconds
delay 18 ...
SUSPEND FAILED, did not go to sleep
wait for 18 seconds
delay 16 ...
SUSPEND FAILED, did not go to sleep
wait for 16 seconds
delay 14 ...
SUSPEND FAILED, did not go to sleep
wait for 14 seconds
delay 12 ...
SUSPEND FAILED, did not go to sleep
wait for 12 seconds
delay 10 ...
SUSPEND FAILED, did not go to sleep
wait for 10 seconds
delay 8 ...
SUSPEND FAILED, did not go to sleep
wait for 8 seconds
delay 6 ...
SUSPEND FAILED, did not go to sleep
wait for 6 seconds
delay 4 ...
SUSPEND FAILED, did not go to sleep
wait for 4 seconds
delay 2 ...

SUSPEND FAILED, did not go to sleep
wait for 2 seconds

*** Please report your results on the Ubuntu WIKI:
    https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

      Battery Consumption: 93 mW

Carla Sella (carla-sella) wrote :

Hibernate/Resume smoke test : failed with message
PM non enough free swap.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel currently in the release pocket than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.17

Today I updated My Oneiric Beta 1 on my laptop with all the updates.
I did the "Extended Suspend/Resume test" on it and:

*** TEST 1 -- suspend triggered via dbus message
did not work and got message:
SUSPEND FAILED, did not go to sleep

*** TEST 2 -- suspend with AC disconnected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 3 -- suspend with AC connected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 4 -- loss of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 5 -- return of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-11.18
Download full text (3.6 KiB)

Dear Brad,
I done the tests with the latest updates done today of Oneiric beta 1.
This is the output of lsb_release -a and uname -a:

root@letozaf-HP-G62-Notebook-PC:/home/letozaf# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu oneiric (development branch)
Release: 11.10
Codename: oneiric
root@letozaf-HP-G62-Notebook-PC:/home/letozaf#

root@letozaf-HP-G62-Notebook-PC:/home/letozaf# uname -a
Linux letozaf-HP-G62-Notebook-PC 3.0.0-11-generic #18-Ubuntu SMP Tue Sep 13 23:38:01 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
root@letozaf-HP-G62-Notebook-PC:/home/letozaf#

Besides the five tests indicated in comment #60 I also have these results for the other tests:

*** TEST 6 -- battery drain during suspend
*** calculates overall power drain during a long-term suspend
*** please ensure your AC cord is detached
*** machine will suspend for 20 minutes
*** press return when ready

SUSPEND FAILED, did not go to sleep
before: 3968 mWh
after: 4032 mWh
consumed: -64 mW
sleep seconds: 1236 sec
overall usage: -186 mW

*** TEST 7 -- 30 iteration variable delay suspend/resume stress test
*** please ensure your AC cord is attached

*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAILED, did not go to sleep
wait for 30 seconds
delay 28 ...
SUSPEND FAILED, did not go to sleep
wait for 28 seconds
delay 26 ...
SUSPEND FAILED, did not go to sleep
wait for 26 seconds
delay 24 ...
SUSPEND FAILED, did not go to sleep
wait for 24 seconds
delay 22 ...
SUSPEND FAILED, did not go to sleep
wait for 22 seconds
delay 20 ...
SUSPEND FAILED, did not go to sleep
wait for 20 seconds
delay 18 ...
SUSPEND FAILED, did not go to sleep
wait for 18 seconds
delay 16 ...
SUSPEND FAILED, did not go to sleep
wait for 16 seconds
delay 14 ...
SUSPEND FAILED, did not go to sleep
wait for 14 seconds
delay 12 ...
SUSPEND FAILED, did not go to sleep
wait for 12 seconds
delay 10 ...
SUSPEND FAILED, did not go to sleep
wait for 10 seconds
delay 8 ...
SUSPEND FAILED, did not go to sleep
wait for 8 seconds
delay 6 ...
SUSPEND F...

Read more...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Carla Sella (carla-sella) wrote :

Also the "Hibernate/Resume smoke test (to be done on installed systems only, not live environments)" test fails, the screen goes blank for a fiew seconds and then the password screen is displayed, the laptop does not hibernate.

http://testcases.qa.ubuntu.com/System/SuspendResume

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
importance: Medium → Undecided

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19

I'm testing Oneiric Beta 2 with all updates applied and I'm having the same problem with the "Hibernate/Resume smoke test (to be done on installed systems only, not live environments)" test fails, the screen goes blank for a fiew seconds and then the password screen is displayed, the laptop does not hibernate.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Carla Sella (carla-sella) wrote :

Test1 failed:

*** TEST 1 -- suspend triggered via dbus message
did not work and got message:
SUSPEND FAILED, did not go to sleep

The other tests, seemed to work but on my screen got this output:

*** TEST 2 -- suspend with AC disconnected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 3 -- suspend with AC connected
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 4 -- loss of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

*** TEST 5 -- return of AC while suspended
seemed to work but I still got the message:
SUSPEND FAILED, did not go to sleep

Carla Sella (carla-sella) wrote :

*** TEST 6 -- battery drain during suspend
*** calculates overall power drain during a long-term suspend
*** please ensure your AC cord is detached
*** machine will suspend for 20 minutes
*** press return when ready

SUSPEND FAILED, did not go to sleep
before: 3968 mWh
after: 3936 mWh
consumed: 32 mW
sleep seconds: 1236 sec
overall usage: 93 mW

*** TEST 7 -- 30 iteration variable delay suspend/resume stress test
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAILED, did not go to sleep
wait for 30 seconds
delay 28 ...
SUSPEND FAILED, did not go to sleep
wait for 28 seconds
delay 26 ...
SUSPEND FAILED, did not go to sleep
wait for 26 seconds
delay 24 ...
SUSPEND FAILED, did not go to sleep
wait for 24 seconds
delay 22 ...
SUSPEND FAILED, did not go to sleep
wait for 22 seconds
delay 20 ...
SUSPEND FAILED, did not go to sleep
wait for 20 seconds
delay 18 ...
SUSPEND FAILED, did not go to sleep
wait for 18 seconds
delay 16 ...
SUSPEND FAILED, did not go to sleep
wait for 16 seconds
delay 14 ...
SUSPEND FAILED, did not go to sleep
wait for 14 seconds
delay 12 ...
SUSPEND FAILED, did not go to sleep
wait for 12 seconds
delay 10 ...
SUSPEND FAILED, did not go to sleep
wait for 10 seconds
delay 8 ...
SUSPEND FAILED, did not go to sleep
wait for 8 seconds
delay 6 ...
SUSPEND FAILED, did not go to sleep
wait for 6 seconds
delay 4 ...
SUSPEND FAILED, did not go to sleep
wait for 4 seconds
delay 2 ...
SUSPEND FAILED, did not go to sleep
wait for 2 seconds

*** Please report your results on the Ubuntu WIKI:
    https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

      Battery Consumption: 93 mW

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Download full text (4.3 KiB)

I'm having the same problems with Oneiric final with all updates applied.

This script will attempt to suspend and resume your computer a number of times.
Should the machine fail to resume, first attempt to manually resume it. If
that fails power your system off and on which will generate an apport bug
report automatically.

Press CTRL-C now to abort testing ...

*** TEST 1 -- suspend triggered via dbus message
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds
*** press return when ready

SUSPEND FAILED, did not go to sleep
test 1 did not work

*** TEST 2 -- suspend with AC disconnected
*** please ensure your AC cord is detached
*** machine will suspend for 20 seconds
*** press return when ready

test 2 worked but got message:
SUSPEND FAILED, did not go to sleep

*** TEST 3 -- suspend with AC connected
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds
*** press return when ready

test 3 worked but got message:
SUSPEND FAILED, did not go to sleep

*** TEST 4 -- loss of AC while suspended
*** please remove the AC cord while the machine is suspended
*** machine will suspend for 20 seconds
*** press return when ready

test 4 worked but got message:
SUSPEND FAILED, did not go to sleep

*** TEST 5 -- return of AC while suspended
*** please insert the AC cord while the machine is suspended
*** machine will suspend for 20 seconds
*** press return when ready

test 5 worked but got message:
SUSPEND FAILED, did not go to sleep

*** TEST 6 -- battery drain during suspend
*** calculates overall power drain during a long-term suspend
*** please ensure your AC cord is detached
*** machine will suspend for 20 minutes
*** press return when ready

test 6 worked and got this output:
SUSPEND FAILED, did not go to sleep
before: 4096 mWh
after: 4096 mWh
consumed: 0 mW
sleep seconds: 1236 sec
overall usage: 0 mW

*** TEST 7 -- 30 iteration variable delay suspend/resume stress test
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAIL...

Read more...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Carla Sella (carla-sella) wrote :

Also Hibernate/Resume smoke test (to be done on installed systems only, not live environments)

Case ID: snr-003

(http://testcases.qa.ubuntu.com/System/SuspendResume) does not work, the screen goes black for a fiew seconds, more or less 15 and then password is required and you go back to the users session.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Carla Sella (carla-sella) wrote :
Download full text (5.4 KiB)

I installed the kernel downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2011-10-19-oneiric/linux-headers-3.1.0-999-generic_3.1.0-999.201110190711_amd64.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2011-10-19-oneiric/linux-headers-3.1.0-999_3.1.0-999.201110190711_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2011-10-19-oneiric/linux-image-3.1.0-999-generic_3.1.0-999.201110190711_amd64.deb

I installed it and rebooted my laptop selecting in the boot menu the new kernel.

The Suspend/Resume smoke test - Case ID: snr-001 (http://testcases.qa.ubuntu.com/System/SuspendResume) does not work, the screen goes black the laptop seems suspended, but as you move the mouse you get the prompt for password and you go back to your session but network is not working anymore, can't activate it had to restart network manager from command line.

The Extended Suspend/Resume test - Case ID: snr-002 does not work:

letozaf@HP-G62-Notebook-PC:~$ sudo /usr/share/checkbox/scripts/suspend_test --full
This script will attempt to suspend and resume your computer a number of times.
Should the machine fail to resume, first attempt to manually resume it. If
that fails power your system off and on which will generate an apport bug
report automatically.

Press CTRL-C now to abort testing ...

*** TEST 1 -- suspend triggered via dbus message
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds
*** press return when ready

test1 did not work
SUSPEND FAILED, did not go to sleep

*** TEST 2 -- suspend with AC disconnected
*** please ensure your AC cord is detached
*** machine will suspend for 20 seconds
*** press return when ready

test2 did not work
SUSPEND FAILED, did not go to sleep

*** TEST 3 -- suspend with AC connected
*** please ensure your AC cord is attached
*** machine will suspend for 20 seconds

test 3 failed
*** SUSPEND FAILED, did not go to sleep

*** TEST 4 -- loss of AC while suspended
*** please remove the AC cord while the machine is suspended
*** machine will suspend for 20 seconds
*** press return when readyress return when ready

Test 4 : laptop did not suspend, so I did not remove AC cord

SUSPEND FAILED, did not go to sleep
*** WARNING: AC power not in expected state (0) after test

*** TEST 5 -- return of AC while suspended
*** please insert the AC cord while the machine is suspended
*** machine will suspend for 20 seconds
*** press return when ready

Test 5: laptop did not suspend, but I inserted AC cord

SUSPEND FAILED, did not go to sleep

*** TEST 6 -- battery drain during suspend
*** calculates overall power drain during a long-term suspend
*** please ensure your AC cord is detached
*** machine will suspend for 20 minutes
*** press return when ready

Test 6 failed (test lasted only a few seconds, not a minute)
SUSPEND FAILED, did not go to sleep
before: 1152 mWh
after: 1120 mWh
consumed: 32 mW
sleep seconds: 30 sec
overall usage: 3840 mW
WARNING: the suspend was less than 20 minutes
         to get reliable numbers increase the sleep time

*** TEST 7 -- 30 iteration variable delay suspend/resume stress test
*** please ensure your AC cord is attached
*** machine will susp...

Read more...

tags: removed: needs-upstream-testing
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: kernel-bug-exists-upstream
Carla Sella (carla-sella) wrote :

At the moment bugzilla.kernel.org is not available as there has been a recent security breach in kernel.org and the different kernel.org systems will be brought up over the next few weeks.
I suppose i have to wait, if you have an alternative please let me know.

Joseph Salisbury (jsalisbury) wrote :

Yes, it appears that bugzilla.kernel.org is still unavailable. One alternative would be to report this directly to the subsystem maintainer or to the Linux Kernel Mailing List - <email address hidden>

Joe Areeda (areeda) wrote :

I am getting the same error messages but slightly different behavior.
I get "SUSPEND FAILED, did not go to sleep" but it seems like printing that message puts the computer to sleep. I assume on the previous test.

On the hibernate smoke test the laptop does hibernate for a short time and restarts despite the error message. On the sleep tests it doesn't seem to restart by itself.

I don't really understand what the expected behavior is from the test description.

Carla Sella (carla-sella) wrote :

I've reported the bug upstream on LKML. I will give you the link as soon as it appears.

Carla Sella (carla-sella) wrote :

I ran a test on kernel 3.2-rc7 but the problem is not solved yet, I wrote this mail to kernel.org:

http://marc.info/?l=linux-kernel&m=132578717805234&w=2

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/752881

tags: added: laptop-testing
tags: added: bot-stop-nagging
removed: kernel-request-3.0.0-11.17 kernel-request-3.0.0-11.18 kernel-request-3.0.0-12.19 kernel-request-3.0.0-12.20
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Triaged → Incomplete
Carla Sella (carla-sella) wrote :

@Christofer: Model: G62-120EL Product: VY394EA#ABZ

tags: added: bios-outdated-f.37
summary: - suspend triggered via dbus message on laptop fails
+ [HP HP G62-120EL Notebook PC] Suspend triggered via dbus message on
+ laptop fails
summary: - [HP HP G62-120EL Notebook PC] Suspend triggered via dbus message on
- laptop fails
+ [HP G62-120EL Notebook PC] Suspend triggered via dbus message on laptop
+ fails
Carla Sella (carla-sella) wrote :
Download full text (3.2 KiB)

Hello Christofer,
I updated my BIOS to F.37, but the test still fails:

letozaf@letozaf-HP-G62-Notebook-PC:~$ sudo /usr/share/checkbox/scripts/suspend_test --full
This script will attempt to suspend and resume your computer a number of times.
Should the machine fail to resume, first attempt to manually resume it. If
that fails power your system off and on which will generate an apport bug
report automatically.

Press CTRL-C now to abort testing ...

*** TEST 1 -- suspend triggered via dbus message
*** machine will suspend for 20 seconds
*** press return when ready

SUSPEND FAILED, did not go to sleep
*** no BATTERY detected ac tests skipped ...
*** no BATTERY detected power test skipped ...

*** TEST 2 -- 30 iteration variable delay suspend/resume stress test
*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAILED, did not go to sleep
wait for 30 seconds
delay 28 ...
SUSPEND FAILED, did not go to sleep
wait for 28 seconds
delay 26 ...
SUSPEND FAILED, did not go to sleep
wait for 26 seconds
delay 24 ...
SUSPEND FAILED, did not go to sleep
wait for 24 seconds
delay 22 ...
SUSPEND FAILED, did not go to sleep
wait for 22 seconds
delay 20 ...
SUSPEND FAILED, did not go to sleep
wait for 20 seconds
delay 18 ...
SUSPEND FAILED, did not go to sleep
wait for 18 seconds
delay 16 ...
SUSPEND FAILED, did not go to sleep
wait for 16 seconds
delay 14 ...
SUSPEND FAILED, did not go to sleep
wait for 14 seconds
delay 12 ...
SUSPEND FAILED, did not go to sleep
wait for 12 seconds
delay 10 ...
SUSPEND FAILED, did not go to sleep
wait for 10 seconds
delay 8 ...
SUSPEND FAILED, did not go to sleep
wait for 8 seconds
delay 6 ...
SUSPEND FAILED, did not go to sleep
wait for 6 seconds
delay 4 ...
SUSPEND FAILED, did not go to sleep
wait for 4 seconds
delay 2 ...
SUSPEND FAILED, did not go to sleep
wait for 2 seconds

*** Please report your results on the Ubuntu WIKI:
    https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

Here is the output of sudo dmidecode -s bios-release-date:

sudo dmidecode -s bios-version && sudo dmidecode ...

Read more...

tags: added: latest-bios-f.37
removed: bios-outdated-f.37
Carla Sella (carla-sella) wrote :

Christopher, I installed the latest daily development release of Ubuntu (Trusty Tahr) installed all updates and lanched the test again, but nothing changes I have the same exact behavior.
I will test the latest upstream kernel and let you know.

Carla Sella (carla-sella) wrote :

Christopher, I installed the latest upstream kernel: v3.13-rc2-trusty but everything is just the same the suspend_test --full fails.

tags: added: kernel-bug-exists-upstream-v3.13-rc2-trusty
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: trusty
tags: added: kernel-bug-exists-upstream-v3.13-rc2
removed: kernel-bug-exists-upstream-v3.13-rc2-trusty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Carla Sella (carla-sella) wrote :

Christopher, here is cat /proc/acpi/wakeup, will do 4 just next.

Carla Sella (carla-sella) wrote :

Christopher, here is 4 (dmesg.txt).
Suspension worked, after suspension I pressed enter and the PC resumed.
The "suspend_test --full" fails but my PC can suspend and resume.

Carla, if you can suspend successfully in the standard methods (ex. GUI or sudo pm-suspend) but not via checkbox, it would seem the checkbox script is the issue. Sending to checkbox (Ubuntu) for review.

affects: linux (Ubuntu) → checkbox (Ubuntu)
Changed in checkbox (Ubuntu):
importance: Medium → Low
status: Incomplete → New
Daniel Manrique (roadmr) wrote :

Hello,

Thanks for reporting this bug about Checkbox. Ubuntu 11.04 reached end of life and is unsupported as of October 28, 2012. To ensure this bug is still relevant, or close it if it's not anymore, would it be possible for you to try this procedure with the latest version of Ubuntu and update the report with your findings? The suspend script has evolved quite a bit since then so this may no longer be an issue.

I'll set as incomplete pending your response.

Thanks again!

Changed in checkbox (Ubuntu):
status: New → Incomplete
Daniel Manrique (roadmr) wrote :

My bad for not checking the earlier comments, apologies.

Still, since the versions of checkbox reported in this script seem a bit outdated, could you please confirm the version of ubuntu you're using, as well as the version of checkbox you have installed?

Carla Sella (carla-sella) wrote :

I am using Ubuntu 14.04 Trusty with all updates applied.
Checkbox is version 0.16.7.

Daniel Manrique (roadmr) wrote :

Thanks for the report, the script is very outdated and it's just not working anymore, first the dbus method fails to suspend the system (this is around line 140 of the script), but even if I change that to use pm-suspend, the loop starting around line 157 is suspect and fails to find the expected string indicating resume is complete ("Back to C"). Looking at output from a recent (3.8.0) kernel it doesn't even print that string anymore.

I checked and there are no checkbox jobs using this script anymore, which leads me to believe we stopped using it at some point but neglected removing it.

My recommendation would be removing the script from Checkbox entirely, as it's broken due to bitrot.

Carla, would you be OK with this approach? to clarify, checkbox has newer and better fwts-based suspend tests (see suspend/suspend_advanced), so we do provide for testing this functionality, just not with the old script.

I'll set to triaged but wait for the original reporter's opinion before pulling the trigger on any changes.

Changed in checkbox (Ubuntu):
status: Incomplete → Triaged
assignee: nobody → Daniel Manrique (roadmr)
Changed in checkbox:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Daniel Manrique (roadmr)
milestone: none → 2013-dec-20
Carla Sella (carla-sella) wrote :

@Daniel: ok It's fine for me.

Daniel Manrique (roadmr) on 2013-12-06
Changed in checkbox:
status: Triaged → In Progress
Changed in checkbox (Ubuntu):
status: Triaged → In Progress
Daniel Manrique (roadmr) on 2013-12-18
Changed in checkbox:
status: In Progress → Fix Committed
Changed in checkbox (Ubuntu):
status: In Progress → Fix Committed
Daniel Manrique (roadmr) on 2013-12-20
Changed in checkbox:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package checkbox - 0.17.4ubuntu4

---------------
checkbox (0.17.4ubuntu4) trusty; urgency=low

  * Ignore some build-depends on a few architectures where they're
    unavailable.
  * Declare specific architectures for which the checkbox-gui binary package
    can be built.
  * Make rules file conditionally build, install and package checkbox-gui
    files only on supported archs.
  * Removed stray lintian override and .install files for obsolete packages
 -- Daniel Manrique <email address hidden> Thu, 13 Feb 2014 11:09:48 -0500

Changed in checkbox (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.