From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Inconsistent kallsyms data error on ARM
Date: Tue, 30 Oct 2012 20:30:42 +0200 [thread overview]
Message-ID: <20121030183041.GB4690@tarshish> (raw)
In-Reply-To: <1351536890.13635.11.camel@Homeserver>
Hi Chris,
On Mon, Oct 29, 2012 at 02:54:50PM -0400, Chris Wilkinson wrote:
> I intermittently get the below error on ARM/EM7210 after make clean,
> make.
>
> In the past it has gone away following config changes but I was never
> able to isolate just what buildroot or kernel config changes were
> responsible.
>
> What would cause this?
>
> chrisw at Homeserver:~/embedded/buildroot-2012.08$ make
[...]
> Inconsistent kallsyms data
Try the patch at http://git.kernel.org/linus/9973290ce. This patch is included
in kernel version 3.5, but didn't make it into the stable series.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-10-30 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 18:54 [Buildroot] Inconsistent kallsyms data error on ARM Chris Wilkinson
2012-10-30 18:30 ` Baruch Siach [this message]
2013-08-21 9:51 ` Sagaert Johan
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=20121030183041.GB4690@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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