[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14922669.WYSjPzUBX6@wuerfel>
Date: Fri, 29 Jul 2011 14:55:01 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Kukjin Kim <kgene.kim@...sung.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org,
'Ben Dooks' <ben-linux@...ff.org>,
'Russell King' <rmk@....linux.org.uk>,
linux-kbuild@...r.kernel.org, Michal Marek <mmarek@...e.cz>
Subject: Re: Question about "Inconsistent kallsyms data"
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists