From: Githogori Nyangara-Murage <githogori@xensource.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: githogori@xensource.com, xen-devel@lists.xensource.com,
"Stephan Böni" <boeni@bpm.ch>,
ian.pratt@cl.cam.ac.uk, xen-users@lists.xensource.com
Subject: RE: xen 3.0 boot problem
Date: Fri, 07 Oct 2005 00:22:48 -0700 [thread overview]
Message-ID: <1128669768.5392.10.camel@linux.site> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E1A4@liverpoolst.ad.cl.cam.ac.uk>
As I had stated earlier, I have again built Xen-unstable and have it
running on a Dell 1850 which has a qla2300 card. In fact right now it is
busy beating up on the storage using ibre channel via the qla2300. It is
on RHEL 4.1, and build against a vanilla Cambridge download, so this
should also work on SuSE.
Below is a snippet of my messages file.
.githogori.
Oct 6 22:19:58 localhost kernel: Red Hat/Adaptec aacraid driver
(1.1.2-lk2 Oct 6 2005)
Oct 6 22:19:58 localhost kernel: QLogic Fibre Channel HBA Driver
Oct 6 22:19:58 localhost kernel: ACPI: PCI Interrupt 0000:02:0b.0[A] ->
GSI 37 (level, low) -> IRQ 37
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Found an
ISP2312, irq 37, iobase 0xe0002000
Oct 6 22:19:58 localhost kernel: scsi0 : qla2xxx
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Configuring PCI
space...
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Configure NVRAM
parameters...
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Verifying loaded
RISC code...
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Waiting for LIP
to complete...
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0: Cable is
unplugged...
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.0:
Oct 6 22:19:58 localhost kernel: QLogic Fibre Channel HBA Driver:
8.00.02b5-k
Oct 6 22:19:58 localhost kernel: QLogic QLA2342 - 133MHz PCI-X to 2Gb
FC, Dual Channel
Oct 6 22:19:58 localhost kernel: ISP2312: PCI-X (133 MHz) @
0000:02:0b.0 hdma-, host#=0, fw=3.03.08 IPX
Oct 6 22:19:58 localhost kernel: ACPI: PCI Interrupt 0000:02:0b.1[B] ->
GSI 38 (level, low) -> IRQ 38
Oct 6 22:19:58 localhost kernel: qla2300 0000:02:0b.1: Found an
ISP2312, irq 38, iobase 0xe0004000
Oct 6 22:19:59 localhost kernel: scsi1 : qla2xxx
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: Configuring PCI
space...
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: Configure NVRAM
parameters...
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: Verifying loaded
RISC code...
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: Waiting for LIP
to complete...
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: LIP reset
occured (f8f7).
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: LIP occured
(f8f7).
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: LOOP UP detected
(1 Gbps).
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1: Topology -
(Loop), Host Loop address 0x7d
Oct 6 22:19:59 localhost kernel: qla2300 0000:02:0b.1:
Oct 6 22:19:59 localhost kernel: QLogic Fibre Channel HBA Driver:
8.00.02b5-k
Oct 6 22:19:59 localhost kernel: QLogic QLA2342 - 133MHz PCI-X to 2Gb
FC, Dual Channel
Oct 6 22:19:59 localhost kernel: ISP2312: PCI-X (133 MHz) @
0000:02:0b.1 hdma-, host#=1, fw=3.03.08 IPX
Oct 6 22:19:59 localhost kernel: megaraid cmm: 2.20.2.5 (Release Date:
Fri Jan 21 00:01:03 EST 2005)
Oct 6 22:19:59 localhost kernel: megaraid: 2.20.4.5 (Release Date: Thu
Feb 03 12:27:22 EST 2005)
Oct 6 22:19:59 localhost kernel: Vendor: DGC Model: RAID 5
Rev: 0411
Oct 6 22:19:59 localhost kernel: Type: Direct-Access
ANSI SCSI revision: 02
Oct 6 22:19:59 localhost kernel: 3ware Storage Controller device driver
for Linux v1.26.02.001.
Oct 6 22:19:59 localhost kernel: SCSI device sda: 68317440 512-byte
hdwr sectors (34979 MB)
On Wed, 2005-10-05 at 21:28 +0100, Ian Pratt wrote:
> Has anyone used xen succefully with a qla2300?
>
> What machines have this card?
>
> Ian
>
> > I've installed Xen 3.0-devel on SUSE Linux without any problems.
> > But when i tryed to boot the system, i've got a funny problem:
> >
> > qla2300 0000:05:01.0: Found an ISP2312, irq 185, iobase
> > 0xf8812000 qla2300 0000:05:01.0: Configuring PCI space...
> > qla2300 0000:05:01.0: Configure NVRAM parameters...
> > qla2300 0000:05:01.0: Verifying loaded RISC code...
> > qla2300 0000:05:01.0: Waiting for LIP to complete...
> >
> > until here all works fine, but then:
> >
> > input: PS/2 Generic Mouse on synaptcs-pt/serio0 qla2300
> > 0000:05:01.0: LIP reset occured (f7f7).
> > qla2300 0000:05:01.0: LOOP UP detected (2 Gbps).
> > qla2300 0000:05:01.0: Topology - (F_Port), Host Loop address 0xffff
> > scsi3 : qla2xxx
> > qla2300 0000:04:02.0:
> > QLogic Fibre Channel HBA Driver: 8.01.00b5-k
> > QLogic QLA2340 - 133MHz PCI-X to 2Gb FC, Single Channel
> > ISP2312: PCI-X (100 MHz) @ 0000:05:01.0 hdma+, host#=3,
> > fw=3.03.15 IPX
> > Loading kernel/fs/reiserfs/reiserfs.ko
> > Waiting for device /dev/sda4 to appear: .....not found ---
> > exiting to /bin/sh $
> >
> > if i use the standard (bigsmp) kernel the normal massages are:
> >
> > SCSI device sda: 41943040 512-byte hdwr sectors (21475 MB)
> > SCSI device sda: drive cache: write back SCSI device sda:
> > 41943040 512-byte hdwr sectors (21475 MB) SCSI device sda:
> > drive cache: write back
> > sda: sda1 sda2 sda3 sda4
> > ....usw.
> >
> > Well, my qla2300 has the storage attached not a generic mouse.
> > Of course it isn't possible to boot from this mouse. :-(
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
next prev parent reply other threads:[~2005-10-07 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:28 [Xen-users] xen 3.0 boot problem Ian Pratt
2005-10-07 7:22 ` Githogori Nyangara-Murage [this message]
2005-10-07 17:12 ` The Smoking Man
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 7:44 Stephan Böni
2005-10-10 16:28 Stephan Böni
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=1128669768.5392.10.camel@linux.site \
--to=githogori@xensource.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=boeni@bpm.ch \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.