[openib-general] RE: ib_uat kernel panic without async callback

Hal Rosenstock halr at voltaire.com
Tue Jul 12 02:49:44 PDT 2005


On Mon, 2005-07-11 at 20:03, Arlin Davis wrote:
> Hal,
> 
> >-----Original Message-----
> >From: Hal Rosenstock [mailto:halr at voltaire.com]
> >Sent: Monday, July 11, 2005 4:21 PM
> >To: Davis, Arlin R
> >Cc: openib-general at openib.org
> >Subject: Re: ib_uat kernel panic without async callback
> >
> >Hi Arlin,
> >
> >On Mon, 2005-07-11 at 18:37, Davis, Arlin R wrote:
> >> I was attempting to call ib_at_route_by_ip() in sync mode and get the
> >> following oops:
> >>
> >> You can change the att.c (line 193) example as follow to duplicate:
> >>
> >>   r = ib_at_route_by_ip(0x1400a8c0, 0, 0, 0,
> >>                                       att_rt + i, NULL, NULL);

BTW, did this compile ? I think there is 1 too many NULLs here.

> >> I will go back to async mode for now.
> >>
> >> Thanks,
> >>
> >> -arlin
> >
> >How was IPoIB configured ? Was ib0 on the 192.168.0.x subnet ?
> >
> 
> ib0       Link encap:UNSPEC  HWaddr 00-00-04-04-FE-80-00-00-00-00-00-00-00-00-00-00
>           inet addr:192.168.0.19  Bcast:192.168.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::202:c902:0:409d/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:2044  Metric:1
>           RX packets:19 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:128
>           RX bytes:1204 (1.1 KiB)  TX bytes:1108 (1.0 KiB)
> 
> >What do you mean by "back to async mode" ? Did you use async mode before
> >?
> 
> Yes, I used async mode similar to the example before trying the call synchronously. If I provide the
> async_comp with the ib_at_route_by_ip() followed by ib_at_callback_get() then it seems to work. If
> async_comp == NULL then it blows up in the ib_at_route_by_ip call.

I understand. I was confused by the use of sync and async here. It is
just that the async callback is not supplied. My bad. I'll look into it
and get back on this.

-- Hal




More information about the general mailing list