public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Michael wang <wangyun@linux.vnet.ibm.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org,
	Ingo Molnar <mingo@redhat.com>,
	acme@ghostprotocols.net, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] sched: tip/master show panic while booting/rebooting
Date: Mon, 24 Feb 2014 20:41:00 -0800	[thread overview]
Message-ID: <20140225044100.GL8264@linux.vnet.ibm.com> (raw)
In-Reply-To: <530C03C6.9080405@linux.vnet.ibm.com>

On Tue, Feb 25, 2014 at 10:45:26AM +0800, Michael wang wrote:
> Hi, Paul
> 
> On 02/25/2014 08:30 AM, Paul E. McKenney wrote:
> [snip]
> > 
> > I don't see an opportunity for load_balance() to loop with interrupts
> > disabled, but maybe I am looking at the wrong code.  The NMI handler
> > looks to me like it is diagnosing rather than being the problem.
> 
> Thanks for the comment :)
> 
> It was a stuck inside pick_next_task_fair(), and we already got one
> solution now ;-)

What I get for too-late reply.  Glad it is fixed!

							Thanx, Paul

> Regards,
> Michael Wang
> 
> > 
> > 							Thanx, Paul
> > 
> >>  [<ffffffff8108a88f>] idle_balance+0x10f/0x1c0
> >>  [<ffffffff8108aa5e>] pick_next_task_fair+0x11e/0x2a0
> >>  [<ffffffff8107bbf3>] ? dequeue_task+0x73/0x90
> >>  [<ffffffff815717fa>] __schedule+0x12a/0x670
> >>  [<ffffffff81571e19>] schedule+0x29/0x70
> >>  [<ffffffff81067daf>] worker_thread+0x1bf/0x370
> >>  [<ffffffff81067bf0>] ? manage_workers+0x160/0x160
> >>  [<ffffffff8106e799>] kthread+0xc9/0xe0
> >>  [<ffffffff8106e6d0>] ? flush_kthread_worker+0xb0/0xb0
> >>  [<ffffffff8157d62c>] ret_from_fork+0x7c/0xb0
> >>  [<ffffffff8106e6d0>] ? flush_kthread_worker+0xb0/0xb0
> >> Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 


      reply	other threads:[~2014-02-25  4:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  5:12 [BUG] sched: tip/master show panic while booting/rebooting Michael wang
2014-02-18 11:22 ` Peter Zijlstra
2014-02-19  3:12   ` Michael wang
2014-02-19 11:57     ` Peter Zijlstra
2014-02-25  0:30 ` Paul E. McKenney
2014-02-25  2:45   ` Michael wang
2014-02-25  4:41     ` Paul E. McKenney [this message]

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=20140225044100.GL8264@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=wangyun@linux.vnet.ibm.com \
    --cc=x86@kernel.org \
    /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