[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] linux-2.6-xen kernels and initrds


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Andrew D. Ball" <aball@xxxxxxxxxx>
  • Date: Thu, 30 Mar 2006 18:27:02 -0500
  • Delivery-date: Thu, 30 Mar 2006 23:28:58 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I may be seeing the same problem.  It looks like something is messed up
with the way the kernel modules are versioned or their symbol tables,
but I don't know quite enough to finish figuring out what's wrong at the
moment.

Here's some of the error messages I saw while trying to boot:

==
Mounting sysfs
Creating /dev
Starting udev

Loading scsi_mod.ko module
scsi_mod: no version for "struct_module" found: kernel tainted.
Loading sd_mod.ko module
SCSI subsystem initialized
sd_mod: Unknown symbol scsi_print_sense_hdr
Loading libata.ko module
sd_mod: Unknown symbol scsi_mode_sense
insmod: error inserting '/lib/sd_mod.ko': -1 Unknown symbol in module
sd_mod: Unknown symbol scsi_device_get
Loading ata_piix.ko module
sd_mod: Unknown symbol scsi_get_sense_info_fld
insmod: error inserting '/lib/libata.ko': -1 Unknown symbol in module
==

If I do objdump -x on sd_mod from /lib/modules/2.6.16-xen I see several
lines like this:

00000000         *UND*  00000000 scsi_print_sense_hdr

in the symbol table dump.  This is one of the symbols that the initrd
complained about.

Any help fixing this would be appreciated.  I can post more output if
needed.

Thanks!
Andrew
==============
Andrew D. Ball <aball@xxxxxxxxxx>


David F. Barrera wrote:
I have a question regarding the building of the unified xen kernel (linux-2.6-xen) and the use of initrd. In the past I built both xen0 and xenU kernels; the xen0 default configurations had SCSI and Fusion MPT support compiled into the kernel. Now, they are built as modules. The problem is that I am unable to boot the xen kernel built that way, even though I am building an initrd. I have machines running both SLES and FC that are exhibiting this problem. The question is, do I need to do something special to build the initrds? In SuSE, I typically just used the 'mkinitrd' command; in FC4, I do it like this: "mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen 2.6.16-xen". At any rate, nothing has worked to this point.

The SCSI device support help page in 'make menuconfig' states 'do not compile this as a module if your root file system (the one containing the directory /) is located on a SCSI device.', which is the case in my setup. But I have seen it where the distros compile it as module, and the initrd takes care of it.

Any help would be appreciated.





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.