-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SoftRoce failed while working with NVMeoF #63
Comments
Hello, I ran into the same issues attempting to set up a machine to test SPDK functionality with RDMA NICs. I would really appreciate your expertise in finding a workaround for this issue. Thank you
|
Does any of one has met with this issue or have any solution on it? Currently, i am setting up the environment on vagrant vm ro run with nvmf and also have the same issue. |
Hi,
I am trying to setup the NVMeoF using soft-roce but I didnt able to make it due to the following error
rdma_rxe:qp#17 moved to error state.
nvme nvme0 : identify controller failed.
when I debug it using KASAN it shows this:
[ 7.345365] rdma_rxe: qp#17 moved to error state
[ 8.847464] nvme nvme0 : identify controller failed.
[ 8.859829]
[ 8.861048] BUG: KASAN: stack-out-of-bounds in
rxe_post_send+0x12f3/0x1880 [rdma_rxe] at addr ffff88001f787838
which will flows to the infiniband driver code.that is
(gdb) list *(rxe_post_send+0x12f3)
0x1e133 is in rxe_post_send (drivers/infiniband/sw/rxe/rxe_verbs.c:685).
680 switch (wr->opcode) {
681 case IB_WR_RDMA_WRITE_WITH_IMM:
682 wr->ex.imm_data = ibwr->ex.imm_data;
683 case IB_WR_RDMA_READ:
please help me to find the solution for it.
The text was updated successfully, but these errors were encountered: