All of lore.kernel.org
 help / color / mirror / Atom feed
From: MIke Galbraith <efault@gmx.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [k2.6.16-rc1-mm5] kernel BUG at include/linux/mm.h:302!
Date: Thu, 09 Feb 2006 10:50:52 +0100	[thread overview]
Message-ID: <1139478652.7867.9.camel@homer> (raw)
In-Reply-To: <20060209004712.3998e336.akpm@osdl.org>

On Thu, 2006-02-09 at 00:47 -0800, Andrew Morton wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >
> > MIke Galbraith wrote:
> > > Greetings,
> > > 
> > > Excuse me if this is already known, I've been too busy tinkering to read
> > > lkml.
> > > 
> > 
> > It should be fixed as of current -git (not sure about the latest
> > -mm though). It would be good if you could verify that 2.6.16-rc2-git7
> > works OK for you.
> > 
> 
> This was a -mm kernel - how do we know it's not -mm breakage?

It _appears_ to be mm breakage.  I just built/ran rc1 with the same
config, and it works fine.

RL is calling, so I can't dig right this minute... in a couple hours I
hope to be able to start though.

Before I get to the 'what comes next' compile marathon, any likely
candidates?  (or Nick, do you have the supposed fix handy?)

	-Mike


  reply	other threads:[~2006-02-09  9:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  8:24 [k2.6.16-rc1-mm5] kernel BUG at include/linux/mm.h:302! MIke Galbraith
2006-02-09  8:38 ` Nick Piggin
2006-02-09  8:47   ` Andrew Morton
2006-02-09  9:50     ` MIke Galbraith [this message]
2006-02-09 10:11       ` Andrew Morton
2006-02-09 12:44         ` Nick Piggin
2006-02-09 13:53           ` MIke Galbraith
2006-02-09 14:11             ` Nick Piggin
2006-02-09  8:59   ` MIke Galbraith
2006-02-09  8:46 ` Andrew Morton
2006-02-09  9:05   ` MIke Galbraith

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=1139478652.7867.9.camel@homer \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.