From owner-freebsd-stable@freebsd.org Thu Oct 6 08:59:35 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 C135FBD36E5 for ; Thu, 6 Oct 2016 08:59:35 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7359EFC5 for ; Thu, 6 Oct 2016 08:59:35 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: by mail-qk0-f177.google.com with SMTP id n189so10601628qke.0 for ; Thu, 06 Oct 2016 01:59:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=HvU+wO5vh10ruJqUYW2etcMHEv5qd5EXqU7zDUhjvec=; b=ktF7y2jUxxdEkm2nccryKsoRFOOAFyKxAIMeWBesyhe6RYbBr4MzBXWdKqK4Optb2G KCKHDAe568A2v2Al0IWE4CqwJfVdPQFgxMwxwKdjpNEmZheMBv4KXZYID+A2YA1qyOZ5 vzLt9gtR/zjQG9vyL6Yy0ycKb5LZ2wKWf87xKaU+vjgSa7KQqqW9XuTiyVL8DUCKrjpa Xca86yZ6vAhOc2ZuZzKL3qWzb1nUWXinzT95nb7X6TtPGHJ0AgX9z8kPKPBq7bStQale DtiFjP9oAI4iBtKGSB16L9/l9Jy/iL3GpvR3YTDW2u9z27VK5aG0qP+cyAhH03xpk7k9 x8yA== X-Gm-Message-State: AA6/9RlC+p5400xNbyJIyw6QW/WnFwo+frcwv2bWyX4y23BgvA7pBloswp/EENSx2RDcgA== X-Received: by 10.55.5.21 with SMTP id 21mr13907897qkf.231.1475740321630; Thu, 06 Oct 2016 00:52:01 -0700 (PDT) Received: from [10.100.64.23] ([217.30.88.44]) by smtp.gmail.com with ESMTPSA id v5sm493686qtc.24.2016.10.06.00.51.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Oct 2016 00:52:00 -0700 (PDT) Subject: Re: 11.0 stuck on high network load To: hiren panchasara References: <20160921195155.GW2840@zxy.spb.ru> <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> Cc: Slawa Olhovchenkov , Julien Charbon , Konstantin Belousov , freebsd-stable@FreeBSD.org From: Julien Charbon Message-ID: Date: Thu, 6 Oct 2016 09:51:44 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20161006074459.GI50669@strugglingcoder.info> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hpo3idiVRA9C8RP2Uug5lNLsNiiLQ1soo" 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:59:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hpo3idiVRA9C8RP2Uug5lNLsNiiLQ1soo Content-Type: multipart/mixed; boundary="UNWhH0cTeRXX8arXRVpufSMpxKxBxOBi8"; protected-headers="v1" From: Julien Charbon To: hiren panchasara Cc: Slawa Olhovchenkov , Julien Charbon , Konstantin Belousov , freebsd-stable@FreeBSD.org Message-ID: Subject: Re: 11.0 stuck on high network load References: <20160921195155.GW2840@zxy.spb.ru> <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> In-Reply-To: <20161006074459.GI50669@strugglingcoder.info> --UNWhH0cTeRXX8arXRVpufSMpxKxBxOBi8 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Hiren, 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 usefu= l >> 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. 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. Of usual, we can have more than one issue here, but this INP_TIMEWAI|INP_DROPPED issue need to be fixed anyway. -- Julien --UNWhH0cTeRXX8arXRVpufSMpxKxBxOBi8-- --hpo3idiVRA9C8RP2Uug5lNLsNiiLQ1soo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJX9gKZAAoJEKVlQ5Je6dhxT8sIALTO7JPbleGxCy9w0a6sRMkN xugGeEmPA2RLPduj4WbDHANRvXCx+tNEjdlkeHPd3m1M4Vh7Bs5aGr42QG/ZdiW3 HIP9nOwh3xSSyA5m+CVC/lqQoR7r3xX+9W9D1mfRCWK3O2NcubsxhqZOecgP3uAY /chrvU5zCd/Kkeep3TNhlX39PLf4Vi46tMCmfwV2JW7UKOgVWm3w1Bb3fXcfea2e +gnlEFTeng0pRtOd/emQwOcIWIC2I80HDurSXX3O3zkUCC4eQX0bMmX1vvFwSUHa zqRmBLBH3k7/AKqKBNy7b19lwzlO6eeJfYUaKmP1afXTx54wY5Z8ABVwvdP/iKQ= =TLuh -----END PGP SIGNATURE----- --hpo3idiVRA9C8RP2Uug5lNLsNiiLQ1soo--