[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1157576720.5713.37.camel@keithlap>
Date: Wed, 06 Sep 2006 14:05:19 -0700
From: keith mannthey <kmannth@...ibm.com>
To: lkml <linux-kernel@...r.kernel.org>
Cc: andrew <akpm@...l.org>
Subject: 2.6.18-rc5-mm1 module build symbol issues -- mkinitrd
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists