From: keith mannthey <kmannth@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: andrew <akpm@osdl.org>
Subject: 2.6.18-rc5-mm1 module build symbol issues -- mkinitrd
Date: Wed, 06 Sep 2006 14:05:19 -0700 [thread overview]
Message-ID: <1157576720.5713.37.camel@keithlap> (raw)
Hello,
Some things have changed between rc5-mm1 and rc4-mm3. During my build
process I pickup the following errors when making the initrd. I don't
see any errors during modules_install.
WARNING: /var/tmp/mkinitramfs.N19592/mnt/lib/modules/2.6.18-rc5-mm1-
smp/kernel/drivers/acpi/processor.ko needs unknown symbol
register_latency_notifier
WARNING: /var/tmp/mkinitramfs.N19592/mnt/lib/modules/2.6.18-rc5-mm1-
smp/kernel/drivers/acpi/processor.ko needs unknown symbol
system_latency_constraint
WARNING: /var/tmp/mkinitramfs.N19592/mnt/lib/modules/2.6.18-rc5-mm1-
smp/kernel/drivers/acpi/processor.ko needs unknown symbol
unregister_latency_notifier
WARNING: /var/tmp/mkinitramfs.N19592/mnt/lib/modules/2.6.18-rc5-mm1-
smp/kernel/drivers/scsi/scsi_mod.ko needs unknown symbol blk_free_tags
My config build all of SCSI as modules and loads them into an initrd.
As I build things into the kernel the errors go away but if I build say
scsi support into the kernel all the symbols from host.c start not
linking (lots and lots of unknown symbols)
Maybe these are just warning from my mkinird scrips (SLES based) but I
wasn't seeing these until rc5-mm1. The symbols in question seem to be
exported correctly so I am not sure what the deal is.
Has some linker / module script been changed or is my mkinitrd script
off in la-la land?
Thanks,
Keith
next reply other threads:[~2006-09-06 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 21:05 keith mannthey [this message]
2006-09-07 0:22 ` 2.6.18-rc5-mm1 module build symbol issues -- mkinitrd keith mannthey
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=1157576720.5713.37.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=akpm@osdl.org \
--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