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.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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@us.ibm.com> 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@lists.xensource.com http://lists.xensource.com/xen-devel
Puthiyaparambil, Aravindh
2006-Mar-30 23:47 UTC
RE: [Xen-devel] linux-2.6-xen kernels and initrds
I too am having the same issue but it is manifested differently. I have
an Adaptec 392320 Ultra320 SCSI adapter and I am getting the following
error on the module load from initrd:
ACPI: PCI Interrupt 0000:03:0d.0[A] -> GSI 49 (level, low) -> IRQ 18
scsi2 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
<Adaptec (Dell OEM) 39320 Ultra320 SCSI adapter>
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz,
512 SCBs
Vendor: SEAGATE Model: ST373207LW Rev: D702
Type: Direct-Access ANSI SCSI revision: 03
target2:0:0: asynchronous
scsi2:A:0:0: Tagged Queuing enabled. Depth 32
target2:0:0: Beginning Domain Validation
target2:0:0: wide asynchronous
target2:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU RDSTRM RTI WRFLOW
PCOMP (6.25 ns, offset 63)
target2:0:0: Ending Domain Validation
SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
sdb: Write Protect is off
SCSI device sdb: drive cache: write back w/ FUA SCSI device sdb:
143374650 512-byte hdwr sectors (73408 MB)
sdb: Write Protect is off
SCSI device sdb: drive cache: write back w/ FUA
sdb: sdb1
sd 2:0:0:0: Attached scsi disk sdb
scsi2: Invalid Sequencer interrupt occurred.>>>>>>>>>>>>>>>>>> Dump
Card State Begins
<<<<<<<<<<<<<<<<<
scsi2: Dumping Card State at program address 0x236 Mode 0x0 Card was
paused INTSTAT[0x0] SELOID[0x2] SELID[0x0] HS_MAILBOX[0x0] INTCTL[0x80]
SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] SCSISIGI[0x0]
SCSIPHASE[0x0] SCSIBUS[0x0] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12]
SEQCTL0[0x0] SEQINTCTL[0x6] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0]
QFREEZE_COUNT[0x1] KERNEL_QFREEZE_COUNT[0x1] MK_MESSAGE_SCB[0xff00]
MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0]
PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0]
LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0xe1]
SCB Count = 4 CMDS_PENDING = 1 LASTSCB 0x3 CURRSCB 0x3 NEXTSCB 0xff00
qinstart = 41 qinfifonext = 41
QINFIFO:
WAITING_TID_QUEUES:
0 ( 0x2 )
Pending list:
2 FIFO_USE[0x0] SCB_CONTROL[0x60] SCB_SCSIID[0x7] Total 1 Kernel Free
SCB list: 1 3 0 Sequencer Complete DMA-inprog list:
Sequencer Complete list:
Sequencer DMA-Up and Complete list:
Sequencer On QFreeze and Complete list:
scsi2: FIFO0 Free, LONGJMP == 0x8000, SCB 0x1 SEQIMODE[0x3f]
SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2]
SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00,
SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
scsi2: FIFO1 Free, LONGJMP == 0x8063, SCB 0x3 SEQIMODE[0x3f]
SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2]
SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00,
SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]
LQIN: 0x8 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
0x0 0x0 0x0 0x0
scsi2: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x52
scsi2: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1
scsi2: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x4]
scsi2: REG0 == 0x2c60, SINDEX = 0x10e, DINDEX = 0x102
scsi2: SCBPTR == 0x1, SCB_NEXT == 0xff00, SCB_NEXT2 == 0x3 CDB f2 0 0 80
8 d4
STACK: 0x36 0x22 0x0 0x0 0x0 0x0 0x0 0x0
<<<<<<<<<<<<<<<<< Dump Card
State Ends
>>>>>>>>>>>>>>>>>>
> 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@us.ibm.com>
>
>
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel