From owner-freebsd-stable@freebsd.org  Fri Sep 16 20:31:01 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 C4542BDD1B4
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 16 Sep 2016 20:31:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7F6A6319;
 Fri, 16 Sep 2016 20:31:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1bkzmj-0003U4-7l; Fri, 16 Sep 2016 23:30:57 +0300
Date: Fri, 16 Sep 2016 23:30:57 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: hiren panchasara <hiren@strugglingcoder.info>
Cc: jch@FreeBSD.org, Konstantin Belousov <kostikbel@gmail.com>,
 freebsd-stable@FreeBSD.org
Subject: Re: 11.0 stuck on high network load
Message-ID: <20160916203057.GH2840@zxy.spb.ru>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160916191155.GM9397@strugglingcoder.info>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
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 20:31:01 -0000

On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote:

> 
> As I suspected, this looks like a hang trying to lock V_tcbinfo.
> 
> 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.

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.