From: Leroy van Logchem <leroy.vanlogchem@wldelft.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix COMPAT_VDSO regression bug
Date: Thu, 15 Mar 2007 22:47:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20070315T233648-47@post.gmane.org> (raw)
In-Reply-To: 20070315110714.a22581b2.akpm@linux-foundation.org
Andrew Morton <akpm <at> linux-foundation.org> writes:
> > Revert "[PATCH] Fix CONFIG_COMPAT_VDSO"
> > This reverts commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f.
> >
> > Several systems couldnt boot using CONFIG_HIGHMEM64G=y as
> > reported in bug #8040. Reverting the above patch solved the problem.
> I think reverting it is probably the right thing to do, unless we can fix
> it for real quite promptly.
Chuck Ebbert at redhat.com asked:
> Can you please double check this by trying with/without again -- sometimes
bisects go bad.
As requested I started to redo the test but now without git
using kernel.org tars. The results now are, still using the same .config:
linux-2.6.20.tar.gz : bad
linux-2.6.20.1.tar.gz: bad (boot log equal)
linux-2.6.20.2.tar.gz: good
linux-2.6.20.3.tar.gz: good
(triple checked)
Chuck is right, the bisect gone bad.
I asked Nilshar to try these kernels too with:
COMPAT_VDSO=y
CONFIG_HIGHMEM64G=y
He did and says 2.6.20.3 works fine. So only 2.6.20 and 2.6.20.1 had
this 'hang' at boot behavior on my Supermicro 7044 while Nilshar's
machine started working with 2.6.20.3
Reverting avoided imo. I hope more people cheer up who reported bug #8040
and confirm it's fine with the latest stable.
prev parent reply other threads:[~2007-03-15 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 23:38 [PATCH] Fix COMPAT_VDSO regression bug Leroy van Logchem
2007-03-15 1:15 ` Roland McGrath
2007-03-15 3:45 ` [stable] " Greg KH
2007-03-15 8:45 ` Leroy van Logchem
2007-03-15 10:08 ` Leroy van Logchem
2007-03-15 19:07 ` Andrew Morton
2007-03-15 22:47 ` Leroy van Logchem [this message]
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=loom.20070315T233648-47@post.gmane.org \
--to=leroy.vanlogchem@wldelft.nl \
--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