mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Tej Parkash <tejparkash.d@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-kernel-digest Digest, Vol 32, Issue 795
Date: Wed, 30 May 2007 17:36:05 +0200	[thread overview]
Message-ID: <20070530153605.GC15335@uranus.ravnborg.org> (raw)
In-Reply-To: <2bd9ebfa0705300822s453fe5ccva18bf244e1551098@mail.gmail.com>

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

      reply	other threads:[~2007-05-30 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.13746.1180510421.20629.linux-kernel-digest@lists.us.dell.com>
     [not found] ` <2bd9ebfa0705300735l51dcf4ceubf7f83ab44703010@mail.gmail.com>
2007-05-30 14:37   ` Tej Parkash
2007-05-30 15:12     ` Sam Ravnborg
2007-05-30 15:22       ` Tej Parkash
2007-05-30 15:36         ` Sam Ravnborg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070530153605.GC15335@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tejparkash.d@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®