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
If this isn't the right place to report this, then please redirect or forward.
We've seen processes that use the rsocket library hang indefinitely.
Here's a backtrace from such a process (obtained via gdb -p ...)
#0 0x00007f7d76bdf3ad in read () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f7d73e611f3 in read (__nbytes=8, __buf=0x7fff8c56c850, __fd=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2 __ibv_get_cq_event (channel=<optimized out>, cq=0x7fff8c56c880, cq_context=0x7fff8c56c888) at src/verbs.c:484
#3 0x00007f7d75688394 in ?? () from /usr/lib/librdmacm.so.1
#4 0x00007f7d75689ec0 in ?? () from /usr/lib/librdmacm.so.1
#5 0x00007f7d7568d23e in rshutdown () from /usr/lib/librdmacm.so.1
#6 0x00007f7d7568ec1a in rclose () from /usr/lib/librdmacm.so.1
#7 0x0000000000ddf454 in ordma_rclose (fd=<optimized out>) at ordma_close.c:28
This is version 1.0.21 (installed via debian package: librdmacm1 1.0.21mlnx-OFED.3.3.0.0.1.33100 )
If this isn't the right place to report this, then please redirect or forward.
We've seen processes that use the rsocket library hang indefinitely.
Here's a backtrace from such a process (obtained via
gdb -p ...
)This is version 1.0.21 (installed via debian package: librdmacm1 1.0.21mlnx-OFED.3.3.0.0.1.33100 )
It seems to be related to this SO question:
http://stackoverflow.com/questions/38119745/how-to-avoid-getting-stuck-in-rdma-get-recv-comp-or-ibv-get-cq-event
The text was updated successfully, but these errors were encountered: