From owner-freebsd-stable@freebsd.org  Fri Sep 16 21:46:48 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 593E4BDD250
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 16 Sep 2016 21:46:48 +0000 (UTC)
 (envelope-from hiren@strugglingcoder.info)
Received: from mail.strugglingcoder.info (strugglingcoder.info
 [104.236.146.68])
 by mx1.freebsd.org (Postfix) with ESMTP id 48916DD3;
 Fri, 16 Sep 2016 21:46:47 +0000 (UTC)
 (envelope-from hiren@strugglingcoder.info)
Received: from localhost (unknown [10.1.1.3])
 (Authenticated sender: hiren@strugglingcoder.info)
 by mail.strugglingcoder.info (Postfix) with ESMTPA id 76CD717F65;
 Fri, 16 Sep 2016 14:46:46 -0700 (PDT)
Date: Fri, 16 Sep 2016 14:46:46 -0700
From: hiren panchasara <hiren@strugglingcoder.info>
To: Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc: Konstantin Belousov <kostikbel@gmail.com>, jch@FreeBSD.org,
 freebsd-stable@FreeBSD.org
Subject: Re: 11.0 stuck on high network load
Message-ID: <20160916214646.GR9397@strugglingcoder.info>
References: <20160904215739.GC22212@zxy.spb.ru>
 <20160905014612.GA42393@strugglingcoder.info>
 <20160914213503.GJ2840@zxy.spb.ru>
 <20160915085938.GN38409@kib.kiev.ua>
 <20160915090633.GS2840@zxy.spb.ru>
 <20160916181839.GC2960@zxy.spb.ru>
 <20160916183053.GL9397@strugglingcoder.info>
 <20160916190330.GG2840@zxy.spb.ru>
 <20160916191155.GM9397@strugglingcoder.info>
 <20160916203057.GH2840@zxy.spb.ru>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="F74xYepWx8quU230"
Content-Disposition: inline
In-Reply-To: <20160916203057.GH2840@zxy.spb.ru>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 21:46:48 -0000


--F74xYepWx8quU230
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote:
> On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote:
>=20
> >=20
> > As I suspected, this looks like a hang trying to lock V_tcbinfo.
> >=20
> > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve
> > performance for short-lived connections. I am not too sure if thats the
> > problem but looks in similar area so he may be able to provide some
> > insights.
>=20
> No, this is other case. In may case at this time no network traffic
> more then hour. This is some sore of deadlock or like.

In my limited understanding, such deadlock like situation can occur
without traffic too.

Cheers,
Hiren

--F74xYepWx8quU230
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAABCgBmBQJX3GhCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4
QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lbWoH/i9AjDz8VZy4LyfaQnA59BS8
SYBBVa0dBb/Oru+ltLUdSnG1YUgUfVDapCBBkAoZj4DBDDjFevzxcKBv3Dz4vDIS
Bpj6rOtwyqjzrDE/LG3FmT2Nt68PvKzO/Uk3TpluSvdI70q3yr9pzQAmGrAwsIz3
E706nb2fEecETnYP11kwrc9HPyPKJqIA2vOpvg7u5Ixa2PhdtfKrEUycD9Na8pMN
qug3UxlhR01w9VMUk7PGyIKc1VvI/RP0hFCIsR8hYdh37vDrPUYDwWOrOjzT+VMR
o8S0AItFzScO4Iw4igUQ6WnopGXvAx+ubR1Qpaomr3Lwd1cumLYvTlRWn3GyWCs=
=JFDK
-----END PGP SIGNATURE-----

--F74xYepWx8quU230--