From: Keith Owens <kaos@ocs.com.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: sh: inconsistent kallsyms data
Date: Sat, 01 Jan 2005 05:15:43 +1100 [thread overview]
Message-ID: <3512.1104516943@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 31 Dec 2004 19:25:50 +0200." <20041231172549.GA18211@linux-sh.org>
On Fri, 31 Dec 2004 19:25:50 +0200,
Paul Mundt <lethal@linux-sh.org> wrote:
>Building 2.6.10 for sh results in inconsistent kallsyms data. Turning on
>CONFIG_KALLSYMS_ALL fixes it, as does CONFIG_KALLSYMS_EXTRA_PASS.
>
>The symbols that seem to be problematic between the second and third
>pass are all kallsyms special symbols. With only CONFIG_KALLSYMS set we
>see:
>
>--- System.map 2004-12-31 10:53:10.278567522 -0600
>+++ .tmp_System.map 2004-12-31 10:53:10.347558024 -0600
>@@ -6868,9 +6868,9 @@
> 8817c4d0 D kallsyms_addresses
> 88182660 D kallsyms_num_syms
> 88182670 D kallsyms_names
>-88190630 D kallsyms_markers
>-881906a0 D kallsyms_token_table
>-88190b50 D kallsyms_token_index
>+881906a0 D kallsyms_markers
>+88190710 D kallsyms_token_table
>+88190bc0 D kallsyms_token_index
> 88191000 D irq_desc
> 88191000 A __per_cpu_end
> 88191000 A __per_cpu_start
>
>So for some reason we have a 0x70 variance between these, and only
>these. Running with --all-symbols this seems to work fine.
I suspect the change in the kallsyms compression algorithm between
2.6.9 and 2.6.10. It added 3 new symbols and I am not convinced that
they are being processed correctly by scripts/kallsyms.c. Apply this
debug patch, tar .tmp_kallsyms* and send the tarball to me.
Index: 2.6.10-pristine/Makefile
===================================================================
--- 2.6.10-pristine.orig/Makefile 2004-12-25 10:25:19.000000000 +1100
+++ 2.6.10-pristine/Makefile 2005-01-01 05:13:25.714459901 +1100
@@ -680,7 +680,7 @@ define verify_kallsyms
$(Q)cmp -s System.map .tmp_System.map || \
(echo Inconsistent kallsyms data; \
echo Try setting CONFIG_KALLSYMS_EXTRA_PASS; \
- rm .tmp_kallsyms* ; /bin/false )
+ /bin/false )
endef
# Update vmlinux version before link
next prev parent reply other threads:[~2004-12-31 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 17:25 sh: inconsistent kallsyms data Paul Mundt
2004-12-31 17:59 ` pmarques
2004-12-31 18:22 ` Paul Mundt
2004-12-31 19:29 ` pmarques
2004-12-31 19:42 ` Paul Mundt
2004-12-31 18:15 ` Keith Owens [this message]
2005-01-01 3:59 ` Keith Owens
2005-01-01 4:15 ` Keith Owens
2005-01-01 9:01 ` Paul Mundt
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=3512.1104516943@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.