linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: linux-next: Tree for Dec 7 (kallsyms failure)
Date: Thu, 8 Dec 2016 10:56:07 +1100	[thread overview]
Message-ID: <20161208105607.68810cae@canb.auug.org.au> (raw)
In-Reply-To: <13d83759-40d3-593b-b53f-f3e75fb05b7a@infradead.org>

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

       reply	other threads:[~2016-12-07 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161207172432.184970d7@canb.auug.org.au>
     [not found] ` <13d83759-40d3-593b-b53f-f3e75fb05b7a@infradead.org>
2016-12-07 23:56   ` Stephen Rothwell [this message]
2016-12-08  2:30     ` linux-next: Tree for Dec 7 (kallsyms failure) Randy Dunlap
2016-12-08  4:29       ` Stephen Rothwell
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=20161208105607.68810cae@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=sachinp@linux.vnet.ibm.com \
    /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).