Re: 2.6.23-rc1: i386 section mismatch warnings

From: Sam Ravnborg
Date: Tue Jul 24 2007 - 08:29:27 EST


On Tue, Jul 24, 2007 at 10:08:47AM +0200, Sam Ravnborg wrote:
> On Tue, Jul 24, 2007 at 09:48:48AM +0200, Gabriel C wrote:
> > Al Viro wrote:
> > > On Mon, Jul 23, 2007 at 09:18:38PM -0400, Jeff Garzik wrote:
> > >> make allmodconfig on i386:
> > >>
> > >> WARNING: vmlinux(.text+0xc0101183): Section mismatch: reference to
> > >
> > > Ignore. vmlinux.o ones are interesting; so are ones in modules.
> > > vmlinux ones are either duplicates of vmlinux.o or false positives.
> >
> > allyesconfig has a lot Section mismatch warnings , are these false positive too ?
> >
> >
> > http://lkml.org/lkml/2007/7/22/312
>
> The first group are to be solved.
> The last group can be ignored.
>
> I have saved your original mail but not yet looked into any of them.
> I assume that a few hours work can bring down the list considerably but
> I was sidetracked by a book (HP7) ;-)

Took a closer look at the warnings.
modpost gets confused on the weired section mames: .init.text.1, .init.text.3 etc.

See for example:

WARNING: vmlinux.o(.data+0x4b38): Section mismatch: reference to .init.text.3:powernow_cpu_init (between 'powernow_driver' and 'minimum
^^^^^^^^^^^^

This is easy to ignore but anyone that knows why we suddenly have a number following
the section name in a few cases?

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