[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200703150113.53212.ak@suse.de>
Date: Thu, 15 Mar 2007 01:13:53 +0100
From: Andi Kleen <ak@...e.de>
To: Andrew Morton <akpm@...ux-foundation.org>,
Leroy van Logchem <leroy.vanlogchem@...elft.nl>
Cc: linux-kernel@...r.kernel.org, Roland McGrath <roland@...hat.com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
On Thursday 15 March 2007 02:01, Andrew Morton wrote:
> > On Wed, 14 Mar 2007 17:52:01 +0000 (UTC) Leroy van Logchem <leroy.vanlogchem@...elft.nl> wrote:
> > Leroy van Logchem <leroy.vanlogchem <at> wldelft.nl> writes:
> >
Where does it hang exactly? Do you have a boot log?
> > > > > None whatsoever. Three people are reporting this and it's a drop-dead
> > > > > showstopper for a 2.6.21 release so we just have to wait until someone
> > > > > wakes up and thinks about it.
> > >
> > > The topic should be "when CONFIG_HIGHMEM64G=y" imo.
> > >
> > > I'll try to do my first bi-sect today.
>
> Thanks. Please always do reply-to-all. Cc's restored (and added..)
>
> > Bisecting went well, after 13 compiles this commit was found:
> >
> > a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f is first bad commit
> > commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f
> > Author: Roland McGrath <roland@...hat.com>
> > Date: Fri Jan 26 00:56:46 2007 -0800
Can you please double check this by trying with/without again -- sometimes bisects go bad.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists