public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: [PATCH] [RSDL-mm 0/6] RSDL cpu scheduler for -mm
Date: Thu, 8 Mar 2007 16:25:05 +1100	[thread overview]
Message-ID: <200703081625.06383.kernel@kolivas.org> (raw)
In-Reply-To: <20070307201502.4e93c5d5.akpm@linux-foundation.org>

On Thursday 08 March 2007 15:15, Andrew Morton wrote:
> On Wed, 7 Mar 2007 18:54:30 -0800 Andrew Morton <akpm@linux-foundation.org> 
wrote:
> > On Wed, 7 Mar 2007 17:43:45 -0800 Andrew Morton 
<akpm@linux-foundation.org> wrote:
> > > On Wed, 7 Mar 2007 12:26:42 +1100
> > >
> > > Con Kolivas <kernel@kolivas.org> wrote:
> > > > What follows is the same patch series that constitutes the RDSL
> > > > "Rotating Staircase DeadLine" cpu scheduler resynced for
> > > > 2.6.21-rc2-mm2.
> > >
> > > Big oops early in boot on x86_64 SMP, in rq_bitmap_error+0x97/0x9f.
> > >
> > > I stubbed it out with a `return MAX_RT_PRIO;' (I think) but it then
> > > oopsed differently.  Before netconsole had come up, no serial console,
> > > no digital camera.
> > >
> > > There's stuff in http://userweb.kernel.org/~akpm/ck/ - you can probably
> > > boot that kernel on your own machine.
> > >
> > > I need to do rc3-mm1 now.  I might find some time to poke at this
> > > further after that, but I have to leave for a week in .jp and it'll be
> > > squeezy, sorry.
> >
> > well it boots os dual pIII and quad powerpc.
>
> It also boots OK on a very similar but somewhat older Nocona machine. 
> Perhaps due to config changes: 
> http://userweb.kernel.org/~akpm/ck/config-ok.txt

Ok I just remembered that not only did I expect the cpu task to never be 
scheduled and it _might_ be scheduled on sched_init, it is actually 
_consciously_ scheduled on hotplug cpu which I have no way of handling at the 
moment. On both your configs I noticed you had hotplug cpu enabled, but 
perhaps it isn't really being used on the more conservative config. So this 
is something I already know I need to handle. Did your ppc that had 
the "bitmap error" have hotplug cpu enabled? It might be an unrelated 
bug^Wphenomenon.

-- 
-ck

  reply	other threads:[~2007-03-08  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07  1:26 [PATCH] [RSDL-mm 0/6] RSDL cpu scheduler for -mm Con Kolivas
2007-03-08  1:43 ` Andrew Morton
2007-03-08  2:54   ` Andrew Morton
2007-03-08  4:15     ` Andrew Morton
2007-03-08  5:25       ` Con Kolivas [this message]
2007-03-08  6:03         ` Andrew Morton
2007-03-08  4:22     ` Con Kolivas
2007-03-09  5:13     ` Con Kolivas

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=200703081625.06383.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@linux-foundation.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.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