public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux•vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, paulus@samba•org, anton@samba•org
Subject: Re: BUG: scheduling while atomic: swapper/0/0x00000002
Date: Mon, 28 Jun 2010 09:49:06 -0700	[thread overview]
Message-ID: <20100628164906.GA6667@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100610010854.GA11432@linux.vnet.ibm.com>

On Wed, Jun 09, 2010 at 06:08:54PM -0700, Paul E. McKenney wrote:
> On Thu, Jun 10, 2010 at 09:20:08AM +1000, Benjamin Herrenschmidt wrote:
> > On Wed, 2010-06-09 at 14:52 -0700, Paul E. McKenney wrote:
> > > Hello!
> > > 
> > > I get the following during boot on a 16 CPU Power box.  Thoughts?
> > > (/proc/config attached)
> > 
> > Wow... looks like the preempt count of the idle task got busted or
> > something ... how reproduceable ? Something like a record of previous
> > interrupts might be useful..
> 
> I have seen it only once, but it did get my attention.  I will try running
> it again this evening when/if kernel-ml8 is free again.  2.6.35-rc2,
> I should have mentioned.

And it does appear to be reproducible perhaps 50% of boots running
CONFIG_PREEMPT on kernel-ml8.  I have not yet seen it on any other system.
Do you have a patch to instrument the interrupts so as to get the info
you need, or should I improvise?

 							Thanx, Paul

  reply	other threads:[~2010-06-28 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 21:52 BUG: scheduling while atomic: swapper/0/0x00000002 Paul E. McKenney
2010-06-09 23:20 ` Benjamin Herrenschmidt
2010-06-10  1:08   ` Paul E. McKenney
2010-06-28 16:49     ` Paul E. McKenney [this message]
2010-06-28 21:29       ` Benjamin Herrenschmidt

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=20100628164906.GA6667@linux.vnet.ibm.com \
    --to=paulmck@linux$(echo .)vnet.ibm.com \
    --cc=anton@samba$(echo .)org \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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