Re: sh: inconsistent kallsyms data

From: Keith Owens (kaos_at_ocs.com.au)
Date: 12/31/04

  • Next message: William Park: "Re: waiting 10s before mounting root filesystem?"
    To: Paul Mundt <lethal@linux-sh.org>
    Date:	Sat, 01 Jan 2005 05:15:43 +1100
    
    

    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

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: William Park: "Re: waiting 10s before mounting root filesystem?"

    Relevant Pages

    • Re: [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.48-00
      ... >> fix. ... addresses are not allowed to move between kallsyms passes, ... the working set hides this peculiarity, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.8-rc2-mm1
      ... Took a look at this and atm compiling a sparc tool-chain to try it out. ... because we do not do the kallsyms stuff if not configured in. ... rules in one place if sparc needs special rules. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC] kallsyms C_SYMBOL_PREFIX support
      ... > kallsyms does not consider SYMBOL_PREFIX of C. ... Maybe even a bigger message, ... At least the patch seems to not affect architectures that don't use the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.7-mm6 - ppc32 inconsistent kallsyms data
      ... > I'm getting this while building for ppc32: ... >bug, and reads like kallsyms is a utility or part of the toolchain; ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: "Needlessly global functions static...."
      ... On Dunnersdag 17 Februar 2005 22:25, Chris Wright wrote: ... > are in kallsyms or System.map. ... gcc -funit-at-a-time. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)