[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1178740693.3086.81.camel@zod.rchland.ibm.com>
Date: Wed, 09 May 2007 14:58:13 -0500
From: Josh Boyer <jwboyer@...ux.vnet.ibm.com>
To: Linas Vepstas <linas@...tin.ibm.com>
Cc: Gabriel Paubert <paubert@...m.es>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>, paulus@...ba.org,
LKML <linux-kernel@...r.kernel.org>,
ppc-dev <linuxppc-dev@...abs.org>
Subject: Re: Section mismatch warnings (was Re: [PATCH] early_pfn_to_nid
needs to be __meminit)
On Wed, 2007-05-09 at 14:45 -0500, Linas Vepstas wrote:
> On Wed, May 09, 2007 at 06:51:15PM +0200, Gabriel Paubert wrote:
> > On Thu, May 10, 2007 at 02:25:52AM +1000, Stephen Rothwell wrote:
> > > This removes a section mismatch warning in those circumstances.
> >
> > Speaking of this, I just tried to compile an official (Linus' git tree)
> > kernel for my old PMac G4 and I get a lot of section mismatch warnings at
> > the end of the compilation:
> >
> > WARNING: arch/powerpc/mm/built-in.o - Section mismatch: reference to .init.text:early_get_page from .text between 'pte_alloc_one_kernel' (at offset 0xf50) and 'v_mapped_by_bats'
> >
> > I find these 50 or so warnings so scary that I've not yet tried
> > to boot the kernel. Note that this is a non-modular kernel.
>
> I'm getting oodles of these on an older -mm2 tree. The kernels seem to
> work fine. Yes, they should be fixed but I'm up to my proverbial eyballs
> in alligators.
Yeah, I see all kinds of this too. Does anyone have an idea why they're
being spit out? Or if it's related to a particular binutils version,
etc?
josh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists