public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
To: linux-kernel@vger.kernel.org
Subject: [ 2.6.27-rc5 ] x86-32 results of CONFIG_DEBUG_SECTION_MISMATCH
Date: Fri, 29 Aug 2008 21:24:05 -0300	[thread overview]
Message-ID: <48B89325.90801@yahoo.com.ar> (raw)

Hi,

Using:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.27-rc5.tar.bz2

The config is here: http://pastebin.com/f1754954e


WARNING: vmlinux.o(.text+0x85a4): Section mismatch in reference from the
function setup_trampoline() to the variable .cpuinit.data:trampoline_end
The function setup_trampoline() references
the variable __cpuinitdata trampoline_end.
This is often because setup_trampoline lacks a __cpuinitdata
annotation or the annotation of trampoline_end is wrong.

WARNING: vmlinux.o(.text+0x85ac): Section mismatch in reference from the
function setup_trampoline() to the variable .cpuinit.data:trampoline_data
The function setup_trampoline() references
the variable __cpuinitdata trampoline_data.
This is often because setup_trampoline lacks a __cpuinitdata
annotation or the annotation of trampoline_data is wrong.

WARNING: vmlinux.o(.data+0x57f4): Section mismatch in reference from the
variable contig_page_data to the variable .init.data:bootmem_node_data
The variable contig_page_data references
the variable __initdata bootmem_node_data
If the reference is valid then annotate the
variable with __init* (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

WARNING: vmlinux.o(.cpuinit.data+0x0): Section mismatch in reference
from the variable initial_code to the function
.init.text:i386_start_kernel()
The variable __cpuinitdata initial_code references
a function __init i386_start_kernel().
If i386_start_kernel is only used by initial_code then
annotate i386_start_kernel with a matching annotation.

WARNING: vmlinux.o(.cpuinit.data+0xfd0): Section mismatch in reference
from the variable trampoline_data to the variable .init.text:startup_32_smp
The variable __cpuinitdata trampoline_data references
a variable __init startup_32_smp.
If startup_32_smp is only used by trampoline_data then
annotate startup_32_smp with a matching annotation.

Chau,

-- 
Gerardo Exequiel Pozzi ( djgera )
http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219  76ED 39AB 221B 1B8C 330D


                 reply	other threads:[~2008-08-30  0:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=48B89325.90801@yahoo.com.ar \
    --to=vmlinuz386@yahoo.com.ar \
    --cc=linux-kernel@vger.kernel.org \
    /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