From: Andrew Morton <akpm@linux-foundation.org>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ak@suse.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23-rc8 (build failure from -rc1)
Date: Tue, 25 Sep 2007 10:02:33 -0700 [thread overview]
Message-ID: <20070925100233.dfe3a37f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1190739421.13955.34.camel@dyn9047017100.beaverton.ibm.com>
On Tue, 25 Sep 2007 09:57:01 -0700 Badari Pulavarty <pbadari@gmail.com> wrote:
> On Mon, 2007-09-24 at 17:46 -0700, Linus Torvalds wrote:
> > Ok, I think I'm getting close to releasing a real 2.6.23. Things seem to
> > have calmed down, and I think Thomas Gleixner may have found the
> > suspend/resume regression that has dogged us for a while, so I'm feeling
> > happy about things.
> >
> > Of course, me feeling happy is usually immediately followed by some nasty
> > person finding new problems, but I'll just ignore that and enjoy the
> > feeling anyway, however fleeting it may be.
>
> I don't want to be the "nasty" person, but one of my machines doesn't
> like 2.6.23-rc8. Infact, 2.6.23-rc1 was the first kernel this is broken.
> (I didn't get hands on this machine till now).
>
> Since my other x86-64 machines are doing fine, I am going to blame it
> on my machine specific config :)
>
> Thanks,
> Badari
>
>
> elm3a242:/usr/src/linux-2.6.23-rc8 # make -j4 bzImage
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> SYSCALL arch/x86_64/vdso/vdso.so
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-
> linux/bin/ld: section .text [ffffffffff700500 -> ffffffffff700797]
> overlaps section .dynstr [ffffffffff7004b8 -> ffffffffff700510]
> collect2: ld returned 1 exit status
> make[1]: *** [arch/x86_64/vdso/vdso.so] Error 1
> make: *** [arch/x86_64/vdso] Error 2
> make: *** Waiting for unfinished jobs....
>
<goes fishing in Andi's tree>
box:/usr/src/25> grep vdso series
x86_64-mm-vdso-text-offset.patch
x86_64-mm-vdso-compat-install-unstripped-copies-on-disk.patch
x86_64-mm-vdso-64bit-install-unstripped-copies-on-disk.patch
fix-discrepancy-between-vdso-based-gettimeofday-and-sys_gettimeofday.patch
x86_64-mm-vdso-text-offset.patch looks likely - can you test it please?
Increase VDSO_TEXT_OFFSET for ancient binutils
For some reason old binutils genertate larger headers so
increase the text offset of the vdso to avoid linker errors.
Signed-off-by: Andi Kleen <ak@suse.de>
---
arch/x86_64/vdso/voffset.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/x86_64/vdso/voffset.h
===================================================================
--- linux.orig/arch/x86_64/vdso/voffset.h
+++ linux/arch/x86_64/vdso/voffset.h
@@ -1 +1 @@
-#define VDSO_TEXT_OFFSET 0x500
+#define VDSO_TEXT_OFFSET 0x600
next prev parent reply other threads:[~2007-09-25 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 0:46 Linux 2.6.23-rc8 Linus Torvalds
2007-09-25 16:57 ` Linux 2.6.23-rc8 (build failure from -rc1) Badari Pulavarty
2007-09-25 17:02 ` Andrew Morton [this message]
2007-09-25 17:22 ` Badari Pulavarty
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=20070925100233.dfe3a37f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=torvalds@linux-foundation.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