Re: Linux-kernel-digest Digest, Vol 32, Issue 795

Re: Linux-kernel-digest Digest, Vol 32, Issue 795

[Tej Parkash]

On 5/30/07, Tej Parkash <tejparkash.d@gmail.com> wrote:
> > > >
> > > > 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.

> 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

Re: Linux-kernel-digest Digest, Vol 32, Issue 795

[Sam Ravnborg]

On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote:
> On 5/30/07, Tej Parkash <tejparkash.d@gmail.com> wrote:
> >> > >
> >> > > 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.
> 
> >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.
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

Re: Linux-kernel-digest Digest, Vol 32, Issue 795

[Tej Parkash]

On 5/30/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote:
> > On 5/30/07, Tej Parkash <tejparkash.d@gmail.com> wrote:
> > >> > >
> > >> > > 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.
> >
> > >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.
> 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

Re: Linux-kernel-digest Digest, Vol 32, Issue 795

[Sam Ravnborg]

On Wed, May 30, 2007 at 08:52:29PM +0530, Tej Parkash wrote:
> On 5/30/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> >On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote:
> >> On 5/30/07, Tej Parkash <tejparkash.d@gmail.com> wrote:
> >> >> > >
> >> >> > > 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.
> >>
> >> >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.
> >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'

[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