From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [x86-tip] overflow in relocation type 11 val 39ffdd0e8690
Date: Fri, 6 Mar 2009 12:18:22 +0100 [thread overview]
Message-ID: <20090306111822.GI21168@elte.hu> (raw)
In-Reply-To: <49B083AC.1070505@kernel.org>
* Tejun Heo <tj@kernel.org> wrote:
> Jaswinder Singh Rajput wrote:
> > On Thu, 2009-03-05 at 22:25 +0100, Ingo Molnar wrote:
> >> * Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> >>
> >>> On latest tip I am getting:
> >>>
> >>> [ 124.169475] overflow in relocation type 11 val 39ffdd0e8690
> >>> [ 124.169508] `msr_debug' likely not compiled with -mcmodel=kernel
> >>> [ 146.582299] overflow in relocation type 11 val 39ffdd0e8690
> >>> [ 146.582299] `msr_debug' likely not compiled with -mcmodel=kernel
> >>> [ 836.653168] overflow in relocation type 11 val 39ffdd0e8690
> >>> [ 836.653201] `msr_debug' likely not compiled with -mcmodel=kernel
> >>>
> >>> But 1d10914bf2c8 was working fine.
> >
> > No it is also not fine :( for percpu.
> >
> >> That's a linker bug - Tejun Cc:-ed.
> >>
> >
> > Problem is basically with 64 bit percpu on 32 bit it is OK. Ahh, Here is
> > the solution:
> >
> > http://lkml.org/lkml/2009/3/3/129
> >
> > because of commit 8ac83757149 of Tejun Heo.
>
> Yeah, patchset almost ready. Please wait a bit more.
>
> Thanks.
Latest tip:master should have your fixes for modules and kernel
text getting farther than ~2GB apart from each other on 64-bit.
Ingo
prev parent reply other threads:[~2009-03-06 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 21:14 [x86-tip] overflow in relocation type 11 val 39ffdd0e8690 Jaswinder Singh Rajput
2009-03-05 21:25 ` Ingo Molnar
2009-03-05 21:33 ` Jaswinder Singh Rajput
2009-03-06 2:00 ` Tejun Heo
2009-03-06 11:18 ` Ingo Molnar [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=20090306111822.GI21168@elte.hu \
--to=mingo@elte.hu \
--cc=efault@gmx.de \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=x86@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