From: Peter Zijlstra <peterz@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
gregkh@linuxfoundation.org, rjw@sisk.pl
Subject: Re: Regression in v3.4-rc0 " BUG: soft lockup - CPU#0 stuck for 29s! [migration/0:6]..[<ffffffff810d3b8b>] stop_machine_cpu_stop+0x7b/0xf"
Date: Wed, 21 Mar 2012 17:30:32 +0100 [thread overview]
Message-ID: <1332347432.18960.497.camel@twins> (raw)
In-Reply-To: <1332345420.18960.495.camel@twins>
On Wed, 2012-03-21 at 16:57 +0100, Peter Zijlstra wrote:
> On Wed, 2012-03-21 at 11:26 -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Mar 20, 2012 at 07:53:22PM -0400, Konrad Rzeszutek Wilk wrote:
> > > Seeing this in v3.4-rc0 tree and didn't see that with v3.3:
> >
> > Hey Peter,
> >
> > Git bisection points this to the fault of
> > 5fbd036b552f633abb394a319f7c62a5c86a9cd7 " sched: Cleanup cpu_active madness"
> >
> > thoughts? (also attaching the .config)
>
> Argh.. so when is this? boot? No that's somewhat unexpected. I have one
> report of funnies during a hotplug bash that I'm looking into, but I
> haven't actually been able to reproduce that report myself either.
is arch/x86/xen/smp.c:cpu_bringup() missing a call to
notify_cpu_starting() before doing set_cpu_online()?
Also, shouldn't that also take the ipi_call_lock() around setting the
cpu online?
next prev parent reply other threads:[~2012-03-21 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 23:53 Konrad Rzeszutek Wilk
2012-03-21 15:26 ` Konrad Rzeszutek Wilk
2012-03-21 15:57 ` Peter Zijlstra
2012-03-21 16:30 ` Peter Zijlstra [this message]
2012-03-21 16:32 ` Peter Zijlstra
2012-03-22 3:04 ` Regression in v3.4-rc0 " BUG: soft lockup - CPU#0 stuck for 29s! [migration/0:6]..[<ffffffff810d3b8b>] stop_machine_cpu_stop+0x7b/0xf Konrad Rzeszutek Wilk
2012-03-22 3:04 ` [PATCH] xen/smp: Fix bringup bug in AP code Konrad Rzeszutek Wilk
2012-03-22 9:20 ` Peter Zijlstra
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=1332347432.18960.497.camel@twins \
--to=peterz@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®