2.6.22-rc6 on Dreamcast (SH4)
Still getting this:
MODPOST vmlinux
WARNING: arch/sh/boards/dreamcast/built-in.o(.data+0x0): Section
mismatch: reference to .init.text: (between 'mv_dreamcast' and 'systemasic_int')
WARNING: drivers/built-in.o(.text+0x168e0): Section mismatch: reference to .init.data: (between 'pvr2fb_check_var' and 'pvr2fb_interrupt')
WARNING: drivers/built-in.o(.text+0x1701c): Section mismatch: reference to .init.data: (between 'pvr2fb_pci_probe' and 'read_mem')
WARNING: drivers/built-in.o(.text+0x17024): Section mismatch: reference to .init.text: (between 'pvr2fb_pci_probe' and 'read_mem')
WARNING: drivers/built-in.o(.data+0x738): Section mismatch: reference to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
WARNING: drivers/built-in.o(.data+0x750): Section mismatch: reference to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
But compiles and executes
Quoted 16 lines · Adrian McMenamin
Still getting this:
MODPOST vmlinux
WARNING: arch/sh/boards/dreamcast/built-in.o(.data+0x0): Section
mismatch: reference to .init.text: (between 'mv_dreamcast' and 'systemasic_int')
WARNING: drivers/built-in.o(.text+0x168e0): Section mismatch: reference to .init.data: (between 'pvr2fb_check_var' and 'pvr2fb_interrupt')
WARNING: drivers/built-in.o(.text+0x1701c): Section mismatch: reference to .init.data: (between 'pvr2fb_pci_probe' and 'read_mem')
WARNING: drivers/built-in.o(.text+0x17024): Section mismatch: reference to .init.text: (between 'pvr2fb_pci_probe' and 'read_mem')
WARNING: drivers/built-in.o(.data+0x738): Section mismatch: reference to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
WARNING: drivers/built-in.o(.data+0x750): Section mismatch: reference to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
it means there is code that is not marked as init making references function/data that is marked as init ... this is normally not noticed at boot as the init sections arent cleared/clobbered until well after boot and usually these are problems just for initialization routines ...
i'd review the symbols that are being warned about here to see if they're missing the proper section markers (aka functions that should be labeled as __init but arent)
-mike