You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't fully tracked this down, but with my latest out of tree changes (merging soon), the client hangs trying to send back responses. A backtrace from interrupting the process gives this:
#0 0xb7fb5d54 in sock_compare_addr (addr1=0x8068714, addr2=0x804d1e0)
at prov/sockets/src/sock_conn.c:104
#1 0xb7fb5dad in sock_conn_map_lookup (map=0x804d730, addr=0x804d1e0)
at prov/sockets/src/sock_conn.c:114
#2 0xb7fb64c2 in sock_conn_map_connect (dom=0x804d490, map=0x804d730,
addr=0x804d1e0) at prov/sockets/src/sock_conn.c:237
#3 0xb7fb65ab in sock_conn_map_match_or_connect (dom=0x804d490,
map=0x804d730, addr=0x804d1e0) at prov/sockets/src/sock_conn.c:260
#4 0xb7faa17e in sock_ep_lookup_conn (ep=0x807a7e8)
at prov/sockets/src/sock_ep.c:1343
#5 0xb7fb722d in sock_ep_sendmsg (ep=0x807a7e8, msg=0xbffff050, flags=0)
at prov/sockets/src/sock_msg.c:173
#6 0xb7fb7675 in sock_ep_send (ep=0x807a7e8, buf=0x808ad58, len=100,
desc=0x0, dest_addr=0, context=0x804d468)
at prov/sockets/src/sock_msg.c:254
#7 0x08049269 in fi_send (context=0x804d468, dest_addr=0, desc=0x0,
len=<optimized out>, buf=<optimized out>, ep=<optimized out>)
at /usr/local/include/rdma/fi_endpoint.h:271
#8 post_sends (node=0x804d468) at ported/librdmacm/cmatose.c:204 #9 0x08048df4 in run_client () at ported/librdmacm/cmatose.c:493 #10 main (argc=3, argv=0xbffff1b4) at ported/librdmacm/cmatose.c:606
Note that data transfers have already gone from the server to the client, so an existing connection should be available.
The text was updated successfully, but these errors were encountered:
I haven't fully tracked this down, but with my latest out of tree changes (merging soon), the client hangs trying to send back responses. A backtrace from interrupting the process gives this:
#0 0xb7fb5d54 in sock_compare_addr (addr1=0x8068714, addr2=0x804d1e0)
#1 0xb7fb5dad in sock_conn_map_lookup (map=0x804d730, addr=0x804d1e0)
#2 0xb7fb64c2 in sock_conn_map_connect (dom=0x804d490, map=0x804d730,
#3 0xb7fb65ab in sock_conn_map_match_or_connect (dom=0x804d490,
#4 0xb7faa17e in sock_ep_lookup_conn (ep=0x807a7e8)
#5 0xb7fb722d in sock_ep_sendmsg (ep=0x807a7e8, msg=0xbffff050, flags=0)
#6 0xb7fb7675 in sock_ep_send (ep=0x807a7e8, buf=0x808ad58, len=100,
#7 0x08049269 in fi_send (context=0x804d468, dest_addr=0, desc=0x0,
#8 post_sends (node=0x804d468) at ported/librdmacm/cmatose.c:204
#9 0x08048df4 in run_client () at ported/librdmacm/cmatose.c:493
#10 main (argc=3, argv=0xbffff1b4) at ported/librdmacm/cmatose.c:606
Note that data transfers have already gone from the server to the client, so an existing connection should be available.
The text was updated successfully, but these errors were encountered: