<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2><SPAN
class=632415906-12022009>DomU access config space through pcibackend, so that
message is ok.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> subbu kl [mailto:subbukl@gmail.com]
<BR><B>Sent:</B> 2009年2月12日 14:59<BR><B>To:</B> Jiang, Yunhong<BR><B>Cc:</B>
David Brown; xen-devel@lists.xensource.com;
general@lists.openfabrics.org<BR><B>Subject:</B> Re: [Xen-devel] Re:
[ofa-general] Fwd: pciback module not working<BR></FONT><BR></DIV>
<DIV></DIV>So getting PCI config space access in domU will solve the problem ?
if so how can I achieve that ?<BR><BR>~subbu<BR><BR>
<DIV class=gmail_quote>On Thu, Feb 12, 2009 at 12:26 PM, Jiang, Yunhong <SPAN
dir=ltr><<A
href="mailto:yunhong.jiang@intel.com">yunhong.jiang@intel.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff size=2>Sorry that seems
the original mail has tried the permissive already :$</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff size=2>How will So how
will the card do the QEUREY_FW command?Through config space or through MMIO?
Following information is something strange, why all the MMIO range is
disabled?</FONT></SPAN></DIV>
<DIV class=Ih2E3d>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN> Memory at
fdc00000 (64-bit, non-prefetchable) [disabled] [size=1M]<BR>
Memory at fd000000 (64-bit, prefetchable) [disabled]
[size=8M]</SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
size=2></FONT></SPAN> </DIV></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff size=2>As for the
following information, I think it should be harmless since domU has no
method of config spacess access method.</FONT></SPAN></DIV>
<DIV class=Ih2E3d>
<DIV> <FONT face="Courier New" size=2>PCI: Fatal: No PCI config space
access function found</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT> </DIV></DIV>
<DIV><SPAN><FONT face="Courier New" size=2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN><FONT face="Courier New" size=2>Yunhong Jiang</FONT></SPAN></DIV>
<DIV><BR></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2>
<DIV class=Ih2E3d><B>From:</B> subbu kl [mailto:<A
href="mailto:subbukl@gmail.com" target=_blank>subbukl@gmail.com</A>]
<BR></DIV><B>Sent:</B> 2009年2月12日 14:43
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c><BR><B>To:</B> Jiang, Yunhong<BR><B>Cc:</B> David Brown;
<A href="mailto:xen-devel@lists.xensource.com"
target=_blank>xen-devel@lists.xensource.com</A>; <A
href="mailto:general@lists.openfabrics.org"
target=_blank>general@lists.openfabrics.org</A><BR><B>Subject:</B> Re:
[Xen-devel] Re: [ofa-general] Fwd: pciback module not
working<BR></DIV></DIV></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>
<DIV></DIV>oops missed it,<BR><BR>well now I dont see that enable
permissive...message. here goes the messages what I got in dom0 while
booting domU <BR><BR>tap tap-1-51712: 2 getting info<BR>pciback: vpci:
0000:0e:00.0: assign to virtual slot 0<BR>device vif1.0 entered
promiscuous mode<BR>ADDRCONF(NETDEV_UP): vif1.0: link is not
ready<BR>blktap: ring-ref 9, event-channel 9, protocol 1
(x86_64-abi)<BR>PCI: Enabling device 0000:0e:00.0 (0000 ->
0002)<BR>ACPI: PCI Interrupt 0000:0e:00.0[A] -> GSI 16 (level, low)
-> IRQ 16<BR>PCI: Setting latency timer of device 0000:0e:00.0 to
64<BR>ACPI: PCI interrupt for device 0000:0e:00.0
disabled<BR>ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes ready<BR>xenbr0:
topology change detected, propagating<BR>xenbr0: port 3(vif1.0) entering
forwarding state<BR><BR>any suspicious message ? <BR>any Idea why I get
that :<BR> <FONT face="Courier New" size=2>PCI: Fatal: No PCI config
space access function found<BR>rtc: IRQ 8 is not free.<BR><BR><SPAN
style="FONT-FAMILY: arial,helvetica,sans-serif">message in domU bootup
message ?</SPAN><BR><BR></FONT>~subbu<BR><BR>
<DIV class=gmail_quote>On Thu, Feb 12, 2009 at 11:50 AM, Jiang, Yunhong
<SPAN dir=ltr><<A href="mailto:yunhong.jiang@intel.com"
target=_blank>yunhong.jiang@intel.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT size=2><SPAN>So
a</SPAN>ny<SPAN> changes in dom0's dmesg?</SPAN></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT
size=2><SPAN></SPAN></FONT></FONT> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> subbu kl [mailto:<A
href="mailto:subbukl@gmail.com" target=_blank>subbukl@gmail.com</A>]
<BR><B>Sent:</B> 2009年2月12日 13:52<BR><B>To:</B> Jiang,
Yunhong<BR><B>Cc:</B> David Brown; <A
href="mailto:xen-devel@lists.xensource.com"
target=_blank>xen-devel@lists.xensource.com</A>; <A
href="mailto:general@lists.openfabrics.org"
target=_blank>general@lists.openfabrics.org</A><BR><B>Subject:</B> Re:
[Xen-devel] Re: [ofa-general] Fwd: pciback module not
working<BR></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV>
<DIV></DIV>
<DIV dir=ltr><FONT face=Tahoma color=#000000 size=2>no luck
!<BR> dmesg in XEN PV guest shows :</FONT></DIV>
<DIV dir=ltr><FONT face=Tahoma size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>ib_mthca: Mellanox
InfiniBand HCA driver v1.0 (April 4, 2008)<BR>ib_mthca: Initializing
0000:00:00.0<BR>PCI: Enabling device 0000:00:00.0 (0000 ->
0002)<BR>PCI: Setting latency timer of device 0000:00:00.0 to
64<BR>ib_mthca 0000:00:00.0: QUERY_FW command failed,
aborting.<BR>ib_mthca: probe of 0000:00:00.0 failed with error
-11<BR><BR></FONT></DIV>
<DIV dir=ltr>even after executingh the following in
dom0:<BR><BR></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>#echo -n 0000:0e:00.0
> /sys/bus/pci/drivers/pciback/permissive<BR><BR></FONT></DIV>
<DIV dir=ltr>I am getting the follwing messages on the console as part
of the initial bootup messages of the guest:</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>Started domain
rhel52_64_3<BR>PCI: Fatal: No PCI config space access function
found<BR>rtc: IRQ 8 is not free.<BR>i8042.c: No controller
found.<BR><BR></FONT></DIV>
<DIV dir=ltr>after executing the following in dom0 :</DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>#xm create -c
rhel52_64_3<BR><BR><BR><SPAN
style="FONT-FAMILY: verdana,sans-serif">so, problem
persisits,</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face="courier new" size=2></FONT> </DIV>
<DIV dir=ltr>~subbu</DIV><BR><BR>
<DIV class=gmail_quote>2009/2/12 Jiang, Yunhong <SPAN dir=ltr><<A
href="mailto:yunhong.jiang@intel.com"
target=_blank>yunhong.jiang@intel.com</A>></SPAN><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=宋体 color=#0000ff
size=2>Seems it is because PCI frontend try to write some
configuration space that PCIback has no config_field entry to
support it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=宋体 color=#0000ff size=2>I
think you can firstly try to do as dom0's dmesg suggested: "<FONT
face="Times New Roman" color=#000000 size=3>see permissive attribute
in sysfs" (it should be "set permissive attribute...", I
think).</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=宋体 color=#0000ff
size=2>BTW, where you got following log? That seems suggest
config space function not found.</FONT></SPAN></DIV>
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=宋体 color=#0000ff
size=2><FONT face="Times New Roman" color=#000000 size=3><FONT
face=宋体 color=#0000ff size=2></FONT><BR>PCI: Fatal: No PCI config
space access function found<BR>rtc: IRQ 8 is not free.<BR>i8042.c:
No controller found."</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT color=#0000ff
size=2></FONT></SPAN> </DIV><SPAN></SPAN></DIV><FONT
face="Times New Roman">-- Yunhong Jiang<SPAN></SPAN></FONT><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> <A
href="mailto:xen-devel-bounces@lists.xensource.com"
target=_blank>xen-devel-bounces@lists.xensource.com</A> [mailto:<A
href="mailto:xen-devel-bounces@lists.xensource.com"
target=_blank>xen-devel-bounces@lists.xensource.com</A>] <B>On
Behalf Of </B>subbu kl<BR><B>Sent:</B> 2009年2月11日
22:18<BR><B>To:</B> David Brown<BR><B>Cc:</B> <A
href="mailto:xen-devel@lists.xensource.com"
target=_blank>xen-devel@lists.xensource.com</A>; <A
href="mailto:general@lists.openfabrics.org"
target=_blank>general@lists.openfabrics.org</A><BR><B>Subject:</B>
[Xen-devel] Re: [ofa-general] Fwd: pciback module not
working<BR></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV>
<DIV></DIV>I am getting the same QUERY_FW failed on RHEL5.2 with
xenxen paravirtualized guest with pciback module.<BR><BR>No one
seems to have tried answering this question on the list, let me
ping xen-devel and ofed people again.<BR><BR>after executing in
dom0<BR>echo -n 0000:0e:00.0 >
/sys/bus/pci/drivers/ib_mthca/unbind<BR>echo -n 0000:0e:00.0 >
/sys/bus/pci/drivers/pciback/new_slot<BR>echo -n 0000:0e:00.0 >
/sys/bus/pci/drivers/pciback/bind<BR><BR>#dmesg<BR>ACPI: PCI
interrupt for device 0000:0e:00.0 disabled<BR>tap tap-1-51712: 2
getting info<BR>tap tap-2-51712: 2 getting info<BR>pciback
0000:0e:00.0: seizing device<BR>PCI: Enabling device 0000:0e:00.0
(0140 -> 0142)<BR>ACPI: PCI Interrupt 0000:0e:00.0[A] -> GSI
16 (level, low) -> IRQ 16<BR>ACPI: PCI interrupt for device
0000:0e:00.0 disabled<BR><BR>#xm create -c rhel52_64_3<BR><BR>PCI:
Fatal: No PCI config space access function found<BR>rtc: IRQ 8 is
not free.<BR>i8042.c: No controller found.<BR><BR><BR>GUEST
dmesg:<BR><BR>ib_mthca: Mellanox InfiniBand HCA driver v1.0 (April
4, 2008)<BR>ib_mthca: Initializing 0000:00:00.0<BR>PCI: Enabling
device 0000:00:00.0 (0000 -> 0002)<BR>PCI: Setting latency
timer of device 0000:00:00.0 to 64<BR>ib_mthca 0000:00:00.0:
QUERY_FW command failed, aborting.<BR>ib_mthca: probe of
0000:00:00.0 failed with error -11<BR><BR>in dom0:<BR>Feb 11
19:44:37 p128 kernel: tap tap-3-51712: 2 getting info<BR>Feb 11
19:44:37 p128 kernel: pciback: vpci: 0000:0e:00.0: assign to
virtual slot 0<BR>Feb 11 19:44:37 p128 kernel: device vif3.0
entered promiscuous mode<BR>Feb 11 19:44:37 p128 kernel:
ADDRCONF(NETDEV_UP): vif3.0: link is not ready<BR>Feb 11 19:44:39
p128 kernel: blktap: ring-ref 9, event-channel 9, protocol 1
(x86_64-abi)<BR>Feb 11 19:44:48 p128 kernel: pciback 0000:0e:00.0:
Driver tried to write to a read-only configuration space field at
offset 0x44, size 2. This may be harmless, but if you have
problems with your device:<BR>Feb 11 19:44:48 p128 kernel: 1) see
permissive attribute in sysfs<BR>Feb 11 19:44:48 p128 kernel: 2)
report problems to the xen-devel mailing list along with details
of your device obtained from lspci.<BR>Feb 11 19:44:48 p128
kernel: PCI: Enabling device 0000:0e:00.0 (0000 -> 0002)<BR>Feb
11 19:44:48 p128 kernel: ACPI: PCI Interrupt 0000:0e:00.0[A] ->
GSI 16 (level, low) -> IRQ 16<BR>Feb 11 19:44:49 p128 kernel:
ACPI: PCI interrupt for device 0000:0e:00.0
disabled<BR><BR><BR><BR>some more details - [root@p128 ~]# rpm -qa
| grep
xen<BR>kernel-xen-2.6.18-92.1.22.el5<BR>xen-3.0.3-64.el5_2.9<BR>xen-libs-3.0.3-64.el5_2.9<BR>xen-libs-3.0.3-64.el5_2.9<BR><BR>[root@p128
~]# ibv_devinfo<BR>hca_id:
mthca0<BR>
fw_ver:
5.3.0<BR>
node_guid:
0002:c902:0022:cd48<BR>
sys_image_guid:
0002:c902:0022:cd4b<BR>
vendor_id:
0x02c9<BR>
vendor_part_id:
25218<BR>
hw_ver:
0x20<BR>
board_id:
MT_0370130002<BR>
phys_port_cnt:
2<BR>
port:
1<BR>
state:
PORT_INIT
(2)<BR>
max_mtu:
2048
(4)<BR>
active_mtu:
512
(2)<BR>
sm_lid:
0<BR>
port_lid:
0<BR>
port_lmc:
0x00<BR><BR>
port:
2<BR>
state:
PORT_DOWN
(1)<BR>
max_mtu:
2048
(4)<BR>
active_mtu:
512
(2)<BR>
sm_lid:
0<BR>
port_lid:
0<BR>
port_lmc:
0x00<BR><BR><BR>any help greatly
appreciated.<BR><BR>~subbu<BR><BR>
<DIV class=gmail_quote>On Sat, Oct 18, 2008 at 4:54 AM, David
Brown <SPAN dir=ltr><<A href="mailto:dmlb2000@gmail.com"
target=_blank>dmlb2000@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Okay
so my question to the openfabrics guys is, why would the
OFED<BR>drivers fail to read the firmware?<BR><BR>Any
thoughts?<BR><BR>Thanks,<BR>- David Brown<BR><BR><BR>----------
Forwarded message ----------<BR>From: David Brown <<A
href="mailto:dmlb2000@gmail.com"
target=_blank>dmlb2000@gmail.com</A>><BR>Date: Thu, Sep 11,
2008 at 2:24 PM<BR>Subject: pciback module not working<BR>To: <A
href="mailto:xen-users@lists.xensource.com"
target=_blank>xen-users@lists.xensource.com</A>, <A
href="mailto:xen-devel@lists.xensource.com"
target=_blank>xen-devel@lists.xensource.com</A><BR><BR><BR>This
issue was brought up about a year and a half ago. So I'll
bring<BR>it up again and see if anything happens.<BR><BR>I've
got an infiniband network and am attempting to pass
the<BR>infiniband card through the host and give it to the
guest.<BR>I'm working with standard CentOS 5.2 on both guest and
host with their<BR>provided xen (3.0.3 ish). I've also attempted
to install the newest<BR>Xen 3.3 and use their standard host
kernel and that did the same<BR>thing. The guest dmesg output in
the guest is similar on both<BR>permissive and normal
mode.<BR><BR>I'm getting issues with detecting the firmware on
the card for some reason...<BR><BR>Any help would be
appreciated.<BR><BR>Thanks,<BR>- David Brown<BR><BR>=== GUEST
dmesg output ===<BR>ib_mthca: Mellanox InfiniBand HCA driver
v1.0 (February 28, 2008)<BR>ib_mthca: Initializing
0000:00:00.0<BR>PCI: Enabling device 0000:00:00.0 (0000 ->
0002)<BR>PCI: Setting latency timer of device 0000:00:00.0 to
64<BR>ib_mthca 0000:00:00.0: QUERY_FW command failed,
aborting.<BR>ib_mthca: probe of 0000:00:00.0 failed with error
-11<BR>=======================<BR><BR>=== Host modprobe.conf
===<BR>alias eth0 bnx2<BR>alias eth1 bnx2<BR>alias
scsi_hostadapter cciss<BR>options pciback
hide=(41:00.0)<BR>=====================<BR><BR>=== Host lspci
output ===<BR># lspci -vs 41:00.0<BR>41:00.0 InfiniBand:
Mellanox Technologies MT25204 [InfiniHost III Lx<BR>HCA] (rev
20)<BR> Subsystem: Hewlett-Packard Company
Unknown device 170a<BR> Flags: fast devsel,
IRQ 16<BR> Memory at fdc00000 (64-bit,
non-prefetchable) [disabled] [size=1M]<BR>
Memory at fd000000 (64-bit, prefetchable) [disabled]
[size=8M]<BR> Capabilities: [40] Power
Management version 2<BR> Capabilities: [48]
Vital Product Data<BR> Capabilities: [90]
Message Signalled Interrupts: 64bit+ Queue=0/5 Enable-<BR>
Capabilities: [84] MSI-X: Enable- Mask-
TabSize=32<BR> Capabilities: [60] Express
Endpoint IRQ 0<BR>=====================<BR><BR>This makes sure
it get loaded first off before anything else.<BR>=== Host
mkinitrd cmd ===<BR># mkinitrd -f --with=pciback --preload
pciback<BR>/boot/initrd-2.6.18-92.1.10.el5xen.img
2.6.18-92.1.10.el5xen<BR>====================<BR><BR>=== Host
pciback dmesg ===<BR>pciback 0000:41:00.0: Driver tried to write
to a read-only<BR>configuration space field at offset 0x44, size
2. This may be<BR>harmless, but if you have problems with your
device:<BR>1) see permissive attribute in sysfs<BR>2) report
problems to the xen-devel mailing list along with details
of<BR>your device obtained from lspci.<BR>PCI: Enabling device
0000:41:00.0 (0000 -> 0002)<BR>ACPI: PCI Interrupt
0000:41:00.0[A] -> GSI 16 (level, low) -> IRQ 16<BR>PCI:
Setting latency timer of device 0000:41:00.0 to 64<BR>ACPI: PCI
interrupt for device 0000:41:00.0
disabled<BR>======================<BR><BR>=== Host pciback dmesg
(after setting it permissive) ===<BR>pciback 0000:41:00.0:
enabling permissive mode configuration space
accesses!<BR>pciback 0000:41:00.0: permissive mode is
potentially unsafe!<BR>pciback: vpci: 0000:41:00.0: assign to
virtual slot 0<BR>device vif1.0 entered promiscuous
mode<BR>ADDRCONF(NETDEV_UP): vif1.0: link is not
ready<BR>blkback: ring-ref 9, event-channel 28, protocol 1
(x86_64-abi)<BR>PCI: Enabling device 0000:41:00.0 (0000 ->
0002)<BR>ACPI: PCI Interrupt 0000:41:00.0[A] -> GSI 16
(level, low) -> IRQ 16<BR>PCI: Setting latency timer of
device 0000:41:00.0 to 64<BR>ACPI: PCI interrupt for device
0000:41:00.0
disabled<BR>=========================================<BR><BR>===
Guest lspci output ===<BR># lspci -v<BR>00:00.0 InfiniBand:
Mellanox Technologies MT25204 [InfiniHost III Lx<BR>HCA] (rev
20)<BR> Subsystem: Hewlett-Packard Company
Unknown device 170a<BR> Flags: fast devsel,
IRQ 16<BR> Memory at fdc00000 (64-bit,
non-prefetchable) [disabled] [size=1M]<BR>
Memory at fd000000 (64-bit, prefetchable) [disabled]
[size=8M]<BR> Capabilities: [40] Power
Management version 2<BR> Capabilities: [48]
Vital Product Data<BR> Capabilities: [90]
Message Signalled Interrupts: 64bit+<BR>Queue=0/5
Enable-<BR> Capabilities: [84] MSI-X:
Enable- Mask- TabSize=32<BR> Capabilities:
[60] Express Endpoint IRQ
0<BR>=====================<BR>_______________________________________________<BR>general
mailing list<BR><A href="mailto:general@lists.openfabrics.org"
target=_blank>general@lists.openfabrics.org</A><BR><A
href="http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general"
target=_blank>http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general</A><BR><BR>To
unsubscribe, please visit <A
href="http://openib.org/mailman/listinfo/openib-general"
target=_blank>http://openib.org/mailman/listinfo/openib-general</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>. . . s u b b u<BR>"You've got to be
original, because if you're like someone else, what do they need
you for?"<BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>. . . s u b b u<BR>"You've got to be original,
because if you're like someone else, what do they need you
for?"<BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>. . . s u b b u<BR>"You've got to be original,
because if you're like someone else, what do they need you
for?"<BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>. . . s u b b u<BR>"You've got to be original, because if
you're like someone else, what do they need you
for?"<BR></BLOCKQUOTE></BODY></HTML>