The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
Date: Thu, 02 Aug 2007 12:50:23 +0100	[thread overview]
Message-ID: <1186055423.2686.2.camel@localhost.localdomain> (raw)
In-Reply-To: <46B1A9DE.4090907@free.fr>

[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]

On Thu, 2007-08-02 at 11:54 +0200, John Sigler wrote:
> Hello,
> 
> I'm trying to build a 2.6.22.1-rt9 kernel for a P3.
> 
> I used 'make xconfig' to create .config
> http://linux.kernel.free.fr/latency/config-2.6.22.1-rt9-adlink
> 
> I get the following warning:
> 
>    LD      vmlinux
>    SYSMAP  System.map
>    SYSMAP  .tmp_System.map
>    MODPOST vmlinux
> WARNING: kernel/built-in.o(.text+0x19152): Section mismatch: reference 
> to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
>    AS      arch/i386/boot/bootsect.o
>    LD      arch/i386/boot/bootsect
>    AS      arch/i386/boot/setup.o
>    LD      arch/i386/boot/setup
>    AS      arch/i386/boot/compressed/head.o
>    CC      arch/i386/boot/compressed/misc.o
>    OBJCOPY arch/i386/boot/compressed/vmlinux.bin
>    GZIP    arch/i386/boot/compressed/vmlinux.bin.gz
>    LD      arch/i386/boot/compressed/piggy.o
>    LD      arch/i386/boot/compressed/vmlinux
>    OBJCOPY arch/i386/boot/vmlinux.bin
>    HOSTCC  arch/i386/boot/tools/build
>    BUILD   arch/i386/boot/bzImage
> Root device is (3, 1)
> Boot sector 512 bytes.
> Setup is 7082 bytes.
> System is 1142 kB
> Kernel: arch/i386/boot/bzImage is ready  (#1)
>    Building modules, stage 2.
>    MODPOST 0 modules
> 
> 
> I also get the following warnings (which seem less severe)
> 
>    CC      drivers/pci/pci.o
>    CC      drivers/pci/quirks.o
>    CC      drivers/pci/pci-driver.o
>    CC      drivers/pci/search.o
> drivers/pci/search.c: In function `pci_find_slot':
> drivers/pci/search.c:99: warning: `pci_find_device' is deprecated 
> (declared at include/linux/pci.h:477)
> drivers/pci/search.c: At top level:
> drivers/pci/search.c:434: warning: `pci_find_device' is deprecated 
> (declared at drivers/pci/search.c:241)
> drivers/pci/search.c:434: warning: `pci_find_device' is deprecated 
> (declared at drivers/pci/search.c:241)
>    CC      drivers/pci/pci-sysfs.o
>    CC      drivers/pci/rom.o
> 
> 
> Finally, I note that X86_CMPXCHG64 is no longer defined since its 
> specification was changed between 2.6.20 and 2.6.22.
> 
>   config X86_CMPXCHG64
>      bool
> -   depends on !M386 && !M486
> +   depends on X86_PAE
>      default y

this patch resolve the warning ? 
I always got this warning but don't care much about it 

-- 
Sérgio M. B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]

      parent reply	other threads:[~2007-08-02 11:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  9:54 Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head') John Sigler
2007-08-02 10:35 ` Satyam Sharma
2007-08-02 11:50 ` Sergio Monteiro Basto [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=1186055423.2686.2.camel@localhost.localdomain \
    --to=sergio@sergiomb.no-ip.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux.kernel@free.fr \
    /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