[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160208144232.GA5984@sudip-pc>
Date: Mon, 8 Feb 2016 20:13:07 +0530
From: Sudip Mukherjee <sudipm.mukherjee@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Steven Miao <realmz6@...il.com>,
Chris Metcalf <cmetcalf@...hip.com>,
adi-buildroot-devel@...ts.sourceforge.net,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Guenter Roeck <linux@...ck-us.net>,
Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: Tree for Feb 8
On Mon, Feb 08, 2016 at 05:26:11PM +0530, Sudip Mukherjee wrote:
> On Mon, Feb 08, 2016 at 04:17:56PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20160205:
>
> My blackfin defconfig build fails with:
>
> kallsyms failure: relative symbol value 0xffa00000 out of range in
> relative mode
>
> build log at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/107707060
>
> and tilegx defconfig fails with:
> kallsyms failure: relative symbol value 0xfffffff700020000 out of range
> in relative mode
>
> build log at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/107707069
>
> I will do a bisect later today to see which has caused this.
Bisected. And -
de9d2352a3c9 ("kallsyms: add support for relative offsets in kallsyms address table")
is introducing the message of "kallsyms failure: relative symbol value .... "
and 9b461d6a3ab9 ("scripts/link-vmlinux.sh: force error on kallsyms failure")
is causing the build failure.
Just reverting de9d2352a3c9 is fixing these build failures.
Adding Cc to Andrew, Guenter, Ard and Kees.
regards
sudip
Powered by blists - more mailing lists