From owner-freebsd-stable@freebsd.org Thu Oct 6 08:06:53 2016 Return-Path: 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 CE93FAF5D12 for ; Thu, 6 Oct 2016 08:06:53 +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 BCE4D910; Thu, 6 Oct 2016 08:06:53 +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 AE2A0170D9; Thu, 6 Oct 2016 01:06:52 -0700 (PDT) Date: Thu, 6 Oct 2016 01:06:52 -0700 From: hiren panchasara To: Julien Charbon Cc: Slawa Olhovchenkov , Julien Charbon , Konstantin Belousov , freebsd-stable@FreeBSD.org Subject: Re: 11.0 stuck on high network load Message-ID: <20161006080652.GJ50669@strugglingcoder.info> References: <20160923200143.GG2840@zxy.spb.ru> <20160925124626.GI2840@zxy.spb.ru> <20160926172159.GA54003@zxy.spb.ru> <62453d9c-b1e4-1129-70ff-654dacea37f9@gmail.com> <20160928115909.GC54003@zxy.spb.ru> <20161006074459.GI50669@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HcccYpVZDxQ8hzPO" Content-Disposition: inline In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 08:06:53 -0000 --HcccYpVZDxQ8hzPO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 10/06/16 at 09:51P, Julien Charbon wrote: >=20 > Hi Hiren, >=20 > On 10/6/16 9:44 AM, hiren panchasara wrote: > > On 10/06/16 at 09:28P, Julien Charbon wrote: > >> On 9/28/16 1:59 PM, Slawa Olhovchenkov wrote: > >>> On Wed, Sep 28, 2016 at 12:06:47PM +0200, Julien Charbon wrote: > >>>> > >>>> I am still trying to reproduce your issue, without success so far. > >> > >> Thanks for Slawa effort and multiple debug report we start seeing the > >> bottom of this issue and it seems to be a generic one. The most useful > >> report being: > >> > >> panic: tcp_detach: INP_TIMEWAIT && INP_DROPPED && tp !=3D NULL > >=20 > > I know there are multiple and probably related problems being > > discussed here but what about the one mentioned in subject of this > > thread? > > Apologies if I've missed something conclusive in one of the replies of > > this thread about that issue. >=20 > This issue can lead the machine being stuck on high network load, by > double freeing an inp, you can corrupt/leak an inp lock, and the network > stack can wait definitely on this inp lock to be released. You get this > assert only with INVARIANTS defined. >=20 > Of usual, we can have more than one issue here, but this > INP_TIMEWAI|INP_DROPPED issue need to be fixed anyway. Thanks for the explanation, Julien. Cheers, Hiren --HcccYpVZDxQ8hzPO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJX9gYYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/l7zMIAIDlxx1T+V7xsSvV9vS/qaj+ pYYQZRDhthWYxDiimtzT1hn3sikXqC1ox+0LHEIawt1LtcdFzRvEBu4qhTC/wIPB N37mUwrrGGdJGfaovKxU1dx7V6GYHKEoxeTdIqP0SMiwUrCl2P0zuVcv0mGYYKNW g0PwZXVF4J46nb28TnfD/4etbxT7ZqibrNNt+bqKCe+MJSY+XY3gfeE8B5TvR+GI wSPPHkwMegTGE5/dlSs9kr94ijUdBjUPbldufi+8QvlOo6FMQUo8qqPYnyUZ1K2Y TkkcP6Mx+ogKPsQmyNvbJyFd+qnaz3pPopKO6I6TXXuf6QEXkbAGbhdGvw4FP64= =a3k/ -----END PGP SIGNATURE----- --HcccYpVZDxQ8hzPO--