On 22:16 Wed 23 Jul , Hal Rosenstock wrote:
>
> I was referring to the changes which eliminated index 0 being the
> default interface.
Could you be more specific? The only thing I found is:
commit c7a09338808c4570a24a821f5b71c3bb76375aca
Author: Sasha Khapyorsky <[EMAIL PROTECTED]>
Date: T
Sasha,
On Wed, Jul 23, 2008 at 5:22 PM, Sasha Khapyorsky <[EMAIL PROTECTED]> wrote:
> Hi Hal,
>
> On 12:37 Mon 21 Jul , Hal Rosenstock wrote:
>> > or directory)
>> > [EMAIL PROTECTED] ~]# perfquery
>> > ibpanic: [3926] madrpc_init: can't open UMAD port ((null):0): (No such file
>> > or directo
Hi Hal,
On 12:37 Mon 21 Jul , Hal Rosenstock wrote:
> > or directory)
> > [EMAIL PROTECTED] ~]# perfquery
> > ibpanic: [3926] madrpc_init: can't open UMAD port ((null):0): (No such file
> > or directory)
> > [EMAIL PROTECTED] ~]#
>
> This sounds like an additional aspect of the libibumad API
On Mon, Jul 21, 2008 at 12:33 PM, Steve Wise
<[EMAIL PROTECTED]> wrote:
> Hal Rosenstock wrote:
>>
>> Steve,
>>
>> On Sat, Jul 19, 2008 at 8:07 AM, Steve Wise <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> Hal,
>>>
>>> perfquery barfs when an iwarp device is in the mix. I think it needs to
>>> skip over
Hal Rosenstock wrote:
Steve,
On Sat, Jul 19, 2008 at 8:07 AM, Steve Wise <[EMAIL PROTECTED]> wrote:
Hal,
perfquery barfs when an iwarp device is in the mix. I think it needs to
skip over devices that are not IB.
[EMAIL PROTECTED] ~]# perfquery
ibpanic: [5790] madrpc_init: can't open UMAD
Steve,
On Sat, Jul 19, 2008 at 8:07 AM, Steve Wise <[EMAIL PROTECTED]> wrote:
> Hal,
>
> perfquery barfs when an iwarp device is in the mix. I think it needs to
> skip over devices that are not IB.
>
> [EMAIL PROTECTED] ~]# perfquery
> ibpanic: [5790] madrpc_init: can't open UMAD port ((null):0):
Hal,
perfquery barfs when an iwarp device is in the mix. I think it needs to
skip over devices that are not IB.
[EMAIL PROTECTED] ~]# perfquery
ibpanic: [5790] madrpc_init: can't open UMAD port ((null):0): (No such
file or directory)
[EMAIL PROTECTED] ~]#
__
