Thinkpad T410s will not suspend

[BobG]

1. new T410s
2. installed Lucid with the wubi windows installer
3. Suspend initially worked
4. installed lots of stuff (including fprint and thinfinger for the fingerprint reader and then removed when they did not work)
5. did at least one update -- did not get a new kernel update -- there is only one ubuntu kernel on the machine
6. at some point suspend no longer worked. Screen blanks, but stays on. move mouse and the login prompt appears

Debugging Information:
* If I boot with the mainline kernel Linux 2.6.32-02063215-generic and it suspends fine.
* These lines are in my syslog when it tries to sleep...
Sep 20 10:35:08 ubuntu kernel: [ 48.039576] btusb_send_frame: hci0 urb ffff8800b8b04840 submission failed
....
Sep 20 10:35:20 ubuntu kernel: [ 59.621638] usbhid 2-1.8:1.1: suspend error -5
Sep 20 10:35:20 ubuntu kernel: [ 59.621651] pm_op(): usb_dev_suspend+0x0/0x20 returns -5
Sep 20 10:35:20 ubuntu kernel: [ 59.621655] PM: Device 2-1.8 failed to suspend: error -5
Sep 20 10:35:20 ubuntu kernel: [ 59.621658] PM: Some devices failed to suspend
Sep 20 10:35:20 ubuntu kernel: [ 59.624376] PM: resume of devices complete after 2.718 msecs
Sep 20 10:35:20 ubuntu kernel: [ 59.624458] PM: resume devices took 0.000 seconds
Sep 20 10:35:20 ubuntu kernel: [ 59.624464] PM: Finishing wakeup.
Sep 20 10:35:20 ubuntu kernel: [ 59.624465] Restarting tasks ... done.

 usbhid 2-1.8:1 seems to be the N-trig touch screen device ...
Sep 20 10:34:36 ubuntu kernel: [ 15.858557] input: N-trig DuoSense as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input10
Sep 20 10:34:36 ubuntu kernel: [ 15.858664] input: N-trig DuoSense as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input11
Sep 20 10:34:36 ubuntu kernel: [ 15.858725] input: N-trig DuoSense as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/input/input12
Sep 20 10:34:36 ubuntu kernel: [ 15.858847] ntrig 0003:1B96:0001.0002: input,hiddev96,hidraw1: USB HID v1.10 Device [N-trig DuoSense] on usb-0000:00:1d.0-1.8/input1

* I tried blacklisting the hid_ntrig module and rebooted. The touchscreen was inactive but suspend still did not work.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.43
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bobg 1552 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 17'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:14f15069,17aa21a4,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 10
   Simple ctrls : 5
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6UHT30WW-1.11'
   Mixer name : 'ThinkPad EC 6UHT30WW-1.11'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Sep 20 10:35:37 2010
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2901CTO
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=/dev/sda2 loop=/hostname/disks/root.disk ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
SourcePackage: linux
dmi.bios.date: 07/14/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6UET42WW (1.22 )
dmi.board.name: 2901CTO
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:bvr6UET42WW(1.22):bd07/14/2010:svnLENOVO:pn2901CTO:pvrThinkPadT410s:rvnLENOVO:rn2901CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2901CTO
dmi.product.version: ThinkPad T410s
dmi.sys.vendor: LENOVO

[AndresB (baldrichandres)]

Well it looks like something's wrong with thinkpad's suspend, this problem is similar to https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/532374

[Jeremy Foshee (jeremyfoshee)]

Hi BobG,

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

[BobG (bobg-junga)]

 I am terribly sorry. I have to amend some of my earlier statements upon further testing. There is no kernel where it works (more than once). So it sounds like this might have more to do with the other bug.

Note that I am running Thinkpad BIOS version 1.22 and that this machine has a touchscreen.

1. Mainline kernel test - Linux 2.6.32-02063215-generic
Suspend/resume is still broken with the mainline kernel. The symptoms changes however. With the mainline, suspend will work once. Upon resume, every thing seems fine at first but then the left mouse(trackpoint) button stops working. Trying to suspend a second time produces the same result as with the ubuntu kernel -- the screen blanks but stays on -- moving mouse brings up the login box. Mouse left click was still broken. Suspending a third time caused the machine to stop responding with a blank but powered screen -- caps lock light blinks. Also tried booting the "recovery mode" into low res graphics and behavior was similar -- one suspend/resume, second suspend worked but resume failed in the blank screen, caps lock blinking state.

2. Current upstream kernel test - Linux 2.6.36-999-generic
Every suspend attempt results in going back to the login prompt. It looks like the the machine prepares to suspend but then resumes. I tried about 5 times. The machine never became unresponsive, but it never suspended. With this kernel, when suspending it switched to a console and printed dmesg-like messages. None looked relevant to me.

3. Ubuntu kernel test - Linux 2.6.32-24 generic
Every suspend attempt results in going back to the login prompt. It looks like the the machine prepares to suspend but then resumes. I tried about 5 times. The machine never became unresponsive, but it never suspended.

4. Windows 7 test
Works every time, damn them. This seems to suggest that there is not a hardware failure on this particular machine.

5. Fresh Lucid Install test
Every suspend attempt results in going back to the login prompt. It looks like the the machine prepares to suspend but then resumes. I tried about 5 times. The machine never became unresponsive, but it never suspended. I installed from the network installer, chose "Ubuntu Desktop" and tried suspending right after it rebooted into the Ubuntu for the first time. This surprised me because I thought that suspend had worked at some point but I think now it only worked in Windows.

--BobG

[Michael Gratton (michael-b-gratton)]

Hello,

I also have a 410s. On 10.04, I notice the suspend-then-immediately-resume bug, but I can't reproduce it every time. Last time it occured, I did notice this in my syslog:

Oct 10 23:46:30 hermes kernel: [16527.345061] PM: Preparing system for mem sleep
Oct 10 23:46:30 hermes kernel: [16527.345066] Freezing user space processes ... (elapsed 0.00 seconds) done.
Oct 10 23:46:30 hermes kernel: [16527.345748] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Oct 10 23:46:30 hermes kernel: [16527.345780] PM: Entering mem sleep
Oct 10 23:46:30 hermes kernel: [16527.345797] Suspending console(s) (use no_console_suspend to debug)
Oct 10 23:46:30 hermes kernel: [16527.583998] PM: suspend of drv:psmouse dev:serio2 complete after 226.597 msecs
Oct 10 23:46:30 hermes kernel: [16527.758271] PM: suspend of drv:ieee80211 dev:phy0 complete after 174.567 msecs
Oct 10 23:46:30 hermes kernel: [16527.794504] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 10 23:46:30 hermes kernel: [16527.794616] sd 0:0:0:0: [sda] Stopping disk
Oct 10 23:46:30 hermes kernel: [16528.288427] PM: suspend of drv:psmouse dev:serio1 complete after 424.827 msecs
Oct 10 23:46:30 hermes kernel: [16528.882548] PM: suspend of drv:atkbd dev:serio0 complete after 595.187 msecs
** Oct 10 23:46:30 hermes kernel: [16528.882979] pm_op(): usb_dev_suspend+0x0/0x20 returns -16
** Oct 10 23:46:30 hermes kernel: [16528.882981] PM: Device usb1 failed to suspend: error -16
** Oct 10 23:46:30 hermes kernel: [16528.882982] PM: Some devices failed to suspend
Oct 10 23:46:30 hermes kernel: [16529.034781] PM: resume of drv:usb dev:1-1 complete after 111.756 msecs
Oct 10 23:46:30 hermes kernel: [16529.034787] sd 0:0:0:0: [sda] Starting disk
Oct 10 23:46:30 hermes kernel: [16529.156082] PM: resume of devices complete after 273.589 msecs
Oct 10 23:46:30 hermes kernel: [16529.156189] PM: resume devices took 0.270 seconds
Oct 10 23:46:30 hermes kernel: [16529.156197] PM: Finishing wakeup.

See how the 1-1 usb device wakes it up? I think this may be a version of Bug #289252

[Michael Gratton (michael-b-gratton)]

More testing: Yesterday I had two successful suspends in a row, and then the bug occured again. I had the same error with usb. Looking around, now I think this is the same as Bug #631464 The syslog there has the same message about "usb_dev_suspend+0x0/0x20 returns -16".

[Bart Samwel (bart-samwel)]

I have the same problem on my T410. The device usb1 is a usb hub, but the only submodule normally attached to this hub (if you haven't plugged in anything else) is the webcam. Turns out that if I suspend-blacklist the uvcvideo driver by adding a file "uvcvideo.conf" to /etc/pm/config.d with the line "SUSPEND_MODULES=uvcvideo", then things work OK most of the times (except for some other issues that are irrelevant here).

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

[BobG (bobg-junga)]

For anyone researching a similar problem, here is the way I (the OP) resolved the issue.

After not using this notebook for a while, today I did the following and not suspend and resume works (its been through about 7 cycles without problems).

1) updated ubuntu -> reboot -> same problem (no suspend)
2) updated to new Lenovo bios 1.41 -> reboot -> same problem (no suspend)
3) read Bart's message, create the /etc/pm/config.d/uvcvideo.conf file -> reboot -> same problem (no suspend)
4) (re)added the "blacklist hid_ntrig" line to the bottom of /etc/modprobe.d/blacklist.conf -> rebooted -> problem solved (suspend works)

Way back in the beginning I had tried blacklisting hid_ntrig (which is the touchscreen usb device) but it did not solve the problem. so probably one of the first three steps was also needed to solve the problem.

BTW, I can enable the touchscreen by doing "modprobe hid_ntrig" without rebooting. I find as long as its loaded, suspend is broken. I can, however, turn the touch screen off with "modprobe -r hid_ntrig" and then it will suspend without requiring a reboot.

[BobG (bobg-junga)]

woops, "...not suspend and resume works... " should read "...now suspend and resume works"