public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
To: Tom Tucker <tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
	<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: [ewg] MLX4 Strangeness
Date: Tue, 16 Feb 2010 09:53:24 +0200	[thread overview]
Message-ID: <4B7A4EF4.9090209@mellanox.co.il> (raw)
In-Reply-To: <4B79AD88.8000101-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>

On 2/15/2010 10:24 PM, Tom Tucker wrote:
> Hello,
>
> I am seeing some very strange behavior on my MLX4 adapters running 2.7
> firmware and the latest OFED 1.5.1. Two systems are involved and each
> have dual ported MTHCA DDR adapter and MLX4 adapters.
>
> The scenario starts with NFSRDMA stress testing between the two systems
> running bonnie++ and iozone concurrently. The test completes and there
> is no issue. Then 6 minutes pass and the server "times out" the
> connection and shuts down the RC connection to the client.
>
>   From this point on, using the RDMA CM, a new RC QP can be brought up
> and moved to RTS, however, the first RDMA_SEND to the NFS SERVER system
> fails with IB_WC_RETRY_EXC_ERR. I have confirmed:
>
> - that "arp" completed successfully and the neighbor entries are
> populated on both the client and server
> - that the QP are in the RTS state on both the client and server
> - that there are RECV WR posted to the RQ on the server and they did not
> error out
> - that no RECV WR completed successfully or in error on the server
> - that there are SEND WR posted to the QP on the client
> - the client side SEND_WR fails with error 12 as mentioned above
>
> I have also confirmed the following with a different application (i.e.
> rping):
>
> server# rping -s
> client# rping -c -a 192.168.80.129
>
> fails with the exact same error, i.e.
> client# rping -c -a 192.168.80.129
> cq completion failed status 12
> wait for RDMA_WRITE_ADV state 10
> client DISCONNECT EVENT...
>
> However, if I run rping the other way, it works fine, that is,
>
> client# rping -s
> server# rping -c -a 192.168.80.135
>
> It runs without error until I stop it.
>
> Does anyone have any ideas on how I might debug this?
>
>
>    
Tom
What is the vendor syndrome error when you get a completion with error?

Does the issue occurs only on the ConnectX cards (mlx4) or also on the 
InfiniHost cards (mthca)

Tziporet

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-02-16  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 20:24 MLX4 Strangeness Tom Tucker
     [not found] ` <4B79AD88.8000101-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-02-16  7:53   ` Tziporet Koren [this message]
     [not found]     ` <4B7A4EF4.9090209-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2010-02-16 15:21       ` [ewg] " Tom Tucker
2010-02-16 21:31       ` Tom Tucker
     [not found]         ` <4B7B0E98.9030506-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-02-17  0:18           ` Tom Tucker
     [not found]             ` <4B7B35DD.1030609-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-02-17  0:25               ` Tom Tucker
2010-02-17 18:06               ` Tom Tucker
2010-02-19  0:03                 ` Vu Pham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7A4EF4.9090209@mellanox.co.il \
    --to=tziporet-vpraknaxozvs1mouv/rt9w@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox