Date: Thu, 11 Mar 2004 23:50:09 -0800
From: Andrew Morton <akpm@osdl.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4-mm1
Message-Id: <20040311235009.212d69f2.akpm@osdl.org>
In-Reply-To: <16465.20264.563965.518274@notabene.cse.unsw.edu.au>
References: <20040310233140.3ce99610.akpm@osdl.org>
	<16465.3163.999977.302378@notabene.cse.unsw.edu.au>
	<20040311172244.3ae0587f.akpm@osdl.org>
	<16465.20264.563965.518274@notabene.cse.unsw.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1009
Lines: 31

Neil Brown <neilb@cse.unsw.edu.au> wrote:
>
> On Thursday March 11, akpm@osdl.org wrote:
> > 
> > Tried adding earlyprintk=vga?
> > 
> > If that works, judicious addition of printks will narrow it down.
> 
> It doesn't.
> 
> I've tried compiling with SMP - no go.
> I've tried with gcc-2.95 (instead of 3.3.2).  Still no go.

Your .config works happily here.

> I thought I might try selectively removing patches, but it isn't clear
> what order the borken-out patches were applied it.
> If you have an ordered list, I can try a binary search.

See the `series' file in the broken-out directory.

> Or if you can suggest some patches that I can try backing out....

Maybe turn off -mregparm?  Or back off the 4g/4g patches?  Maybe they broke
non-4:4 code comehow.

-
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/