From: Mike Travis <travis@sgi.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Pavel Machek <pavel@suse.cz>,
Jeff Chua <jeff.chua.linux@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.29-rc1: [SOLVED] thinkpad problems during resume
Date: Sat, 17 Jan 2009 11:48:18 -0800 [thread overview]
Message-ID: <49723602.4090202@sgi.com> (raw)
In-Reply-To: <200901171648.34155.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
>> commit e39ad415ac15116df213dfa2aa2a4f1b0857af9c
>> Author: Mike Travis <travis@sgi.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
Could you try one more experiment? With your working system, please cherry
pick these commits and try it again?
68564a4... work_on_cpu: don't try to get_online_cpus() in work_on_cpu.
e1d9ec6... work_on_cpu: Use our own workqueue.
6eb714c... cpufreq: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write
>From git://git.kernel.org/pub/scm/linux/kernel/git/travis/linux-2.6-cpus4096-for-ingo.git
If that works, then try and un-revert e39ad415ac and see if it's fixed as well?
(The underlying work_on_cpu() function was causing these problems, but the 1st two
of the above should fix it.)
Thanks!
Mike
next prev parent reply other threads:[~2009-01-17 19:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 8:13 2.6.29-rc1: thinkpad problems during resume Pavel Machek
2009-01-13 11:39 ` Rafael J. Wysocki
2009-01-13 12:42 ` Christian Borntraeger
2009-01-13 13:03 ` AW: " Morten P.D. Stevens
2009-01-13 13:28 ` Pavel Machek
2009-01-13 13:33 ` Jeff Chua
2009-01-16 10:44 ` Pavel Machek
2009-01-16 13:23 ` Jeff Chua
2009-01-17 14:46 ` Christian Borntraeger
2009-01-17 15:48 ` 2.6.29-rc1: [SOLVED] " Christian Borntraeger
2009-01-17 16:49 ` Maciej Rutecki
2009-01-17 19:48 ` Mike Travis [this message]
2009-01-17 23:42 ` Christian Borntraeger
2009-01-19 16:59 ` Mike Travis
2009-01-19 17:09 ` Ingo Molnar
2009-01-13 13:05 ` 2.6.29-rc1: " Pavel Machek
2009-01-13 14:06 ` Rafael J. Wysocki
2009-01-13 14:36 ` Pavel Machek
2009-01-13 14:36 ` Pavel Machek
2009-01-13 15:21 ` Jeff Chua
2009-01-16 14:39 ` Pavel Machek
2009-01-16 22:06 ` Rafael J. Wysocki
2009-01-16 23:56 ` Mike Travis
2009-01-17 0:13 ` Rafael J. Wysocki
2009-01-26 15:44 ` Pavel Machek
2009-01-26 16:40 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49723602.4090202@sgi.com \
--to=travis@sgi.com \
--cc=borntraeger@de.ibm.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.