Re: 2.6.22.6: still seeing section mismatch warnings
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.6: still seeing section mismatch warnings
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.6: still seeing section mismatch warnings
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 > > The warnings are the kernel being much more anal with respect to use > of __init sections and friends and you can for normal use ignore them. > They usually find bugs in errorhandling which seldom trigger and > the bugs has been there for ages in most cases - but it is onyl now > we detect them. thanks, -- Frank # # Automatically generated make config: don't edit # Linux kernel version: 2.6.22.6-y165 # Thu Sep 13 10:07:03 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 # CONFIG_CPUSETS is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set # CONFIG_KMOD is not set CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_LSF=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_TICK_ONESHOT=y # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MCORE2 is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set #
Re: 2.6.22.6: still seeing section mismatch warnings
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. The warnings are the kernel being much more anal with respect to use of __init sections and friends and you can for normal use ignore them. They usually find bugs in errorhandling which seldom trigger and the bugs has been there for ages in most cases - but it is onyl now we detect them. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.6: still seeing section mismatch warnings
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. The warnings are the kernel being much more anal with respect to use of __init sections and friends and you can for normal use ignore them. They usually find bugs in errorhandling which seldom trigger and the bugs has been there for ages in most cases - but it is onyl now we detect them. Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22.6: still seeing section mismatch warnings
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 The warnings are the kernel being much more anal with respect to use of __init sections and friends and you can for normal use ignore them. They usually find bugs in errorhandling which seldom trigger and the bugs has been there for ages in most cases - but it is onyl now we detect them. thanks, -- Frank # # Automatically generated make config: don't edit # Linux kernel version: 2.6.22.6-y165 # Thu Sep 13 10:07:03 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 # CONFIG_CPUSETS is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set # CONFIG_KMOD is not set CONFIG_STOP_MACHINE=y # # Block layer # CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_LSF=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # CONFIG_TICK_ONESHOT=y # CONFIG_NO_HZ is not set CONFIG_HIGH_RES_TIMERS=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MCORE2 is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set #
2.6.22.6: still seeing section mismatch warnings
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) -- Frank - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.22.6: still seeing section mismatch warnings
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) -- Frank - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
