From: Andrew Morton <akpm@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: list <linux-pm@lists.linux-foundation.org>,
Dan Kruchinin <dubalom@gmail.com>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
pm@smtp2.linux-foundation.org
Subject: Re: 2.6.21-rc7-mm2 suspend bug. [kernel/kthread.c]
Date: Mon, 30 Apr 2007 00:39:46 -0700 [thread overview]
Message-ID: <20070430003946.b4d856b4.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704292227.45215.rjw@sisk.pl>
On Sun, 29 Apr 2007 22:27:44 +0200 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Sunday, 29 April 2007 21:51, Dan Kruchinin wrote:
> > Hi all.
> >
> > There is a problem on my macbook core duo with suspend.
> > after suspending when i'm trying to 'wake up' my notebook, it seems
> > that it works, but i don't see anything at my monitor. So i have to
> > reboot it to continue my work.
>
> What exactly do you do to suspend?
>
This is due to _cpu_down() calling kthread_bind() in state TASK_RUNNING.
So I was sent the below, including worrisome changelog.
From: Gautham R Shenoy <ego@in.ibm.com>
We are anyway kthread_stop()ping other per-cpu kernel threads after
move_task_off_dead_cpu(), so we can do it with the stop_machine_run thread
as well.
I just checked with Vatsa if there was any subtle reason why they
had put in the kthread_bind() in cpu.c. Vatsa cannot seem to recollect
any and I can't see any. So let us just remove the kthread_bind.
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/cpu.c | 4 ----
1 files changed, 4 deletions(-)
diff -puN kernel/cpu.c~remvoe-kthread_bind-call-from-_cpu_down kernel/cpu.c
--- a/kernel/cpu.c~remvoe-kthread_bind-call-from-_cpu_down
+++ a/kernel/cpu.c
@@ -175,10 +175,6 @@ static int _cpu_down(unsigned int cpu)
/* This actually kills the CPU. */
__cpu_die(cpu);
- /* Move it here so it can run. */
- kthread_bind(p, get_cpu());
- put_cpu();
-
/* CPU is completely dead: tell everyone. Too late to complain. */
if (raw_notifier_call_chain(&cpu_chain, CPU_DEAD, hcpu) == NOTIFY_BAD)
BUG();
_
next prev parent reply other threads:[~2007-04-30 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8f16e2b0704291251l69c1b02ahb9b22370bc468fa1@mail.gmail.com>
2007-04-29 20:27 ` 2.6.21-rc7-mm2 suspend bug. [kernel/kthread.c] Rafael J. Wysocki
[not found] ` <200704292227.45215.rjw@sisk.pl>
2007-04-30 7:39 ` Andrew Morton [this message]
2007-04-30 10:05 ` Gautham R Shenoy
[not found] ` <20070430100535.GA30975@in.ibm.com>
2007-04-30 14:58 ` 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=20070430003946.b4d856b4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dubalom@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=pm@smtp2.linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox