LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-rc4-mm1 + 3 hot-fixes -- WARNING: could not find versions for .tmp_versions/built-in.mod
Date: Tue, 20 Mar 2007 22:27:05 +0100	[thread overview]
Message-ID: <20070320212705.GB13349@uranus.ravnborg.org> (raw)
In-Reply-To: <a44ae5cd0703200735k197bc50cqeb2856f9f50f88c9@mail.gmail.com>

On Tue, Mar 20, 2007 at 07:35:06AM -0700, Miles Lane wrote:
> It looks like the number of section mismatches is much reduced, which
> is great.  But, I don't remember seeing "WARNING: could not find
> versions for ..." warnings before.  Is this an artifact of the
> init/.missing_syscalls.h problem I encountered earlier?
> 
>  MODPOST vmlinux
> WARNING: could not find versions for .tmp_versions/head.mod
> WARNING: could not find versions for .tmp_versions/init_task.mod
> WARNING: init/built-in.o - Section mismatch: reference to .init.text:
> from .text between 'rest_init' (at offset 0x101) and 'try_name'
I do not see this one - but then I do not build the -mm tree.
Will chase it later if no-one beats me.

> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: could not find versions for .tmp_versions/built-in.mod
> WARNING: mm/built-in.o - Section mismatch: reference to
> .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at
> offset 0x15c8f) and '__section_nr'
I took a look at this one.
You have SPARSEMEM enabled in your config.
And then I see that in sparse.c we call alloc_bootmem_node()
from a function I thought should be marked __devinit (it
is used by memory_hotplug.c).
But I am not familiar enough to judge if __alloc_bootmen_node
are marked correct with __init or __devinit (to say
this is used in the HOTPLUG case) is more correct.
Anyone?

> WARNING: mm/built-in.o - Section mismatch: reference to
> .init.text:__alloc_bootmem_node from .text between 'sparse_init' (at
> offset 0x15d02) and '__section_nr'
Same as above....

> WARNING: mm/built-in.o - Section mismatch: reference to
> .init.data:initkmem_list3 from .text between 'set_up_list3s' (at
> offset 0x18c32) and 's_start'
This one I have also tried to track down. But my
slab knowledge was not enough to fix it :-(


	Sam

  parent reply	other threads:[~2007-03-20 21:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 14:35 Miles Lane
2007-03-20 16:11 ` Andrew Morton
2007-03-20 20:35   ` Sam Ravnborg
2007-03-20 21:27 ` Sam Ravnborg [this message]
2007-03-23 12:54   ` Yasunori Goto
2007-03-23 16:19     ` Sam Ravnborg
2007-03-29  5:17       ` [RFC:PATCH]regster memory init functions into white list of section mismatch Yasunori Goto

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=20070320212705.GB13349@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --subject='Re: 2.6.21-rc4-mm1 + 3 hot-fixes -- WARNING: could not find versions for .tmp_versions/built-in.mod' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).