From: Nathan Lynch <nathanl@austin.ibm.com>
To: dipankar@in.ibm.com
Cc: V Srivatsa <vatsa@in.ibm.com>,
Joel Schopp <jschopp@austin.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
lkml <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
zwane@linuxpower.ca
Subject: Re: CPU hotplug broken in 2.6.8-rc2 ?
Date: Tue, 03 Aug 2004 16:07:20 -0500 [thread overview]
Message-ID: <1091567239.28036.36.camel@biclops.private.network> (raw)
In-Reply-To: <1091478386.29556.36.camel@pants.austin.ibm.com>
On Mon, 2004-08-02 at 15:26, Nathan Lynch wrote:
> On Mon, 2004-08-02 at 14:38, Nathan Lynch wrote:
> > Could you try on 2.6.8-rc2-mm2 along with this patch? Vatsa had a patch
> > go in that should prevent the crash you are seeing -- the patch below is
> > needed to prevent the same crash in the offline case. This check used
> > to be in load_balance and some other scheduler functions, iirc; does
> > anyone know why they were removed?
>
> Er, I meant to put the check in rebalance_tick, not load_balance.
>
> However, after a few minutes with this, I hit the BUG_ON in the CPU_DEAD
> case in migration_call; not sure whether this is a separate issue.
So, with the cpu_is_offline check in rebalance_tick on top of
2.6.8-rc2-mm2, this is the BUG_ON in migration_call I tend to hit while
hotplugging cpus as quickly as possible while running make -j 40:
case CPU_DEAD:
migrate_all_tasks(cpu);
rq = cpu_rq(cpu);
kthread_stop(rq->migration_thread);
rq->migration_thread = NULL;
/* Idle task back to normal (off runqueue, low prio) */
rq = task_rq_lock(rq->idle, &flags);
deactivate_task(rq->idle, rq);
rq->idle->static_prio = MAX_PRIO;
__setscheduler(rq->idle, SCHED_NORMAL, 0);
task_rq_unlock(rq, &flags);
BUG_ON(rq->nr_running != 0);
I can reproduce this on both ppc64 and i386. Does anyone know why this
is happening?
If I remove the BUG_ON, things seem to go ok, but I doubt that's the
right thing to do.
Nathan
next prev parent reply other threads:[~2004-08-04 6:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 9:49 CPU hotplug broken in 2.6.8-rc2 ? Dipankar Sarma
2004-08-02 9:57 ` Dipankar Sarma
2004-08-02 13:46 ` Anton Blanchard
2004-08-02 19:38 ` Nathan Lynch
2004-08-02 20:26 ` Nathan Lynch
2004-08-03 21:07 ` Nathan Lynch [this message]
2004-08-04 10:06 ` Srivatsa Vaddagiri
2004-08-04 13:12 ` Nathan Lynch
2004-08-04 14:50 ` Zwane Mwaikambo
2004-08-04 21:07 ` Con Kolivas
2004-08-03 0:13 ` Rusty Russell
2004-08-02 16:00 ` Zwane Mwaikambo
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=1091567239.28036.36.camel@biclops.private.network \
--to=nathanl@austin.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rusty@rustcorp.com.au \
--cc=vatsa@in.ibm.com \
--cc=zwane@linuxpower.ca \
/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