From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: 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>,
Nicholas Piggin <npiggin@gmail•com>,
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:29:35 +1100 [thread overview]
Message-ID: <20161208152935.325120da@canb.auug.org.au> (raw)
In-Reply-To: <90c66e73-f7c9-3d48-04b7-0985cce53382@infradead.org>
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.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-12-08 4:29 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 [this message]
2016-12-08 5:07 ` Nicholas Piggin
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=20161208152935.325120da@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ard.biesheuvel@linaro$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=bsingharora@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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