[Openib-windows] RE: "blue screen" on IP over IB code

Tzachi Dar tzachid at mellanox.co.il
Wed Sep 7 01:00:26 PDT 2005


I wasn't using the latest sources, I'll try again with the new ones.

Thanks
Tzachi

>-----Original Message-----
>From: Fab Tillier [mailto:ftillier at silverstorm.com]
>Sent: Tuesday, September 06, 2005 9:27 PM
>To: 'Tzachi Dar'; openib-windows at openib.org
>Subject: RE: "blue screen" on IP over IB code
>
>> From: Tzachi Dar [mailto:tzachid at mellanox.co.il]
>> Sent: Sunday, September 04, 2005 8:54 AM
>>
>> Hi Fab,
>>
>> While working with our stack, I have received a blue screen. This
>happened
>> when the remote machine that was running open sm has received a blue
>screen
>> as well (this will probably be the subject of another mail, once I have
>more
>> time to debug it).
>>
>> The problem seems to be in the function !__ipoib_ats_reg_cb
>> [f:\projinf2\wininf\trunk\ulp\ipoib\kernel\ipoib_driver.c @ 2220]
>>
>> The immediate problem is that p_adapter variable is not from the correct
>> type. This is because there is a cast from p_reg_svc_rec->svc_context to
>the
>> type ipoib_adapter_t.
>
>What revision are you running?  The svc_context in the current source is
>cast to
>an ats_reg_t structure, which itself has a pointer to the owning adapter
>object.
>
>> This is probably a mistake since the type of the p_reg_svc_rec is dapl.
>> (service name = unsigned char [64] "DAPL Address Translation Service")
>
>IPoIB performs all ATS registrations for assigned IP addresses.  The
>service
>name for ATS is defined by the ATS spec as "DAPL Address Translation
>Service".
>There was discussion in the DAT collaborative about removing the "DAPL"
>from the
>name, but that would have broken backward compatibility so it was left.
>
>Assuming you aren't using the latest source, update and let me know if you
>see
>it again.
>
>Thanks,
>
>- Fab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20050907/4787d40a/attachment.html>


More information about the ofw mailing list