On Tue, Jan 16, 2018 at 2:50 PM, Olga Kornievskaia <aglo@xxxxxxxxx> wrote: > On Fri, Jan 12, 2018 at 7:07 PM, Steve Wise <swise@xxxxxxxxxxxxxxxxxxxxx> wrote: >>> > Ok. The memory probably doesn't matter. Maybe run krping client and >>> server on the same host (to use hw-loopback), and see if it works on both, >>> one, or neither systems when they are both the client and server. >>> >>> Loopback on the original "server" machine produces the same failure. >>> Jan 12 17:05:40 localhost kernel: mlx5_0:dump_cqe:277:(pid 0): dump error >>> cqe >>> Jan 12 17:05:40 localhost kernel: 00000000 00000000 00000000 00000000 >>> Jan 12 17:05:40 localhost kernel: 00000000 00000000 00000000 00000000 >>> Jan 12 17:05:40 localhost kernel: 00000000 00000000 00000000 00000000 >>> Jan 12 17:05:40 localhost kernel: 00000000 93003204 1000017c 0005e1d2 >>> Jan 12 17:05:40 localhost kernel: krping: cq completion failed with >>> wr_id 0 status 4 opcode 0 vender_err 32 >> >> Can someone from Mellanox comment more on the above CQE error? What exactly is it tell us? >> >>> >>> What does this means? >> >> Not sure. But it does seem to be tied to that specific machine. Question: Is an IOMMU enabled on that system? > > IOMMU (Inter's VT-d) is enabled in BIOS (on both machines). > >> Perhaps that is exposing a dma mapping problem with krping? I have replaces the CX-5 card with another one and I no longer see the krping problem. I think it speaks that it's a card issue... -- 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
