2.6.12-rc1-bk1: Inconsistent kallsyms data
While building 2.6.12-rc1-bk1 with attached config I get "Inconsistent kallsyms data".
Setting CONFIG_KALLSYMS_EXTRA_PASS or CONFIG_KALLSYMS_ALL fixes the problem.
Noted differences:
--- System.map
+++ .tmp_System.map
-c03cf83c D kallsyms_markers
-c03cf8d4 D kallsyms_token_table
-c03cfce4 D kallsyms_token_index
+c03cf804 D kallsyms_markers
+c03cf89c D kallsyms_token_table
+c03cfcb0 D kallsyms_token_index
Huge chunk of symbols in tmp_kallsyms2.S are shifted by 0x20000 wrt tmp_kallsyms1.S (_sinittext and _einittext being among them).
--- tmp_kallsyms1.S_
+++ tmp_kallsyms2.S_
-T __sched_text_start PTR 0xc0311e9e
+T __sched_text_start PTR 0xc0311ea0
-T _sinittext PTR 0xc03b5000
+T _sinittext PTR 0xc03d5000
-T _einittext PTR 0xc03cc682
+T _einittext PTR 0xc03ec682
Gnu C 3.4.2 binutils 2.15.92.0.2 Linux C Library 2.3.4 Dynamic linker (ldd) 2.3.4
CONFIG_X86=yCONFIG_MMU=yCONFIG_UID16=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_EXPERIMENTAL=yCONFIG_CLEAN_COMPILE=yCONFIG_BROKEN_ON_SMP=yCONFIG_LOCK_KERNEL=yCONFIG_LOCALVERSION=""CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_POSIX_MQUEUE=yCONFIG_SYSCTL=yCONFIG_HOTPLUG=yCONFIG_KOBJECT_UEVENT=yCONFIG_KALLSYMS=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_SHMEM=yCONFIG_CC_ALIGN_FUNCTIONS=0CONFIG_CC_ALIGN_LABELS=0CONFIG_CC_ALIGN_LOOPS=0CONFIG_CC_ALIGN_JUMPS=0CONFIG_BASE_SMALL=0CONFIG_MODULES=yCONFIG_MODULE_UNLOAD=yCONFIG_OBSOLETE_MODPARM=yCONFIG_KMOD=yCONFIG_X86_PC=yCONFIG_MPENTIUM4=yCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_X86_L1_CACHE_SHIFT=7CONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_HPET_TIMER=yCONFIG_PREEMPT=yCONFIG_PREEMPT_BKL=yCONFIG_X86_TSC=yCONFIG_X86_MCE=yCONFIG_X86_MCE_NONFATAL=yCONFIG_NOHIGHMEM=yCONFIG_MTRR=yCONFIG_HAVE_DEC_LOCK=yCONFIG_REGPARM=yCONFIG_PM=yCONFIG_ACPI=yCONFIG_ACPI_BOOT=yCONFIG_ACPI_INTERPRETER=yCONFIG_ACPI_BUTTON=mCONFIG_ACPI_VIDEO=mCONFIG_ACPI_FAN=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_THERMAL=yCONFIG_ACPI_BLACKLIST_YEAR=2001CONFIG_ACPI_BUS=yCONFIG_ACPI_EC=yCONFIG_ACPI_POWER=yCONFIG_ACPI_PCI=yCONFIG_ACPI_SYSTEM=yCONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_NAMES=yCONFIG_BINFMT_ELF=yCONFIG_BINFMT_MISC=mCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=yCONFIG_FW_LOADER=yCONFIG_PNP=yCONFIG_PNPACPI=yCONFIG_BLK_DEV_FD=mCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_RAM=yCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384CONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_CFQ=yCONFIG_IDE=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_IDEDISK_MULTI_MODE=yCONFIG_BLK_DEV_IDECD=yCONFIG_IDE_GENERIC=yCONFIG_BLK_DEV_IDEPCI=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_GENERIC=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_PIIX=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_IDEDMA_AUTO=yCONFIG_NET=yCONFIG_PACKET=yCONFIG_PACKET_MMAP=yCONFIG_UNIX=yCONFIG_NET_KEY=mCONFIG_INET=yCONFIG_SYN_COOKIES=yCONFIG_IP_TCPDIAG=mCONFIG_NETFILTER=yCONFIG_IP_NF_CONNTRACK=mCONFIG_IP_NF_CT_ACCT=yCONFIG_IP_NF_CONNTRACK_MARK=yCONFIG_IP_NF_CT_PROTO_SCTP=mCONFIG_IP_NF_FTP=mCONFIG_IP_NF_IRC=mCONFIG_IP_NF_TFTP=mCONFIG_IP_NF_AMANDA=mCONFIG_IP_NF_QUEUE=mCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_MATCH_LIMIT=mCONFIG_IP_NF_MATCH_IPRANGE=mCONFIG_IP_NF_MATCH_MAC=mCONFIG_IP_NF_MATCH_PKTTYPE=mCONFIG_IP_NF_MATCH_MARK=mCONFIG_IP_NF_MATCH_MULTIPORT=mCONFIG_IP_NF_MATCH_TOS=mCONFIG_IP_NF_MATCH_RECENT=mCONFIG_IP_NF_MATCH_ECN=mCONFIG_IP_NF_MATCH_DSCP=mCONFIG_IP_NF_MATCH_AH_ESP=mCONFIG_IP_NF_MATCH_LENGTH=mCONFIG_IP_NF_MATCH_TTL=mCONFIG_IP_NF_MATCH_TCPMSS=mCONFIG_IP_NF_MATCH_HELPER=mCONFIG_IP_NF_MATCH_STATE=mCONFIG_IP_NF_MATCH_CONNTRACK=mCONFIG_IP_NF_MATCH_OWNER=mCONFIG_IP_NF_MATCH_ADDRTYPE=mCONFIG_IP_NF_MATCH_REALM=mCONFIG_IP_NF_MATCH_SCTP=mCONFIG_IP_NF_MATCH_COMMENT=mCONFIG_IP_NF_MATCH_CONNMARK=mCONFIG_IP_NF_MATCH_HASHLIMIT=mCONFIG_IP_NF_FILTER=mCONFIG_IP_NF_TARGET_REJECT=mCONFIG_IP_NF_TARGET_LOG=mCONFIG_IP_NF_TARGET_ULOG=mCONFIG_IP_NF_TARGET_TCPMSS=mCONFIG_IP_NF_NAT=mCONFIG_IP_NF_NAT_NEEDED=yCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_TARGET_NETMAP=mCONFIG_IP_NF_TARGET_SAME=mCONFIG_IP_NF_NAT_SNMP_BASIC=mCONFIG_IP_NF_NAT_IRC=mCONFIG_IP_NF_NAT_FTP=mCONFIG_IP_NF_NAT_TFTP=mCONFIG_IP_NF_NAT_AMANDA=mCONFIG_IP_NF_MANGLE=mCONFIG_IP_NF_TARGET_TOS=mCONFIG_IP_NF_TARGET_ECN=mCONFIG_IP_NF_TARGET_DSCP=mCONFIG_IP_NF_TARGET_MARK=mCONFIG_IP_NF_TARGET_CLASSIFY=mCONFIG_IP_NF_TARGET_CONNMARK=mCONFIG_IP_NF_TARGET_CLUSTERIP=mCONFIG_IP_NF_RAW=mCONFIG_IP_NF_TARGET_NOTRACK=mCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_IP_NF_ARP_MANGLE=mCONFIG_XFRM=yCONFIG_NET_DIVERT=yCONFIG_NET_CLS_ROUTE=yCONFIG_NETDEVICES=yCONFIG_NET_ETHERNET=yCONFIG_MII=yCONFIG_NET_PCI=yCONFIG_8139TOO=yCONFIG_8139TOO_PIO=yCONFIG_INPUT=yCONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_EVDEV=yCONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_SERIAL=yCONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_LIBPS2=yCONFIG_SOUND_GAMEPORT=yCONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_NR_UARTS=32CONFIG_SERIAL_CORE=yCONFIG_UNIX98_PTYS=yCONFIG_RTC=yCONFIG_AGP=yCONFIG_AGP_INTEL=yCONFIG_DRM=yCONFIG_DRM_I915=yCONFIG_HPET=yCONFIG_I2C=mCONFIG_I2C_ALGOBIT=mCONFIG_I2C_SENSOR=mCONFIG_SENSORS_IT87=mCONFIG_FB=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SOFT_CURSOR=yCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=yCONFIG_VIDEO_SELECT=yCONFIG_FB_INTEL=yCONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=yCONFIG_LOGO=yCONFIG_LOGO_LINUX_CLUT224=yCONFIG_SOUND=mCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_RTCTIMER=mCONFIG_SND_AC97_CODEC=mCONFIG_SND_INTEL8X0=mCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=yCONFIG_USB=yCONFIG_USB_UHCI_HCD=mCONFIG_EXT2_FS=yCONFIG_EXT3_FS=yCONFIG_JBD=yCONFIG_XFS_FS=mCONFIG_DNOTIFY=yCONFIG_ISO9660_FS=mCONFIG_JOLIET=yCONFIG_PROC_FS=yCONFIG_SYSFS=yCONFIG_DEVPTS_FS_XATTR=yCONFIG_TMPFS=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_RAMFS=yCONFIG_CIFS=mCONFIG_MSDOS_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="utf8"CONFIG_NLS_CODEPAGE_437=mCONFIG_NLS_CODEPAGE_855=mCONFIG_NLS_CODEPAGE_866=mCONFIG_NLS_CODEPAGE_1251=mCONFIG_NLS_ASCII=mCONFIG_NLS_ISO8859_5=mCONFIG_NLS_KOI8_R=mCONFIG_NLS_UTF8=mCONFIG_DEBUG_KERNEL=yCONFIG_MAGIC_SYSRQ=yCONFIG_LOG_BUF_SHIFT=17CONFIG_DEBUG_PREEMPT=yCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_SPINLOCK_SLEEP=yCONFIG_DEBUG_BUGVERBOSE=yCONFIG_EARLY_PRINTK=yCONFIG_DEBUG_STACKOVERFLOW=yCONFIG_4KSTACKS=yCONFIG_CRC32=yCONFIG_GENERIC_HARDIRQS=yCONFIG_GENERIC_IRQ_PROBE=yCONFIG_X86_BIOS_REBOOT=yCONFIG_PC=y
Quoted 4 lines · Alexey Dobriyan
While building 2.6.12-rc1-bk1 with attached config I get "Inconsistent kallsyms data".
Setting
CONFIG_KALLSYMS_EXTRA_PASSorCONFIG_KALLSYMS_ALLfixes the problem.
Please try attached patch. What you see may be the linker deciding to re-shuffle some sections a bit more than usual.
Patch has been in -mm for a while.
Sam
# This is a BitKeeper generated diff -Nru style patch. #
# ChangeSet
# 2005/03/14 20:56:01+01:00 [email protected]
# kbuild: Avoid inconsistent kallsyms data
#
# Several reports on inconsistent kallsyms data has been caused by the aliased symbols # __sched_text_start and __down to shift places in the output of nm. # The root cause was that on second pass ld aligned __sched_text_start to a 4 byte boundary # which is the function alignment on i386. # sched.text and spinlock.text is now aligned to an 8 byte boundary to make sure they # are aligned to a function alignemnt on most (all?) archs.
#
# Tested by: Paulo Marques <[email protected]>
# Tested by: Alexander Stohr <[email protected]>
#
# Signed-off-by: Sam Ravnborg <[email protected]>
#
# include/asm-generic/vmlinux.lds.h # 2005/03/14 20:55:39+01:00 [email protected] +9 -0 # Align sched.text and spinlock.text to an 8 byte boundary # diff -Nru a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h --- a/include/asm-generic/vmlinux.lds.h 2005-03-26 09:07:42 +01:00 +++ b/include/asm-generic/vmlinux.lds.h 2005-03-26 09:07:42 +01:00 @@ -6,6 +6,9 @@ #define VMLINUX_SYMBOL(_sym_) _sym_ #endif
+/* Align . to a 8 byte boundary equals to maximum function alignment. */ +#define ALIGN_FUNCTION() . = ALIGN(8)
+
#define RODATA \
.rodata : AT(ADDR(.rodata) - LOAD_OFFSET) { \
*(.rodata) *(.rodata.*) \
@@ -79,12 +82,18 @@
VMLINUX_SYMBOL(__security_initcall_end) = .; \
}
+/* sched.text is aling to function alignment to secure we have same
+ * address even at second ld pass when generating System.map */
#define SCHED_TEXT \
+ ALIGN_FUNCTION(); \
VMLINUX_SYMBOL(__sched_text_start) = .; \
*(.sched.text) \
VMLINUX_SYMBOL(__sched_text_end) = .;
+/* spinlock.text is aling to function alignment to secure we have same
+ * address even at second ld pass when generating System.map */
#define LOCK_TEXT \
+ ALIGN_FUNCTION(); \
VMLINUX_SYMBOL(__lock_text_start) = .; \
*(.spinlock.text) \
VMLINUX_SYMBOL(__lock_text_end) = .;
Alexey Dobriyan
Tested-byQuoted 8 lines · Sam Ravnborg
Quoted 5 lines · Alexey Dobriyan
While building 2.6.12-rc1-bk1 with attached config I get "Inconsistent kallsyms data".
Setting
CONFIG_KALLSYMS_EXTRA_PASSorCONFIG_KALLSYMS_ALLfixes the problem.Please try attached patch.
Thanks, Sam. It works.
Quoted 3 lines
What you see may be the linker deciding to re-shuffle some sections a bit more than usual.
Patch has been in -mm for a while.
Oh, that's why -mm3 was ok. :-)
Quoted 6 lines
# ChangeSet
# 2005/03/14 20:56:01+01:00 [email protected]
# kbuild: Avoid inconsistent kallsyms data# Tested by: Paulo Marques <[email protected]>
# Tested by: Alexander Stohr <[email protected]>