Date: Wed, 11 May 2005 23:21:24 +0200
From: Sam Ravnborg <sam@ravnborg.org>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Imre Deak <imre.deak@nokia.com>, linux-kernel@vger.kernel.org,
       kaos@ocs.com.au
Subject: Re: arm: Inconsistent kallsyms data
Message-ID: <20050511212124.GB8127@mars.ravnborg.org>
References: <1115802310.9757.20.camel@mammoth.research.nokia.com> <4281E5AE.4090601@grupopie.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4281E5AE.4090601@grupopie.com>
User-Agent: Mutt/1.5.8i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1140
Lines: 28

On Wed, May 11, 2005 at 11:59:58AM +0100, Paulo Marques wrote:
> Imre Deak wrote:
> >Hi,
> >
> >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 .
> 
> From the diff, I can see the problem is that "__bss_start" changes 
> position with "_edata" from the first to the second pass.
> 
> If your read my post from yesterday "Re: Linux v2.6.12-rc4" (not a very 
> descriptive subject), I explain there why this is a problem.
> 
> Sam, from looking at your patch, it seems that the patch shouldn't 
> affect these particular symbols. Am I correct?
As I read the diff my patch will not solve this problem.
Let's see the output generated with Keith's debug_kallsyms patch if
that will sched some light over it.

	Sam
-
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/