Re: help trying to track down issue with opensm port

2010-06-11 Thread Ira Weiny
On Fri, 11 Jun 2010 11:29:24 -0700 "Hefty, Sean" wrote: > The following opensm log is from a windows port of opensm 3.3.6. Can anyone > familiar with the error messages explain whether the errors that are > reported should ever happen? Error 9 is a timeout, so I'm not concerned > about that. I

RE: help trying to track down issue with opensm port

2010-06-11 Thread Hefty, Sean
> It means that the umad vendor layer was unable to find a transaction > ID match in the match table. I'm not sure why since there were no > error messages relating to match table overflow. Looks like they are > on GetTableResp methods (RMPP). Not sure how that works in Windows. Thanks - that help

Re: help trying to track down issue with opensm port

2010-06-11 Thread Hal Rosenstock
On Fri, Jun 11, 2010 at 2:29 PM, Hefty, Sean wrote: > The following opensm log is from a windows port of opensm 3.3.6.  Can anyone > familiar with the error messages explain whether the errors that are reported > should ever happen?  Error 9 is a timeout, so I'm not concerned about that.   > I a

help trying to track down issue with opensm port

2010-06-11 Thread Hefty, Sean
The following opensm log is from a windows port of opensm 3.3.6. Can anyone familiar with the error messages explain whether the errors that are reported should ever happen? Error 9 is a timeout, so I'm not concerned about that. I am concerned about the 'failed to obtain request madw' errors.