From: Nathan Lynch <nathanl@austin.ibm.com>
To: vatsa@in.ibm.com
Cc: dipankar@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: Wed, 04 Aug 2004 08:12:05 -0500 [thread overview]
Message-ID: <1091625124.9360.14.camel@biclops.private.network> (raw)
In-Reply-To: <20040804100642.GA20278@in.ibm.com>
On Wed, 2004-08-04 at 05:06, Srivatsa Vaddagiri wrote:
> On Tue, Aug 03, 2004 at 04:07:20PM -0500, Nathan Lynch wrote:
> > BUG_ON(rq->nr_running != 0);
> >
> > I can reproduce this on both ppc64 and i386. Does anyone know why this
> > is happening?
>
> I guess some task is still stuck with the dead CPU. Can you put a breakpoint on the BUG_ON
> and see the ps output (in kdb) to see which task is that when you hit the breakpoint?
The task is always something like cc1 or sh from the build which is
running.
>
> I will also try debugging the 2.6.8-rc2 CPU Hotplug woes as soon as I can.
>
Well, I am seeing this with 2.6.8-rc2-mm2 -- with 2.6.8-rc2-bk13 (plus
the same patch) I cannot reproduce it; I have run the test for 12 hours
without problem.
Nathan
next prev parent reply other threads:[~2004-08-04 13:17 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 [this message]
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=1091625124.9360.14.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