From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: MIke Galbraith <efault@gmx.de>, 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 23:44:47 +1100 [thread overview]
Message-ID: <43EB393F.1070409@yahoo.com.au> (raw)
In-Reply-To: <20060209021136.410f1128.akpm@osdl.org>
Andrew Morton wrote:
> MIke Galbraith <efault@gmx.de> wrote:
>
>>On Thu, 2006-02-09 at 00:47 -0800, Andrew Morton wrote:
>>>This was a -mm kernel - how do we know it's not -mm breakage?
>>
It's an educated guess. I suppose it could be -mm breakage.
I sent Andrew a patch which tightens up some debug checking, and
that is likely to be causing your BUGs.
>>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?
>
>
> rc2-mm1?
>
>
>> (or Nick, do you have the supposed fix handy?)
>
>
> Yeah, I'm still scratching my head over the mystery fix.
>
>
The mm/swap.c hunk from git 8519fb30e438f8088b71a94a7d5a660a814d3872
is the mystery fix (the mm.h hunk is already in there).
I suppose you'd better verify that -mm works fine with the patch as
well, when you get time.
Thanks,
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-02-09 12:44 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
2006-02-09 10:11 ` Andrew Morton
2006-02-09 12:44 ` Nick Piggin [this message]
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=43EB393F.1070409@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--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