Karmic freezes on resume from suspend Thinkpad X200s

[Aviv Ben-Yosef]

I've upgraded to Karmic from Jaunty a few days ago, and since that resuming from suspend cause trouble.
Most of the time, when I close the lid, wait for the laptop (Thinkpad X200s) to suspend and open the lid again, it seems to resume, I see the gnome screensaver password prompt for about a second and then the display changes to tty1 and the system hangs (the suspend led (little moon) is blinking, the keyboard doesn't respond to magic sysrq, no network access to the machine). A hard reboot is the only way to move past it.

I've tried looking at log files for errors, but couldn't see anything that looks like something bad is going on. When I suspend using the Fn+F4 key, or by choosing suspend from System->Shutdown->Suspend, I've yet to see this happen (even if I resumed by closing the lid after the suspend and opening it again), tried about 20 times.

ProblemType: Bug
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: avivb 2532 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa20ff,00100000'
   Controls : 14
   Simple ctrls : 7
Date: Tue Nov 10 09:55:06 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=82124d1a-bfcf-4efc-8277-c8785a544d1f
MachineType: LENOVO 74706EG
Package: linux-image-2.6.31-14-generic-pae 2.6.31-14.48
ProcCmdLine: root=UUID=9228ecfb-f59d-4beb-b280-96c8f24a41e3 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic-pae N/A
 linux-firmware 1.24
SourcePackage: linux
Uname: Linux 2.6.31-14-generic-pae i686
WpaSupplicantLog:

dmi.bios.date: 03/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET42WW (2.06 )
dmi.board.name: 74706EG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn74706EG:pvrThinkPadX200s:rvnLENOVO:rn74706EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 74706EG
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO

[Aviv Ben-Yosef (aviv-by)]

This might be a duplicate indeed, but in my case the displays switches to tty1 and I've successfully resumed without AC at sometimes, unlike the other bug report.

But, if you decide it really is the same issue - please make sure to change that bug's status to Confirmed as well, as currently it's still filed as New - and not being able to use a laptop with resume is really, really terrible (especially given that boot time is now longer than it was with jaunty on my laptop).

[Søren Jacobsen (sej)]

Yes, you're right, sorry. I have changed other bug to "confirmed" but have of course not established that the 2 bugs are in fact duplicates (though it seems likely that they share root cause). I just wanted the 2 bugs to benefit from each other. I have removed the duplication mark again.

[poet_imp (paul-lemmons)]

I am experiencing the same thing. I have not tried it but someone solved this but reverting back to grub from grub2. Could it be a grub issue?

http://ubuntuforums.org/showpost.php?p=8275395&postcount=9

[hamilyon (hamilyon)]

It is the same as mine, https://bugs.launchpad.net/ubuntu/+bug/458836

Problem still persists, i can reproduce it any time i want, i can do anything on my side, including having kernel rebuilt, just lead me.
This bug is of little importance, understandable.

poet_imp, interesting thing, thank you.

[Robert Harrison (rjharrison)]

Reverting from grub2 to grub has also fixed the problem for me on a thinkpad x200t. Previously with grub2, unplugging after suspending reliably caused resume to hang. With grub I've run the experiment at least 10 times with zero occurrence.

[Aviv Ben-Yosef (aviv-by)]

My machine never had grub2 (it's an update from jaunty), so this doesn't seem related.

[Robert Harrison (rjharrison)]

After replacing grub2 with grub problem occurrence is greatly diminished but to my frustration recurred this morning. Thus, problem is indeed elsewhere.

[Jason Gao (jasongao)]

I've had the same experience as Robert; I thought reverting to legacy grub solved it on my X200 tablet, but the problem is still definitely there. I'm still not sure how to reproduce it reliably.

[Søren Jacobsen (sej)]

You can try w/ power chord plugged in and out, respectively. A similar bug (though not exactly the same behaviour) has been filed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/464291

For me, the difference is that my X200 freezes every time if running on battery, and never if I run with power chord attached.

[Daniel Moerner (dmoerner)]

Here's the backtrace, I got it by tail -f'ing /var/log/messages while manually pm-suspending.

Dec 23 22:38:23 skynet kernel: [ 99.592827] PM: Syncing filesystems ... done.
Dec 23 22:38:23 skynet kernel: [ 99.595240] Freezing user space processes ... (elapsed 0.00 seconds) done.
Dec 23 22:38:23 skynet kernel: [ 99.596063] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Dec 23 22:38:23 skynet kernel: [ 99.596125] Suspending console(s) (use no_console_suspend to debug)
Dec 23 22:38:23 skynet kernel: [ 99.681303] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 23 22:38:23 skynet kernel: [ 99.721164] sd 0:0:0:0: [sda] Stopping disk
Dec 23 22:38:23 skynet kernel: [ 101.480144] ehci_hcd 0000:00:1d.7: PCI INT D disabled
Dec 23 22:38:23 skynet kernel: [ 101.480153] uhci_hcd 0000:00:1d.2: PCI INT C disabled
Dec 23 22:38:23 skynet kernel: [ 101.480161] uhci_hcd 0000:00:1d.1: PCI INT B disabled
Dec 23 22:38:23 skynet kernel: [ 101.480168] uhci_hcd 0000:00:1d.0: PCI INT A disabled
Dec 23 22:38:23 skynet kernel: [ 101.480173] pciehp 0000:00:1c.3:pcie04: pciehp_suspend ENTRY
Dec 23 22:38:23 skynet kernel: [ 101.480177] pciehp 0000:00:1c.1:pcie04: pciehp_suspend ENTRY
Dec 23 22:38:23 skynet kernel: [ 101.480181] pciehp 0000:00:1c.0:pcie04: pciehp_suspend ENTRY
Dec 23 22:38:23 skynet kernel: [ 101.480207] HDA Intel 0000:00:1b.0: PCI INT B disabled
Dec 23 22:38:23 skynet kernel: [ 101.500109] ehci_hcd 0000:00:1a.7: PCI INT D disabled
Dec 23 22:38:23 skynet kernel: [ 101.500117] uhci_hcd 0000:00:1a.2: PCI INT C disabled
Dec 23 22:38:23 skynet kernel: [ 101.500125] uhci_hcd 0000:00:1a.1: PCI INT B disabled
Dec 23 22:38:23 skynet kernel: [ 101.500132] uhci_hcd 0000:00:1a.0: PCI INT A disabled
Dec 23 22:38:23 skynet kernel: [ 101.500335] e1000e 0000:00:19.0: PCI INT A disabled
Dec 23 22:38:23 skynet kernel: [ 101.500341] e1000e 0000:00:19.0: PME# enabled
Dec 23 22:38:23 skynet kernel: [ 101.500346] e1000e 0000:00:19.0: wake-up capability enabled by ACPI
Dec 23 22:38:23 skynet kernel: [ 101.540426] heci 0000:00:03.0: PCI INT A disabled
Dec 23 22:38:23 skynet kernel: [ 101.611404] i915 0000:00:02.0: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 101.611458] PM: suspend devices took 2.020 seconds
Dec 23 22:38:23 skynet kernel: [ 101.611631] ehci_hcd 0000:00:1d.7: PME# disabled
Dec 23 22:38:23 skynet kernel: [ 101.890057] ehci_hcd 0000:00:1d.7: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 102.130065] uhci_hcd 0000:00:1d.0: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 102.130267] ehci_hcd 0000:00:1a.7: PME# disabled
Dec 23 22:38:23 skynet kernel: [ 102.390065] ehci_hcd 0000:00:1a.7: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 102.630065] uhci_hcd 0000:00:1a.2: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 102.870064] uhci_hcd 0000:00:1a.0: power state changed by ACPI to D3
Dec 23 22:38:23 skynet kernel: [ 103.230060] ACPI: Preparing to enter system sleep state S3
Dec 23 22:38:23 skynet kernel: [ 104.610195] Disabling non-boot CPUs ...
Dec 23 22:38:23 skynet kernel: [ 104.720037] CPU 1 is now offline
Dec ...

[Daniel Moerner (dmoerner)]

A bit more clarification: I ran "pm-suspend" from the commandline and multiple times got a crash, so I tried doing this. It seemed to crash, and nothing came up in tail -f. However, I just left the computer hanging there for about 20 minutes. When I got back, it was no longer hanging, and I had the full trace sitting in front of me.

[Daniel Moerner (dmoerner)]

I can't reproduce the problem on:

Linux skynet 2.6.33-020633rc1-generic #020633rc1 SMP Fri Dec 18 10:08:58 UTC 2009 x86_64 GNU/Linux

It also suspends/resumes much faster now. Anyone want to try a bisect? :)

[Sumana Harihareswara (sumanah)]

Check https://bugs.launchpad.net/ubuntu/+source/linux/+bug/467877 and check whether the problem occurs when you start on AC power, suspend, remove the power cord, and then try to resume on battery power.

[Brad Figg (brad-figg)]

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.