Hi,

I don't have Lenovo T61 but I seem to experience similar resume problem
with Fujitsu Siemens E series notebook except for auto-resume issue
which I have never experienced.

On Mon 12-01-09 13:50:12, Zdenek Kabelac wrote:
> 2009/1/12 Rafael J. Wysocki <rjw@sisk.pl>:
> > On Monday 12 January 2009, Zdenek Kabelac wrote:
> >> 2009/1/12 Rafael J. Wysocki <rjw@sisk.pl>:
> >> > On Sunday 11 January 2009, Zdenek Kabelac wrote:
> >> >> 2009/1/11 Maciej Rutecki <maciej.rutecki@gmail.com>:
> >> >> > 2009/1/11 Zdenek Kabelac <zdenek.kabelac@gmail.com>:
> >> >> >> Hi
> >> >> >>
> >> >> >> I've booted and tested 2.6.29-rc1 (c59765042f53a79a7a65585042ff463b69cb248c)
> >> >> >>
> >> >> >> I've observed that suspend is unusable - it goes to sleep - the sleep
> >> >> >> LED is on. After few secs system turns on back itself - and stays in
> >> >> >> some frozen state
> >> >> >
> >> >> > A have similar situation, one difference: I get blank screen during
> >> >> > resume from suspend to ram. Also sometimes, like You, system turns on
> >> >> > back itself.
> >> >> >
> >> >>
> >> >> So it looks like reverting this commit:
> >> >>
> >> >> http://marc.info/?l=linux-kernel&m=123140019117968&w=4
> >> >> (6fd9086a518d4f14213a32fe6c9ac17fabebbc1e)
> >> >> (which is already a tracked regression)
> >> >> fixes the problem with auto-resume
> >> >>
> >> >> But the problem with deadlock in the resume phase is still there.
> >> >
> >> > Please check if unloading all of the USB controller modules before suspend
> >> > helps.
> >>
> >> I've booted to single mode without   usbcore module (thus any load of
> >> other usb modules fails)
> >> (removed from initramdisk as well)
> >>
> >> This time the resume stops with these 3 lines (I'm using
> >> no_console_suspend kernel option):
> >>
> >> ....
> >> thinkpad_acpi  thinkpad_acpi: EARLY resume
> >> thinkpad_hwmon  thinkpad_hwmon: EARLY resume
> >> Enabling non-boot CPUs...
> >
> > So it seems we have broken CPU hotplug again.
> >
> > Does disabling/enabling CPU1 using
> > /sys/devices/system/cpu/cpu1/online work?
> >
> > If it does, please boot with 'no_console_suspend' in the kernel command line,
> > run:
> >
> > # echo core > /sys/power/pm_test
> > # echo 8 > /proc/sys/kernel/printk
> > # echo mem > /sys/power/state
> >
> > and see what happens (you need to have PM_DEBUG set in the kernel .config).
> >
> > Please send dmesg output generated right after the above (if it works).
> 
> 
> I've taken from another Ingo's thread the idea to revert patch:
> 
> 7503bfbae89eba07b46441a5d1594647f6b8ab7d
> 
> 
> With this patch reverted and  o/e/uhci_hcd & usbhid modules removed
> before pm-suspend
> (usbcore could be loaded, I've not trace which one of those usb
> modules makes the problem)
> my system resumes properl again.

This patch reverted helped to get my machine back up (if I suspend from X)
from s2r but screen is blank until I try to get to text console and
back. 

I have tried to run the test suggested by Rafael, but I am not able to
resume (see attached suspend&resume log with Sysrq+T at the end).  
I can see the following BUG during resume:
[...]
platform dock.1: LATE suspend
platform dock.0: LATE suspend
suspend debug: Waiting for 5 seconds.
BUG: using smp_processor_id() in preemptible [00000000] code: sh/2497
caller is retrigger_next_event+0x12/0xa5
Pid: 2497, comm: sh Tainted: G        W  2.6.29-rc1-resume-fix #8
Call Trace:
 [<c0401662>] ? printk+0xf/0x11
 [<c023148a>] debug_smp_processor_id+0xa2/0xb8
 [<c0137f10>] retrigger_next_event+0x12/0xa5
 [<c0403d79>] ? _spin_unlock+0xf/0x23
 [<c0138059>] hres_timers_resume+0xa/0xc
 [<c013b7ee>] timekeeping_resume+0xf9/0xff
 [<c028d600>] __sysdev_resume+0x14/0x38
 [<c028d645>] sysdev_resume+0x21/0x54
 [<c0291e90>] device_power_up+0xb/0x15
 [<c0146fd2>] suspend_devices_and_enter+0xf7/0x159
 [<c0147189>] enter_state+0x130/0x190
 [<c0147278>] state_store+0x8f/0xa2
 [<c01471e9>] ? state_store+0x0/0xa2
 [<c0229505>] kobj_attr_store+0x1a/0x22
 [<c01b4e07>] sysfs_write_file+0xb4/0xdf
 [<c01b4d53>] ? sysfs_write_file+0x0/0xdf
 [<c017de95>] vfs_write+0x8a/0x12e
 [<c017dfd2>] sys_write+0x3b/0x60
 [<c0102f71>] sysenter_do_call+0x12/0x25
[...]

I am not able to resume from the text console (e.g. with init=/bin/sh
results in the blanks screen) but when I resume from X and try to change
to a text console I cannot see anything (X seems to work correctly).

> 
> Zdenek
> 
> PS: I'll do the above 'echo' trace later (being busy right now).
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Michal Hocko
L3 team 
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic