From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Ben Dooks' <ben-linux@fluff.org>,
'Russell King' <rmk@arm.linux.org.uk>,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: Question about "Inconsistent kallsyms data"
Date: Fri, 29 Jul 2011 14:55:01 +0200 [thread overview]
Message-ID: <14922669.WYSjPzUBX6@wuerfel> (raw)
In-Reply-To: <02ae01cc4d91$aed71670$0c854350$%kim@samsung.com>
On Friday 29 July 2011 10:48:46 Kukjin Kim wrote:
> Hi all,
>
> When build with s5pc100_defconfig, happens following.
>
> ...
> KSYM .tmp_kallsyms2.S
> AS .tmp_kallsyms2.o
> LD vmlinux
> SYSMAP System.map
> SYSMAP .tmp_System.map
> Inconsistent kallsyms data
> This is a bug - please report about it
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> make[1]: *** [vmlinux] Error 1
> make: *** [sub-make] Error 2
>
> Its HEAD is following (current latest mainline)
> (commit 55f9c40ff632d03c527d6a6ceddcda0a224587a6)
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc
>
> Please kindly let me know how it should be fixed...
[Taking Michal and linux-kbuild on cc]
I've seen this before with some of my ARM randconfig builds and
spent some time debugging into it, without success.
Can you build with KALLSYMS_EXTRA_PASS=1 and send the diff between
.tmp_kallsyms2.S and .tmp_kallsyms3.S?
Arnd
next parent reply other threads:[~2011-07-29 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02ae01cc4d91$aed71670$0c854350$%kim@samsung.com>
2011-07-29 12:55 ` Arnd Bergmann [this message]
[not found] ` <2563791.8cBqodrk1o@flatron>
[not found] ` <1514384.7oMe1aulyC@flatron>
2011-07-29 13:00 ` Question about "Inconsistent kallsyms data" Arnd Bergmann
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=14922669.WYSjPzUBX6@wuerfel \
--to=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rmk@arm.linux.org.uk \
/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