From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>,
Leroy van Logchem <leroy.vanlogchem@wldelft.nl>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad
Date: Thu, 15 Mar 2007 01:13:53 +0100 [thread overview]
Message-ID: <200703150113.53212.ak@suse.de> (raw)
In-Reply-To: <20070314170113.9c3c75c7.akpm@linux-foundation.org>
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@wldelft.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@redhat.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
next prev parent reply other threads:[~2007-03-15 0:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703141013.l2EADP6c027144@fire-2.osdl.org>
2007-03-14 12:17 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Andrew Morton
2007-03-14 11:25 ` Randy.Dunlap
2007-03-14 11:30 ` Michal Piotrowski
2007-03-14 12:16 ` Leroy van Logchem
2007-03-14 17:52 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Leroy van Logchem
2007-03-15 1:01 ` Andrew Morton
2007-03-15 0:13 ` Andi Kleen [this message]
2007-03-15 14:12 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad? Leroy van Logchem
2007-03-16 7:41 ` Nilshar
2007-03-15 15:31 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y [Fix CONFIG_COMPAT_VDSO] <- Bad Chuck Ebbert
2007-03-15 15:49 ` Leroy van Logchem
2007-03-15 10:02 ` [Bug 8040] Hang before INIT when CONFIG_HIGHMEM4G=y Nilshar
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=200703150113.53212.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=leroy.vanlogchem@wldelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
/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.