From: Keith Owens <kaos@ocs.com.au>
To: Imre Deak <imre.deak@nokia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: arm: Inconsistent kallsyms data
Date: Wed, 11 May 2005 20:57:25 +1000 [thread overview]
Message-ID: <6946.1115809045@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 11 May 2005 12:05:10 +0300." <1115802310.9757.20.camel@mammoth.research.nokia.com>
On Wed, 11 May 2005 12:05:10 +0300,
Imre Deak <imre.deak@nokia.com> wrote:
>building 2.6.12-rc4 results in "Inconsistent kallsyms data". Setting
>CONFIG_KALLSYMS_EXTRA_PASS=y doesn't help.
>
>I made a diff of .tmp_kallsyms[12].S after converting them to human
>readable form with kallsyms_uncompress.pl .
>
>I noticed that the error is triggered by an __initdata definition. It is
>accessed only from an __init function, so that's ok I think. Removing
>the __initdata attribute gets rid of the error message.
>
>Let me know if you need more data to track the problem.
A better approach is this patch, it extracts the maps including the
section headers after each stage. I sent it to lkml on Sat, 26 Feb
2005 with no response. Apply the patch, make debug_kallsyms and send
me the .tmp_map* files.
---
Make it easier to generate maps for debugging kallsyms problems.
debug_kallsyms is only a debugging target so no help or silent mode.
Signed-off-by: Keith Owens <kaos@ocs.com.au>
Index: linux/Makefile
===================================================================
--- linux.orig/Makefile 2005-02-25 16:21:44.000000000 +1100
+++ linux/Makefile 2005-02-26 21:30:54.000000000 +1100
@@ -722,6 +722,16 @@ quiet_cmd_kallsyms = KSYM $@
# Needs to visit scripts/ before $(KALLSYMS) can be used.
$(KALLSYMS): scripts ;
+# Generate some data for debugging strange kallsyms problems
+debug_kallsyms: .tmp_map$(last_kallsyms)
+
+.tmp_map%: .tmp_vmlinux% FORCE
+ ($(OBJDUMP) -h $< | awk '/^ +[0-9]/{print $$4 " 0 " $$2}'; $(NM) $<) | sort > $@
+
+.tmp_map3: .tmp_map2
+
+.tmp_map2: .tmp_map1
+
endif # ifdef CONFIG_KALLSYMS
# vmlinux image - including updated kernel symbols
next prev parent reply other threads:[~2005-05-11 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 9:05 arm: Inconsistent kallsyms data Imre Deak
2005-05-11 10:57 ` Keith Owens [this message]
2005-05-11 21:15 ` Sam Ravnborg
2005-05-11 10:59 ` Paulo Marques
2005-05-11 21:21 ` Sam Ravnborg
2005-05-11 21:47 ` Russell King
2005-05-11 23:53 ` Imre Deak
2005-05-12 5:20 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 9:40 Imre.Deak
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=6946.1115809045@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=imre.deak@nokia.com \
--cc=linux-kernel@vger.kernel.org \
/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