From: Tomasz Figa <tomasz.figa@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
"'Russell King'" <rmk@arm.linux.org.uk>,
"'Ben Dooks'" <ben-linux@fluff.org>
Subject: Re: Question about "Inconsistent kallsyms data"
Date: Fri, 29 Jul 2011 12:00:07 +0200 [thread overview]
Message-ID: <15086105.RIkTVAqRk0@flatron> (raw)
In-Reply-To: <02ae01cc4d91$aed71670$0c854350$%kim@samsung.com>
Hi,
On Friday 29 of July 2011 at 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
I can confirm that it also happens when building with s3c6400_defconfig and
HEAD at commit 5fd00b031530cc476240f654c078c930f1dcd6ea (Merge branch 'for-
linus' of git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6).
The suggested workaround (make KALLSYMS_EXTRA_PASS=1) helps, but it is only a
workaround and not a solution.
Any suggestions?
Best regards,
Tomasz Figa
next prev parent reply other threads:[~2011-07-29 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 1:48 Question about "Inconsistent kallsyms data" Kukjin Kim
2011-07-29 10:00 ` Tomasz Figa [this message]
2011-07-29 10:02 ` Russell King - ARM Linux
2011-07-29 10:58 ` Tomasz Figa
2011-07-29 11:30 ` Tomasz Figa
2011-07-29 13:00 ` Arnd Bergmann
2011-08-02 16:29 ` Paulo Marques
2011-10-08 10:17 ` Eric Miao
2011-10-08 11:14 ` Arnd Bergmann
2011-07-29 12:55 ` 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=15086105.RIkTVAqRk0@flatron \
--to=tomasz.figa@gmail.com \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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