From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Frysinger <vapier.adi@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Kallsyms problems (was: Re: linux-next: arm build failures)
Date: Sat, 20 Jun 2009 14:41:52 +0200 [thread overview]
Message-ID: <20090620124152.GI32531@uranus.ravnborg.org> (raw)
In-Reply-To: <20090620155440.a7dfb2d4.sfr@canb.auug.org.au>
On Sat, Jun 20, 2009 at 03:54:40PM +1000, Stephen Rothwell wrote:
> Hi Russell,
>
> On Fri, 19 Jun 2009 16:13:21 +0100 Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> >
> > On Wed, Jun 17, 2009 at 11:08:04PM +1000, Stephen Rothwell wrote:
> > >
> > > On Wed, 17 Jun 2009 09:34:31 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > >
> > > > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > > > Over the past few days, I have started getting some arm configs (at least
> > > > > iop13xx_defconfig and integrator_defconfig, but some others) failing to
> > > > > build getting this error:
> > > > >
> > > > > SYSMAP System.map
> > > > > SYSMAP .tmp_System.map
> > > > > Inconsistent kallsyms data
> > > > > Try setting CONFIG_KALLSYMS_EXTRA_PASS
> > > > >
> > > > > Is this something you have seen? Could it be my toolchain (I am
> > > > > currently using gcc 4.4.0 and have not changed it recently)?
> > > >
> > > > I reported an error with kallsysms on ARM this Monday leading to
> > > > inconsistent data:
> > > >
> > > > http://lkml.org/lkml/2009/6/15/233
> > > >
> > > > Could it be related?
> > >
> > > Could be. I have added the proposed fix patch to my fixes tree until
> > > Linus or Sam gets around to including it.
> >
> > No, I don't think it's got anything to do with it. It's the kallsyms
> > generator that's getting confused.
> >
> > What's happening is that we're ending up with differences between the
> > symbolic information generated for .tmp_vmlinux2 and vmlinux:
>
> I do wonder if the above could be the root cause, though. Since I added
> the added the fix mentioned above to linux-next, my arm builds have not
> failed do to this problem. Or maybe this "fix" just works around another
> problem?
>
> In any case, it would be nice if the fix (repeated below) could be sent
> to Linus by someone (it also fixes a problem that Dave Miller is seeing).
Just sent it. Overloaded with day-time stuff (again).
Sam
next prev parent reply other threads:[~2009-06-20 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 6:26 linux-next: arm build failures Stephen Rothwell
2009-06-17 8:34 ` Catalin Marinas
2009-06-17 13:08 ` Stephen Rothwell
2009-06-19 15:13 ` Russell King
2009-06-20 5:54 ` [PATCH] Kallsyms problems (was: Re: linux-next: arm build failures) Stephen Rothwell
2009-06-20 12:41 ` Sam Ravnborg [this message]
2009-06-20 14:14 ` Russell King
2009-06-20 23:58 ` Stephen Rothwell
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=20090620124152.GI32531@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=vapier.adi@gmail.com \
/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