From: Con Kolivas <kernel@kolivas.org>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Nathan Lynch <nathanl@austin.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
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>
Subject: Re: CPU hotplug broken in 2.6.8-rc2 ?
Date: Thu, 05 Aug 2004 07:07:26 +1000 [thread overview]
Message-ID: <4111500E.90304@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0408041048350.19619@montezuma.fsmlabs.com>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Zwane Mwaikambo wrote:
> On Tue, 3 Aug 2004, Nathan Lynch wrote:
>
>
>> __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.
>
>
> It could have something to do with the staircase scheduler, Con, got any
> wise words?
Doesn't this bug report say 2.6.8-rc2? It's mm2 that has staircase.
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-08-04 21:09 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
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 [this message]
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=4111500E.90304@kolivas.org \
--to=kernel@kolivas.org \
--cc=dipankar@in.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--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