From: Nicholas Piggin <npiggin@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sachin Sant <sachinp@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Balbir Singh <bsingharora@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Tree for Dec 7 (kallsyms failure)
Date: Thu, 8 Dec 2016 15:07:51 +1000 [thread overview]
Message-ID: <20161208150751.19125a3b@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20161208152935.325120da@canb.auug.org.au>
On Thu, 8 Dec 2016 15:29:35 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > On 12/07/16 15:56, Stephen Rothwell wrote:
> > >
> > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> > >>
> > >> I started seeing this yesterday (2016-1206).
> > >> This is on x86_64.
> > >>
> > >> Anybody know about it?
> > >>
> > >> kallsyms failure: relative symbol value 0xffffffff81000000 out of range in relative mode
> > >
> > > I got a similar failure starting a few days ago on my powerpc
> > > allyesconfig build. I was assuming that it was PowerPC specific, but
> > > noone has found a cause yet.
> > >
> >
> > It may just be an invalid randconfig. I modified scripts/kallsyms.c and
> > I see this message:
> > kallsyms failure: relative symbol value 0xffffffff81000000 [symbol: Tstartup_64] out of range in relative mode
> >
> > and it makes sense that startup_64 would (or could) be at 0xffffffff81000000...
> > especially since CONFIG_PHYSICAL_START=0x1000000 and
> > (from Documentation/x86/x86_64/mm.txt)
> > ffffffff80000000 - ffffffff9fffffff (=512 MB) kernel text mapping, from phys 0
> >
> >
> > Ard, what do you think about this?
>
> The similar failure I saw in the powerpc allyesconfig build
>
> kallsyms failure: relative symbol value 0xc000000000000000 out of range in relative mode
>
> was caused by commit
>
> 8ab2ae655bfe ("default exported asm symbols to zero")
>
> which has been reverted in Linus' tree today.
>
Huh, so it seems like the explicit 0 symbols were being picked up as the
kallsyms relative base, putting the 0xc... symbols beyond reach.
prev parent reply other threads:[~2016-12-08 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 6:24 linux-next: Tree for Dec 7 Stephen Rothwell
2016-12-07 23:42 ` linux-next: Tree for Dec 7 (kallsyms failure) Randy Dunlap
2016-12-07 23:56 ` Stephen Rothwell
2016-12-08 2:30 ` Randy Dunlap
2016-12-08 4:29 ` Stephen Rothwell
2016-12-08 5:07 ` Nicholas Piggin [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=20161208150751.19125a3b@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rdunlap@infradead.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).