Linux-kernel-digest Digest, Vol 32, Issue 795
A message that is not in the archive (sent off-list or not yet received): mailman.13746.1180510421.20629.linux-kernel-digest@lists.us.dell.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Tej Parkash
Quoted 9 lines
Quoted 7 lines
Quoted 3 lines
while building module i was getting following warning and it terminate module building stage
The below are only warnings and your build should succeed.
It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase?
Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this.
yaa i got the warning but as i said building stage is also getting terminated, without any error.
Quoted 7 lines
The MODPOST stage took a while but it proceeded with no hick-ups.
MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP?Sam
I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same.
thanks
TEJ
Quoted 20 lines · Tej Parkash
Quoted 10 lines · Tej Parkash
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
while building module i was getting following warning and it
terminate
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
module building stage
The below are only warnings and your build should succeed.
It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase?
Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this.
yaa i got the warning but as i said building stage is also getting terminated, without any error.
Quoted 5 lines
The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP?
Quoted 6 lines
Quoted 3 lines
Sam
I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same.
Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included.
Ohh, and exact command-line + config you use.
Sam
Quoted 27 lines · Sam Ravnborg
Quoted 20 lines · Tej Parkash
Quoted 10 lines · Tej Parkash
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
while building module i was getting following warning and it
terminate
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
module building stage
The below are only warnings and your build should succeed.
It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase?
Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this.
yaa i got the warning but as i said building stage is also getting terminated, without any error.
Quoted 5 lines
The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP?
Quoted 6 lines
Quoted 3 lines
Sam
I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same.
Quoted 8 lines
Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included.
Ohh, and exact command-line + config you use.
Sam
make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3'
CHK include/linux/version.h
CHK include/linux/utsrelease.h
Building modules, stage 2.
MODPOST 1889 modules
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name'
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init'
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init'
WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo'
WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo'
WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext'
WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start'
WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3'
the actaul kernel where i am running this make is in /home/tej/linux_src/linux-2.6.21.3.
thanks
tej
Quoted 68 lines · Tej Parkash
Quoted 28 lines · Sam Ravnborg
Quoted 7 lines · Tej Parkash
Quoted 6 lines · Tej Parkash
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
while building module i was getting following warning and it
terminate
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
module building stage
The below are only warnings and your build should succeed.
Quoted 11 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase?
Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this.
yaa i got the warning but as i said building stage is also getting terminated, without any error.
Quoted 3 lines
The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available
RAM
Quoted 8 lines
Quoted 5 lines
/ SWAP?
Sam
I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same.
Quoted 8 lines
Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included.
Ohh, and exact command-line + config you use.
Sam
make -C
/lib/modules/2.6.21.3/build/SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3'
CHKinclude/linux/version.h
CHKinclude/linux/utsrelease.h
Building modules, stage 2.
MODPOST 1889 modules
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset0xc0101171) and 'check_x87'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset0xc0101458) and 'try_name'
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset0xc010adfb) and 'cpu_init'
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset0xc010ae11) and 'cpu_init'
WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset0xc010b46b) and 'display_cacheinfo'
WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset0xc010b475) and 'display_cacheinfo'
WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset0xc010d576) and 'cpuid4_cache_lookup'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset0xc02f2c2e) and '_etext'
WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at
Quoted 8 lines
offset
0xc0173aff) and 's_start'
WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset0xc026fecf) and 'cpufreq_unregister_driver'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3'
[It should have been make V=1 - bot is does not matter]. The build succeeds. This is expected when building modules - there are no "I'm done" messages when doing "make modules".
So only thing left is a few more or less harmless warnings that you can ignore for ypur usage.
Sam