From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-samsung-soc@vger.kernel.org,
Kukjin Kim <kgene.kim@samsung.com>,
"'Ben Dooks'" <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: Question about "Inconsistent kallsyms data"
Date: Fri, 29 Jul 2011 15:00:03 +0200 [thread overview]
Message-ID: <1338073.oTaTOFP5NR@wuerfel> (raw)
In-Reply-To: <1514384.7oMe1aulyC@flatron>
On Friday 29 July 2011 13:30:20 Tomasz Figa wrote:
>
> I have no idea why, but I cannot reproduce the issue anymore, even after make
> distclean or starting with a clean tree. A build system bug?
>
> I do not know much technical details about the kernel build system, but might
> it be a concurrency issue (I use make -j5 for building with 5 jobs)?
I could reproduce it on some systems, but it changes when you switch compiler
versions or other flags, or the exact kernel version, so it's impossible
to bisect if you have the same problem that I saw.
I got all the way to the point where I could add a nop instruction in one
file and it would go away because the code size grew across some magic
number.
Arnd
next prev parent reply other threads:[~2011-07-29 13: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
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 [this message]
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=1338073.oTaTOFP5NR@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=linux@arm.linux.org.uk \
--cc=mmarek@suse.cz \
--cc=tomasz.figa@gmail.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