From: Paul Mackerras <paulus@samba.org>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@au1.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PPC64 2.6.34-rc6 warning - Is this expected ?
Date: Fri, 7 May 2010 15:40:34 +1000 [thread overview]
Message-ID: <20100507054034.GB25173@drongo> (raw)
In-Reply-To: <1273060251.13463.8.camel@subratamodak.linux.ibm.com>
On Wed, May 05, 2010 at 05:20:51PM +0530, Subrata Modak wrote:
> I built 2.6.34-rc6 with the attached Fedora Config file
> (config-2.6.33.1-19.fc13.ppc64) on my P5 Fedora Box and got the
> following warning. Is the following expected ?
>
> CALL arch/powerpc/relocs_check.pl
> Building modules, stage 2.
> WARNING: 4 bad relocations
> c00000000007216e R_PPC64_ADDR16_HIGHEST __ksymtab+0x00000000009dcec8
> c000000000072172 R_PPC64_ADDR16_HIGHER __ksymtab+0x00000000009dcec8
> c00000000007217a R_PPC64_ADDR16_HI __ksymtab+0x00000000009dcec8
> c00000000007217e R_PPC64_ADDR16_LO __ksymtab+0x00000000009dcec8
No, it's not expected. It's in iSeries code, so you could avoid it
just by disabling CONFIG_ISERIES (I don't think any distro still
supports legacy iSeries). I'll post a patch to fix the problem
properly.
Paul.
next prev parent reply other threads:[~2010-05-07 5:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 11:50 PPC64 2.6.34-rc6 warning - Is this expected ? Subrata Modak
2010-05-07 5:40 ` Paul Mackerras [this message]
2010-07-15 11:35 ` [PPC64/Power7 - 2.6.35-rc5] Bad relocation warnings while Building a CONFIG_RELOCATABLE kernel with CONFIG_ISERIES enabled Subrata Modak
2010-07-16 2:04 ` Michael Neuling
2010-07-19 8:56 ` Subrata Modak
2010-07-19 1:11 ` Benjamin Herrenschmidt
2010-07-19 7:36 ` Alexander Graf
2010-07-19 11:23 ` [PPC64/Power7 - 2.6.35-rc5] Bad relocation warnings whileBuilding " Milton Miller
2010-07-19 11:35 ` Milton Miller
2010-07-19 12:00 ` Alexander Graf
2010-07-20 7:27 ` Milton Miller
2010-07-20 7:37 ` Alexander Graf
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=20100507054034.GB25173@drongo \
--to=paulus@samba.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@au1.ibm.com \
--cc=subrata@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).