On 29/01/2018 22:18, Joel Nider wrote: > Hi Ilya, > > I am using ConnectX5 EN with special firmware (I just mention it so you > know, but I'm pretty sure that's not the problem). I have used dynamic > debug - it shows me that the call is failing like this: > > mlx5_core 0000:01:00.0: mlx5_cmd_check:714:(pid 120772): CREATE_QP(0x500) > op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x48b5c0) The syndrome means: "create_qp: invalid service type for RoCE" what QP type are you trying to create and with what parameters? > > Is there any way for me to look up the syndrome? > > Ilya Lesokhin <ilyal@xxxxxxxxxxxx> wrote on 29/01/2018 21:04:57: >>> >>> I have used the net/smc module extensively as a reference, but there > seems >>> to be something fundamental that I'm missing. How can I find out > what's >>> going wrong here? >> >> Hi Joel, >> What ROCE device are you using? >> There are many debug prints in the Mellanox drivers. >> You should try enabling dynamic debug for mlx4_ib or mlx5_ib, it might > give >> you more information. >> >> Good luck, >> Ilya >> > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Mark -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
