Re: 2.6.22.6: still seeing section mismatch warnings

From: Sam Ravnborg
Date: Fri Sep 14 2007 - 16:00:27 EST


On Thu, Sep 13, 2007 at 10:35:05AM +0200, Frank van Maarseveen wrote:
> On Thu, Sep 13, 2007 at 09:02:00AM +0200, Sam Ravnborg wrote:
> > On Wed, Sep 12, 2007 at 06:00:17PM +0200, Frank van Maarseveen wrote:
> > > I'm still seeing the warnings below (2.6.22 started off with lots of
> > > section mismatch warning) but I have no idea if it is safe to ignore
> > > these:
> > >
> > > WARNING: arch/i386/kernel/built-in.o(.text+0xea62): Section mismatch: reference to .init.data:trampoline_end (between 'setup_trampoline' and 'cpu_coregroup_map')
> > > WARNING: arch/i386/kernel/built-in.o(.text+0xea67): Section mismatch: reference to .init.data:trampoline_data (between 'setup_trampoline' and 'cpu_coregroup_map')
> > > WARNING: arch/i386/kernel/built-in.o(.text+0xea79): Section mismatch: reference to .init.data:trampoline_data (between 'setup_trampoline' and 'cpu_coregroup_map')
> > > WARNING: arch/i386/kernel/built-in.o(.exit.text+0x26): Section mismatch: reference to .init.text: (between 'cache_remove_dev' and 'ffh_cstate_exit')
> > > WARNING: arch/i386/kernel/built-in.o(.data+0xee0): Section mismatch: reference to .init.text: (between 'thermal_throttle_cpu_notifier' and 'mce_work')
> > > WARNING: kernel/built-in.o(.text+0x1b415): Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
> > >
> > >
> > > gcc version 3.4.6 (Debian 3.4.6-5)
> >
> > Does not appear with an allmodconfig.
> > Care to send me your .config then I may take a look.
>
> See attached .config

Tried to build a fres i386 kernel with your config.
As I'm running on latest from Linus I could see that all your
reported warnings were gone.
But one new warning crept in for which I have prepared a patch -
to be submitted when I have test-builded a bit more.

Anyway - thanks for reporting and sending your .config.

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/