linux-kernel - Re: 2.6.29-rc1 does not resume on Lenove T61

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Jan 2009 18:19:00 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Zdenek Kabelac" <zdenek.kabelac@...il.com>
Cc:	"Maciej Rutecki" <maciej.rutecki@...il.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Henrique de Moraes Holschuh" <hmh@....eng.br>
Subject: Re: 2.6.29-rc1 does not resume on Lenove T61

On Monday 12 January 2009, Zdenek Kabelac wrote:
> 2009/1/12 Rafael J. Wysocki <rjw@...k.pl>:
> > On Monday 12 January 2009, Zdenek Kabelac wrote:
> >> 2009/1/12 Rafael J. Wysocki <rjw@...k.pl>:
> >> > On Sunday 11 January 2009, Zdenek Kabelac wrote:
> >> >> 2009/1/11 Maciej Rutecki <maciej.rutecki@...il.com>:
> >> >> > 2009/1/11 Zdenek Kabelac <zdenek.kabelac@...il.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.

Sure, good idea.  I've been running with this reverted recently.
 
> PS: I'll do the above 'echo' trace later (being busy right now).

That shouldn't be necessary if you can suspend-resume with
7503bfbae89eba07b46441a5d1594647f6b8ab7d reverted and the USB controller
modules unloaded.

Instead, with 7503bfbae89eba07b46441a5d1594647f6b8ab7d reverted, please write
'disabled' to the /sys/devices/.../power/wakeup files of all USB controllers
and see if suspend-resume works in this configuration.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/