failure to resume after suspending for the second time (Dell Latitude E6510)

[John Steele Scott]

I suspend this laptop by closing the lid. If it is only suspended for a short period (e.g. suspend when I leave the office, go home, have dinner, then resume), it resumes with no problem.

If it is suspended for a long period (e.g. overnight), it fails to resume. When I open the lid, nothing appears to happen for some time (maybe 30 seconds), then the system starts as if it has been rebooted (e.g. the Dell logo appears, grub, etc).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jscott 2072 F.... pulseaudio
                      jscott 3626 F.... OUTLOOK.EXE
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe9660000 irq 22'
   Mixer name : 'IDT 92HD81B1C5'
   Components : 'HDA:111d76d5,1028040b,00100104'
   Controls : 18
   Simple ctrls : 12
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xe3080000 irq 16'
   Mixer name : 'Nvidia ID b'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Tue Jun 8 09:10:31 2010
HibernationDevice: RESUME=UUID=a46482fe-ee03-45c1-9906-0dd0714a9302
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Dell Inc. Latitude E6510
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=/dev/mapper/sda9_crypt ro nomodeset quiet splash
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 03/05/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0N5KHN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/05/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

[Jeremy Foshee (jeremyfoshee)]

Hi John,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[John Steele Scott (toojays)]

In my original report I said that short suspend periods were okay, but longer periods could not be resumed from. I think what is actually the case is that the first resume works okay, but the second time you try to resume, the machine fails to resume (and then reboots). The duration of time for which the machine is suspended does not actually seem to be part of the issue.

Anyway, the good news is that this appears to be fixed in 2.6.35-020635rc1-generic. It does not appear to be fixed in 2.6.34-020634 (couldn't even resume once), or 2.6.33-02063305.

[Sebastian Klus (klus-spam)]

The issue I am having is not exactly the same, but comes quite close. So I add this here instead of opening a new report:

When starting my laptop (HP Pavilion dv6000) with dualboot, everything goes fine until the Ubuntu screen shows up (the Ubuntu text with the dots below, that change from white to red). Then (nearly always; let's say in 7 from 10 cases) the screen simply stays this way - the logon screen is not coming up. I touch the power switch and my laptop shuts down as if turning it off. Then, the second boot, everything works fine. It takes a little longer and the screen flickers one or two times during startup, but first the Ubuntu logo comes up and shortly afterwards, the logon screen and from this moment on everything works normal.

Maybe just to clarify: I always do a complete shutdown when ending my work. No standby or suspend.

Please let me know what files to upload, in case you need anything that might help.

Regards,
Sebastian

[Sebastian Klus (klus-spam)]

One more thing:
This phenomenon occured recently. I am running Ubuntu 10.04 since it was published and everything was fine until a couple of weeks ago. Unfortunately I am not exactly sure when it happened, but my impression is that it takes place since the last kernel update.

uname -a says I am running Linux ubuntu 2.6.32-22-generic #36-Ubuntu SMP; and it's 64bit

[John Steele Scott (toojays)]

Sebastian, I suggest opening a separate bug, your issue sounds quite different to mine. My bug is just about suspend, and seems to be already fixed in kernel 2.6.35-rc1. If you think your bug is a kernel bug, you can run "ubuntu-bug linux-image-2.6.32-22-generic", which will run a program to upload any relevant information when you report your bug.

[John Steele Scott (toojays)]

Unfortunately I have to take back what I said about this being fixed in 2.6.35-rc1. It still fails to resume from sleep sometimes. Where 2.6.32 would reboot on resume, 26.35-rc1 just hangs instead. It does work sometimes, but not always.

[Laurent SION (laurent-sion)]

I have had this issue, solved by the patch "ACPI: Unconditionally set SCI_EN on resume". Read the bug 594837:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/594837

[Brian (x-brian)]

This was also solved for me by the kernel patch in bug 594837.

My problem occurred on a Dell E6410 with Intel Core i7 M620 and nVidia NVS 3100M. I had the same problem--every other suspend/resume failed. When resume failed, I saw the BIOS self-test and got a cold boot into Ubuntu. Additionally, networking was disabled after a failed resume. Right-clicked network-manager and choosing "Enable Networking" fixed tat each time.

[penalvch (penalvch)]

John Steele Scott, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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.

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'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

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