[openib-general] [PATCH] kDAPL: remove DAT_UINT32 and DAT_UIN T64

Hal Rosenstock halr at voltaire.com
Thu May 5 22:57:15 PDT 2005


On Thu, 2005-05-05 at 18:39, Tom Duffy wrote:

> kDAPL: DAPL: Started (dapl_init)
> kDAPL: Inside dapl_add_one called by mthca0
> KDAPL : Added device mthca0a to the registry
> KDAPL : Added device mthca0b to the registry
> Kdapltest Module Loaded - major 253
> kDAPL: dapl_ia_open (mthca0a, 8, ffff81003b011ed0, ffff81003b011ef8)
> kDAPL: dapl_ia_open () returns 0x0
> kDAPL: dapl_pz_create (ffff81003aef2168, ffff81003b011ef0)
> kDAPL: dapl_evd_kcreate (ffff81003aef2168, 8, 1, upcall, 0x20, ffff81003b011ee8)
> kDAPL: dapl_evd_kcreate (ffff81003aef2168, 8, 1, upcall, 0xa0, ffff81003b011ee0)
> kDAPL: dapl_evd_kcreate (ffff81003aef2168, 8, 1, upcall, 0x40, ffff81003b011ed8)
> kDAPL: dapl_ep_create (ffff81003aef2168, ffff8100770c0e10, ffff81003aef2a28, ffff81003aef26e0, ffff81003b6a1b40, 0000000000000000, ffff81003b011ec8)
> kDAPL: created qp_hndl = ffff81007693b2d8, qpn = 170406
> kDAPL: dapl_ia_query (ffff81003aef2168, ffff81003b011dc0, ffff81003a97cb88, ffff81003a97ce38)
> kDAPL: dapl_ia_query () returns 0x0
> kDAPL: dapl_ep_query (ffff81007e3354f8, ffff81003b011d08)

Below is where things start shutting down...

> kDAPL: dapl_ep_free (ffff81007e3354f8)
> kDAPL: dapl_ep_disconnect (ffff81007e3354f8, 0)
> kDAPL: dapl_ep_disconnect () returns 0x8007002e
> kDAPL: dapl_ep_free: Free EP: 0, ep ffff81007e3354f8 qp_state 1 qp_handle 7693b2d8
> kDAPL: dapl_evd_free (ffff81003b6a1b40)
> kDAPL: dapl_evd_free () returns 0x0
> kDAPL: dapl_evd_free (ffff81003aef26e0)
> kDAPL: dapl_evd_free () returns 0x0
> kDAPL: dapl_evd_free (ffff81003aef2a28)
> kDAPL: dapl_evd_free () returns 0x0
> kDAPL: dapl_pz_free (ffff8100770c0e10)
> kDAPL: dapl_ia_query (ffff81003aef2168, 0000000000000000, 0000000000000000, ffff81003b011ab8)
> kDAPL: dapl_ia_query () returns 0x0
> kDAPL: dapl_ia_close (ffff81003aef2168, 1)
> kDAPL: dapl_evd_free (ffff81003aef2d70)
> kDAPL: dapl_evd_free () returns 0x0

I think the key was in your previous email with the client error
indicated as:

DT_BpoolAlloc: dat_lmr_kcreate failed DAT_NOT_IMPLEMENTED

I think this is a registry/provider mismatch somehow which makes me
think that the recent build changes did this somehow.

-- Hal




More information about the general mailing list