linux-kernel - Re: 2.6.29-rc1: [SOLVED] thinkpad problems during resume

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]

Message-Id: <200901171648.34155.borntraeger@de.ibm.com>
Date:	Sat, 17 Jan 2009 16:48:34 +0100
From:	Christian Borntraeger <borntraeger@...ibm.com>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Jeff Chua <jeff.chua.linux@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	kernel list <linux-kernel@...r.kernel.org>,
	Mike Travis <travis@....com>, Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.29-rc1: [SOLVED] thinkpad problems during resume

> commit e39ad415ac15116df213dfa2aa2a4f1b0857af9c
> Author: Mike Travis <travis@....com>
> Date:   Sun Jan 4 05:18:10 2009 -0800
>
>     cpumask: use work_on_cpu in acpi-cpufreq.c for read_measured_perf_ctrs
>
> makes cpu hotplug working again. Resume from suspend to ram is still broken
> on my Thinkpad. Looks like there is yet another patch to find....
>
> Ingo, Mike: reverting e39ad415ac15116df213dfa2aa2a4f1b0857af9c fixes cpu
> hotplug on my thinkpad. Any idea how to proceed? Should we revert that
> patch in Linus git until we know what was wrong?

I forgot to revert the usb patch.
Current status:
2.6.29-rc2 + 
reverted e39ad415ac15116df213dfa2aa2a4f1b0857af9c (cpumask: use work_on_cpu in 
acpi-cpufreq.c for read_measured_perf_ctrs) + 
reverted a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 (USB: fix up suspend and 
resume for PCI host controllers)

has a working suspend to ram on my T61p. With any of these two patches not 
reverted resume hangs.

Christian
--
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/