[ofw] Windows Update and IB stack versions
Stanley Sufficool
stanleysufficool at roadrunner.com
Fri Aug 31 09:07:38 PDT 2007
This switch does not seem to allow for disabling of the embedded SM.
This embedded SM would and has caused conflicts with OpenSM in managing
the ports.
I've had more success with the Win to Lin IPoIB connectivity than Win to
Win connectivity. However, I'm unable to establish a pattern of failure.
2 each Gentoo Linux, AMD Opteron 1GB, HP Lion Cub 128 MB, Gentoo kernel
2.6.22.x IB Drivers & ULPs
8 each Windows x64, AMD Opteron 2GB, Voltaire 400Ex-D 128MB, WinIB gen1
(Mellanox Distro) Drivers & ULPs
2 Each Cisco 7000P 24 - Port SFS IB Switch
On Fri, 2007-08-31 at 12:04 +0300, Tzachi Dar wrote:
> Hi,
>
> So far the testing of WinIB and Linux gen2 have been done using opensm
> and not managment switch. So if possibale, can you please try to run
> opensm and see if it solves your problem?
>
> In any case, can you please give us more details about the problem.
> I'm interested in the following:
> 1) Is the windows to windows connectivity not working or only
> Linux-windows?
> 2) Can you look at the event log of the windows machines and let us
> know if there is data there ?
>
> Thanks
> Tzachi
>
>
>
>
> ______________________________________________________________
> From: ofw-bounces at lists.openfabrics.org
> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of
> ssufficool
> Sent: Friday, August 31, 2007 8:42 AM
> To: ofw
> Subject: RE: [ofw] Windows Update and IB stack versions
>
>
>
>
> I'm having Sporadic connectivity with IPoIB using the WinIB
> stack on MLX Infinihost II Ex HCAs and Cisco 7000P switches
> with integrated SM (on the switch). Is there a specific power
> on sequence I should be using or other considerations?
>
> Also, are there any compatibility issues with using OFED gen2
> and WinIB gen1 stacks? I have been having nothing but
> headaches with IPoIB and SRP.
>
> Please help. Thank you.
>
> On Sun, 2007-08-26 at 12:43 +0300, Leonid Keller wrote:
>
> > Hi,
> > The version of WHQL'ed drivers are 1.3.0.1984.
> > Inrease minor version to 4 and rebuild the drivers you are
> > using to get 1.4.0.X version.
> > Then WU won't trouble you more.
> > Leonid
> >
> > ____________________________________________________________
> >
> > From: ofw-bounces at lists.openfabrics.org
> > [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Jan
> > Bottorff
> > Sent: Friday, August 24, 2007 1:44 PM
> > To: Tzachi Dar; ofw at lists.openfabrics.org
> > Subject: RE: [ofw] Windows Update and IB stack versions
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> > As far as I can tell, Windows Update should offer
> > mthca and probably the IB bus driver (although at
> > the moment they don’t seem to show up). It basically
> > matches on PnP id and driver date. The if PnP is the
> > same as what’s installed, and the WU driver date is
> > newer, WU offers it as an update. The paper at
> > http://www.microsoft.com/whdc/maintain/WU_logic.mspx
> > explains the logic.
> >
> >
> >
> > Windows Update I don’t believe will force a driver
> > update on you, but it does offer it if you select
> > custom (which I always do just see what MSFT thinks
> > they should do to my system before they do it). Some
> > users will just periodically install whatever has
> > been updated (good for security patches, bad in this
> > driver case).
> >
> >
> >
> > Jan
> >
> >
> >
> >
> >
> > ____________________________________________________
> >
> > From: Tzachi Dar [mailto:tzachid at mellanox.co.il]
> > Sent: Friday, August 24, 2007 12:27 AM
> > To: Jan Bottorff; ofw at lists.openfabrics.org
> > Subject: RE: [ofw] Windows Update and IB stack
> > versions
> >
> >
> >
> >
> >
> > Is the problem you are seeing specific to IPOIB or
> > does it happen also for other drivers?
> >
> >
> > What I mean is this: It seems that one can easily
> > solve the problem for ipoib but what happens for the
> > bus driver and the low level driver (mthca.sys). Are
> > they also replaced by windows update?
> >
> >
> >
> >
> >
> >
> > It seems that solving the problem for IPOIB can be
> > done, but what about other components?
> >
> >
> >
> >
> >
> >
> > Thanks
> >
> >
> > Tzachi
> >
> >
> >
> >
> >
> >
> >
> >
> > ____________________________________________
> >
> > From: ofw-bounces at lists.openfabrics.org
> > [mailto:ofw-bounces at lists.openfabrics.org]
> > On Behalf Of Jan Bottorff
> > Sent: Wednesday, August 22, 2007 5:30 AM
> > To: ofw at lists.openfabrics.org
> > Subject: [ofw] Windows Update and IB stack
> > versions
> >
> > I see the WHQL signed IPoIB drivers are on
> > Windows Update now. This brings to light a
> > problem in the IB stack.
> >
> >
> >
> > The issue is the PnP hardware id’s generated
> > by the IB bus for virtual devices are not
> > version specific. This means if I install
> > the latest IB stack build, Windows Update
> > will still offer to update my IPoIB drivers,
> > even though they probably would be
> > incompatible with the other IB stack
> > components. The WHQL drivers are
> > approximately build 614, and I know the IBAL
> > interface has new functions and a new
> > version number in the current build. There
> > is absolutely nothing to tell Windows Update
> > that drivers for PnP hardware id “IBA\IPoIB”
> > in version 614 of the IB stack will not work
> > on a stack looking for say the 758 build of
> > the PnP hardware id “IBA\IPoIB”.
> >
> >
> >
> > It seems like some version number and
> > optionally a vendor unique id needs to be
> > part of all the PnP id’s generated, to
> > assure updates only happen between
> > compatible components.
> >
> >
> >
> > Jan
> >
> >
> >
> >
> > _______________________________________________
> > ofw mailing list
> > ofw at lists.openfabrics.org
> > http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
>
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20070831/1a8f056a/attachment.html>
More information about the ofw
mailing list