From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kbuild@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Inconsistent kallsyms data on ARM.
Date: Wed, 14 Mar 2012 13:21:46 +0000 [thread overview]
Message-ID: <201203141321.47010.arnd@arndb.de> (raw)
In-Reply-To: <CAP=VYLoStscdVJretZ-Rkbp7V3Vsm8N0oWcjih7ruHFiDN7CiA@mail.gmail.com>
On Tuesday 13 March 2012, Paul Gortmaker wrote:
> This bug(?) has been seen to float from one ARM build to another since
> I started tracking the day-to-day changes in Stephen's linux-next builds.
>
> I see it was discussed earlier:
>
> https://lkml.org/lkml/2011/8/2/233
> https://lkml.org/lkml/2011/10/8/70
>
> but no concrete cause was nailed down. Can the linux-next build results
> help shed some light on this in any way? Since it seems sporadic, is
> there value in embedding a diagnostic of some sort in the infrastructure
> so that when the error is detected, that it prints out more detailed info?
>
> I can provide links to failed linux-next builds, but at the moment, all they
> really seem to have is the same repeated error message, like this one:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/5869367/
>
> and I don't see that helping folks all that much....
>
I'm sure I can reproduce it if necessary, but I need to know what to
look for to find out what the problem is.
Arnd
next prev parent reply other threads:[~2012-03-14 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 22:00 Inconsistent kallsyms data on ARM Paul Gortmaker
2012-03-14 13:21 ` Arnd Bergmann [this message]
2012-03-25 11:20 ` Russell King - ARM Linux
2012-03-25 23:59 ` Jon Masters
2012-03-26 7:37 ` Russell King - ARM Linux
2012-03-26 7:45 ` Uwe Kleine-König
2012-03-26 8:39 ` Arnd Bergmann
2012-03-26 13:07 ` Jon Masters
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=201203141321.47010.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.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