* Re: linux-next: Tree for Dec 7 (kallsyms failure) [not found] ` <13d83759-40d3-593b-b53f-f3e75fb05b7a@infradead.org> @ 2016-12-07 23:56 ` Stephen Rothwell 2016-12-08 2:30 ` Randy Dunlap 0 siblings, 1 reply; 4+ messages in thread From: Stephen Rothwell @ 2016-12-07 23:56 UTC (permalink / raw) To: Randy Dunlap Cc: linux-next, linux-kernel, Sachin Sant, Michael Ellerman, Benjamin Herrenschmidt, PowerPC, Nicholas Piggin Hi Randy, 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. -- Cheers, Stephen Rothwell ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: Tree for Dec 7 (kallsyms failure) 2016-12-07 23:56 ` linux-next: Tree for Dec 7 (kallsyms failure) Stephen Rothwell @ 2016-12-08 2:30 ` Randy Dunlap 2016-12-08 4:29 ` Stephen Rothwell 0 siblings, 1 reply; 4+ messages in thread From: Randy Dunlap @ 2016-12-08 2:30 UTC (permalink / raw) To: Stephen Rothwell Cc: linux-next, linux-kernel, Sachin Sant, Michael Ellerman, Benjamin Herrenschmidt, PowerPC, Nicholas Piggin, Ard Biesheuvel On 12/07/16 15:56, Stephen Rothwell wrote: > Hi Randy, > > 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? thanks, -- ~Randy ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: Tree for Dec 7 (kallsyms failure) 2016-12-08 2:30 ` Randy Dunlap @ 2016-12-08 4:29 ` Stephen Rothwell 2016-12-08 5:07 ` Nicholas Piggin 0 siblings, 1 reply; 4+ messages in thread From: Stephen Rothwell @ 2016-12-08 4:29 UTC (permalink / raw) To: Randy Dunlap Cc: linux-next, linux-kernel, Sachin Sant, Michael Ellerman, Benjamin Herrenschmidt, PowerPC, Nicholas Piggin, Ard Biesheuvel, Balbir Singh, Arnd Bergmann, Linus 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: Tree for Dec 7 (kallsyms failure) 2016-12-08 4:29 ` Stephen Rothwell @ 2016-12-08 5:07 ` Nicholas Piggin 0 siblings, 0 replies; 4+ messages in thread From: Nicholas Piggin @ 2016-12-08 5:07 UTC (permalink / raw) To: Stephen Rothwell Cc: Randy Dunlap, linux-next, linux-kernel, Sachin Sant, Michael Ellerman, Benjamin Herrenschmidt, PowerPC, Ard Biesheuvel, Balbir Singh, Arnd Bergmann, Linus 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-08 5:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20161207172432.184970d7@canb.auug.org.au>
[not found] ` <13d83759-40d3-593b-b53f-f3e75fb05b7a@infradead.org>
2016-12-07 23:56 ` linux-next: Tree for Dec 7 (kallsyms failure) Stephen Rothwell
2016-12-08 2:30 ` Randy Dunlap
2016-12-08 4:29 ` Stephen Rothwell
2016-12-08 5:07 ` Nicholas Piggin
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).