Failure to resume from suspend

[Chase Douglas]

My computer fails to resume from suspend. It seems that a 2.6.36 kernel resolves the issue.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cndougla 1972 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0e00000 irq 47'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1028041a,00100001'
   Controls : 12
   Simple ctrls : 7
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=2efed373-2706-4ea9-b4fb-f791bb73070a
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100405)
MachineType: Dell Inc. Inspiron 1012
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-21-generic root=UUID=3c709a23-d79e-4eda-9014-8e0593c2d2ba ro intel_idle.max_cstate=0 quiet splash usbcore.autosuspend=1
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick ubuntu-une kernel-power suspend resume regression-potential needs-upstream-testing
Uname: Linux 2.6.35-21-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 02/22/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D3J9P
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/22/2010:svnDellInc.:pnInspiron1012:pvrA06:rvnDellInc.:rn0D3J9P:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 1012
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

apport information

[Chase Douglas (chasedouglas)]

After more testing it appears that disabling intel_idle does not fix my resume issue. Upgrading to 2.6.36 does seem to resolve it, however. I'll try to bisect it when I get a chance.

[Dave Conniff (chronniff)]

I can confirm that I haven't been able to resume from suspend since using kernel 2.6.35. I am currently using intel_idle, but it happend when it is disabled as well.....My guess is that this bug is affecting the core i processors, which is why everyone thinks it is intel_idle ....if 2.6.36 does fix the problem, a backport to fix the issue as soon as it is isolated would be much appreciated

[Chase Douglas (chasedouglas)]

Dave, thanks for confirming. My laptop is an Atom N450, which I think is distinct from the new i series of processors, but I could be wrong.

I note with sadness that I had a hang on resume on 2.6.36 once this past week. It's much less prevalent on 2.6.36, and it sometimes does resume on 2.6.35, so I think this may be a race condition.

[Nuno Sucena Almeida (slug-debian)]

I'm having the same issue. After "upgrading" to maverick from lucid, resume stopped working properly, among several other things: I get a black screen, although I sometimes the keyboard is still working, enabling me to reboot the machine.

[Dave Conniff (chronniff)]

interesting.....well if the Atom N450 is using intel_idle it must be a member of the most recent generation of intel processors as the intel_idle driver only works at all on the the most recent generation. I probably shouldn't have said the new core processors, as I knew that the driver was also for the latest xeon generation, so I guess it makes sense that the atoms would benefit as well......It seems that the lenovo s10-3 has the same cpu that you do, and just had a bug fixed in a recent kernel update that caused the laptop to hang on boot with the intel idle driver....so maybe the most recent kernel updates helped you? doesn't help me at all as that I can tell.......I'm running a i7 960...so I guess it's not so important as if I had this problem on a laptop, but it still aggravates me every time I have to do a full boot in the moring.......I blame ubntu if the intel idle turns out to be the problem considering that it is still labeled as experimental in the kernel and the ubuntu team decided that they sould turn it on by default just for the adventure

[Trent Telfer (unnaturalhigh)]

Like the rest of you I am also affected by this bug 3 different systems. Two laptops and One Desktop, all with intel processors. After recent upgrades from Lucid to Maverick each system has various problems resuming from suspend. I haven't had a chance to try 2.6.36 yet but will this weekend and report back here on my findings. Also I should mention that the processors being affected are a Pentium M, Pentium 4 and Core 2 Duo, so that may debunk the i core processor theory. Please let me know if any additional information is needed from any of these systems.

[Joseph Salisbury (jsalisbury)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.