From owner-freebsd-infiniband@FreeBSD.ORG Mon Jun 10 13:41:47 2013 Return-Path: Delivered-To: freebsd-infiniband@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 544666B3 for ; Mon, 10 Jun 2013 13:41:47 +0000 (UTC) (envelope-from jsteckli@os.inf.tu-dresden.de) Received: from os.inf.tu-dresden.de (os.inf.tu-dresden.de [IPv6:2002:8d4c:3001:48::99]) by mx1.freebsd.org (Postfix) with ESMTP id 19C8418F0 for ; Mon, 10 Jun 2013 13:41:47 +0000 (UTC) Received: from [2002:8d4c:3001:48:ea40:f2ff:fee2:6328] by os.inf.tu-dresden.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1) id 1Um2Lx-0001Mo-Ih for freebsd-infiniband@freebsd.org; Mon, 10 Jun 2013 15:41:46 +0200 Message-ID: <51B5D798.5090008@os.inf.tu-dresden.de> Date: Mon, 10 Jun 2013 15:41:44 +0200 From: Julian Stecklina User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: "freebsd-infiniband@freebsd.org" Subject: ib1: timing out; N sends not completed X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2XELEWWATAANBQTANMPNP" X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jun 2013 13:41:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2XELEWWATAANBQTANMPNP Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, I have two machines connected back-to-back via Infiniband with Mellanox Infinihost III adapters. One machine runs Linux (Fedora 19) and the other 9-STABLE. I sometimes get: ib1: timing out; 47 sends not completed ib1: timing out; 1 sends not completed ib1: timing out; 56 sends not completed or similar and TCP connections will be stuck after each timeout for a while. It is relatively easy to reproduce this behavior with NetPIPE. Any advice? Julian ------enig2XELEWWATAANBQTANMPNP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEARECAAYFAlG115kACgkQ2EtjUdW3H9nLqgCdHu76PgVQQKPPXT9v+c5tR9kS eDMAn3raiW+HU2hudIYDn1eec0lh8520 =rwlV -----END PGP SIGNATURE----- ------enig2XELEWWATAANBQTANMPNP--