ThinkPad T510 Does Not Resume After Suspend to Ram

[Tom Gelinas]

Under Ubuntu Kernel Kernel 2.6.32-12:
The device does not properly resume after suspend to ram while running X server with nv or nVidia drivers.
It is sometimes possible to regain control using Alt+SysRq+K or switching VTs and blindly typing.
The device does not resume after suspend to ram while using text mode
Kern.log reports failure to wake. Backtraces and ACPI Debug "Magic Number" hashes are included.
[ 1.116605] hash matches /build/buildd/linux-2.6.32/drivers/base/power/main.c:430
[ 1.116733] thermal LNXTHERM:01: hash matches

Under Mainline Kernel Kernel 2.6.33-999 08/02/10:
The device resumes after suspend to ram while using text mode, but Kern.log reports failure to wake.
It does not resume after suspend with running x-server
 Backtraces and ACPI Debug "Magic Number" hashes are included.
[ 1.369547] hash matches /home/kernel-ppa/mainline/build/drivers/base/power/main.c:514

No driver is loaded for the following hardware under either kernel:
Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06)
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 06)

Core i5 CPU State C2 is supported under 2.6.33, but not under Ubuntu kernel 2.6.32-12

How should this be reported upstream? Is the problem the lack of drivers for those devices, or is it a separate issue?

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
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: o 2003 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2420000 irq 17'
   Mixer name : 'Conexant ID 5069'
   Components : 'HDA:14f15069,17aa218b,00100301'
   Controls : 6
   Simple ctrls : 4
Date: Tue Feb 9 10:52:47 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b20b8c50-eabc-49c0-8f4f-b9e21ea7d49d
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
Lsusb:
 Bus 002 Device 002: ID 8087:0020
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 17ef:480f Lenovo
 Bus 001 Device 002: ID 8087:0020
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 4313CTO
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-12-generic 2.6.32-12.17 [modified: boot/config-2.6.32-12-generic]
ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-12-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro text
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.29
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-12-generic x86_64
WifiSyslog:
 Feb 9 10:50:16 oo kernel: [ 1808.835812] __ratelimit: 9 callbacks suppressed
 Feb 9 10:50:16 oo kernel: [ 1808.835817] type=1505 audit(1265730616.500:15): operation="profile_replace" pid=4037 name="/sbin/dhclient3"
 Feb 9 10:50:16 oo kernel: [ 1808.836749] type=1505 audit(1265730616.500:16): operation="profile_replace" pid=4037 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
 Feb 9 10:50:16 oo kernel: [ 1808.837273] type=1505 audit(1265730616.500:17): operation="profile_replace" pid=4037 name="/usr/lib/connman/scripts/dhclient-script"
dmi.bios.date: 12/22/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6MET42WW (1.05 )
dmi.board.name: 4313CTO
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:bvr6MET42WW(1.05):bd12/22/2009:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4313CTO
dmi.product.version: ThinkPad T510
dmi.sys.vendor: LENOVO

[Tom Gelinas (tomgelinas)]

Using Ubuntu Kernel:
Here, I boot into text mode and then run GDM. The system suspends, wakes to corrupted screen with colored blocks. Alt+sysrq+k kills VT7 and restarts GDM. Display functions. GDM service is then stopped, xorg.conf is deleted so nv driver will be used. GDM is run, system suspends. System wakes to Lenovo BIOS screen, which does not advance.

[Tom Gelinas (tomgelinas)]

The main concern here is that the system cannot properly resume to text mode. It does a better job with the upstream kernel, which is still unstable.

[Jeremy Foshee (jeremyfoshee)]

added resume tag and Importance Medium

-JFo